Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Vasco Duarte, Agile Coach, Certified Scrum Master, Certified Product Owner

Every week day, Certified Scrum Master, Agile Coach and business consultant Vasco Duarte interviews Scrum Masters and Agile Coaches from all over the world to get you actionable advice, new tips and tricks, improve your craft as a Scrum Master with daily doses of inspiring conversations with Scrum Masters from the all over the world. Stay tuned for BONUS episodes when we interview Agile gurus and other thought leaders in the business space to bring you the Agile Business perspective you need to succeed as a Scrum Master. Some of the topics we discuss include: Agile Business, Agile Strategy, Retrospectives, Team motivation, Sprint Planning, Daily Scrum, Sprint Review, Backlog Refinement, Scaling Scrum, Lean Startup, Test Driven Development (TDD), Behavior Driven Development (BDD), Paper Prototyping, QA in Scrum, the role of agile managers, servant leadership, agile coaching, and more!

  1. 7h ago

    When the Jira Board Looked Fine but the Agile Team Was Drained | Joseph Osei-Kusi

    Joseph Osei-Kusi: When the Jira Board Looked Fine but the Agile Team Was Drained Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Metrics are conversation starters, not the full truth." - Joseph Osei-Kusi   Joseph Osei-Kusi joins us from New York to share a failure from early in his Scrum Master journey, when he became what he calls the "Jira observer Scrum Master." The board looked clean, the metrics looked acceptable, and the tasks appeared to be moving. Underneath that tidy surface, the team was losing energy. People had stopped speaking up, agreement came too quickly, and the real conversations moved outside the meetings. Joseph realized too late that he had been paying more attention to the board than to the people doing the work. The cost was real: two developers left the team. That moment changed how he approached the role. Today, Joseph uses metrics as an invitation to ask better questions: What changed? How does the team feel? What are we not seeing? For Scrum Masters, the warning is simple: a board can look healthy while the human system is already struggling.   In this episode, we refer to psychological safety and how Scrum Masters can use metrics as a doorway into better team conversations.   Self-reflection Question: What quiet signals might your team be sending that do not show up on your Jira board?   [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.   🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.   Buy Now on Amazon   [The Scrum Master Toolbox Podcast Recommends]   About Joseph Osei-Kusi   Joseph is an Agile coach and Scrum Master obsessed with the human side of delivery. He has focused on moving teams beyond just "following the process" to delivering value. He champions radical transparency and psychological safety, and believes that when you get the people part right, everything else falls into place.   You can link with Joseph Osei-Kusi on LinkedIn.

  2. 2d ago

    BONUS AI Changes Management, Not Leadership With Mateo Bervejillo

    BONUS: AI Changes Management, Not Leadership In this BONUS episode, we explore what AI changes for software leaders, and what it leaves firmly in human hands. Mateo Bervejillo, CEO of Xseed Solutions and author of Back to Basics, brings the view of a manager of managers: AI can help us process information faster, but leadership still happens through clarity, judgment, and relationships. From Attorney to Software CEO: Clarity as a Leadership Skill "What are we building? Why are we building it? What's the benefit for the client? What's the business value?"   Mateo started his career as an attorney, then moved through operations, vendor management, business development, and finally into software company leadership. That path gave him an unusual advantage in technology: an obsession with clear definitions. In law, unclear scope creates risk. In software, unclear scope creates waste, frustration, and products that miss the point. For Mateo, leadership starts before execution, with crisp answers to simple questions: what problem are we solving, why does it matter, and what would success look like? AI Removes Busywork, But It Does Not Replace Leadership "There's a part about management that is moving information around, up and down, sideways. That is changing drastically because of AI."   Mateo sees AI transforming the administrative side of management: gathering data, processing updates, preparing reports, and helping managers stay on top of follow-ups. But he draws a firm line between management mechanics and leadership. AI can make managers faster at moving information, but it cannot choose the right people, create trust, provide meaningful feedback, or understand what motivates each person. The danger is that organizations may conclude they need fewer leaders because the reporting work became easier, while the human work actually becomes more important. The One-on-One Cannot Become a Slack Check-In "If you have one manager leading 50 people, that one-on-one that was so important now becomes a Slack message."   One of the risks Mateo calls out is the pressure to flatten organizations and stretch managers across too many people. On paper, AI makes that look possible. In practice, it can turn leadership into status collection. Mateo described his own weekly rhythm: face-to-face conversations, walking meetings, and one-hour one-on-ones where the work is to listen, ask questions, understand what is happening in the person's life and work, and keep the company aligned around its North Star. That is not overhead. It is the work that keeps teams healthy before problems become escalations. Use AI as a Sparring Partner, Not as the Thinker "The problem of the blank page goes away with AI. You can have a conversation."   Mateo uses AI as an assistant for podcast preparation, idea generation, research, outreach, and even book writing. When drafting Back to Basics, he used AI to challenge the structure and ask what was missing, which led to several chapters he had not planned. The point is not to outsource judgment. It is to remove the fear of starting, create better first drafts, and pressure-test thinking. For Scrum Masters and agile coaches, that means AI can help design workshops, prepare questions, and explore options, but the leader still has to understand the context and make the call. Outcomes Keep Leaders Away From Micromanagement "Too much focus on the inputs can be misleading and you forget about the outcome, which is where the client sits."   AI gives managers more visibility into activity, and that can quickly become control. Mateo's antidote is to keep the organization focused on outputs and outcomes instead of inputs. Story points, process steps, and activity metrics can be useful, but they can also pull leaders into managing the wrong thing. Clients care about outcomes. Teams need clarity about the result, then room to decide how to get there. When leaders become obsessed with the how of every input, they move from creating clarity into micromanagement. Managing Up With AI, Managing People With Care "Today we are going through a time where we need to stay close to people more than ever and make it personal."   In Mateo's book, leadership is framed across four dimensions: managing up, managing yourself, managing teams, and managing sideways. Through the AI lens, he sees the biggest immediate gain in managing up: clearer communication, faster delivery, better follow-up, and fewer things falling through the cracks. But when it comes to managing teams, the basic human work becomes more important. People are anxious about AI and jobs, even when they are not saying it openly. Leaders need to stay close, make the relationship personal, and create the conditions where people can thrive. About Mateo Bervejillo Mateo Bervejillo is CEO of Xseed Solutions, a Montevideo-based software development and staff augmentation company helping US firms build high-performing LATAM engineering teams. An attorney by background, he brings a results-first view to tech leadership. He wrote Back to Basics, a practical leadership guide for new managers in technology. LinkedIn.   You can link with Mateo Bervejillo on LinkedIn, learn more about Xseed Solutions, and listen to Mateo's podcast, The Future Of The Future.

  3. 3d ago

    Product Owners Who Turn Feedback Into Agile Team Learning | Oluyomi Emmanuel

    Oluyomi Emmanuel: Product Owners Who Turn Feedback Into Agile Team Learning The Great Product Owner: Listening, Investing, and Learning With the Team Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "A great product owner is not the person with all the answers. It is the person who creates access to the right evidence." - Oluyomi Emmanuel   Oluyomi shares the example of a Product Owner whose strongest habit was asking the team for feedback, listening without defending himself, and then acting on what he heard. In one sprint review, the team looked at internal metrics and raised a difficult concern: they were completing work, but it did not always seem closely connected to what customers needed. The Product Owner could have defended the roadmap or blamed incomplete metrics. Instead, he treated the feedback as evidence worth investigating. He secured a training budget and enrolled both himself and the whole team in behavior-driven development training. More importantly, the training did not remain a certificate exercise. The Product Owner joined the learning and helped bring BDD practices into refinement, stakeholder conversations, and interviews. The team's conversations moved from abstract requirements to specific situations and expected outcomes. Hidden assumptions became visible earlier, and the team could challenge unclear requirements constructively before implementation began.   Self-reflection Question: How does your Product Owner show the team that feedback changes real behavior? The Bad Product Owner: The Absent Product Owner as a Role Design Problem Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "An absent product owner is often not an individual time management problem. It is usually a role design problem." - Oluyomi Emmanuel   Oluyomi also describes the absent Product Owner anti-pattern. In his example, the Product Owner was not careless or uninterested. The structural problem was that the same person was both Product Owner and line manager, so the Product Owner role kept being squeezed into whatever time remained. Epics existed, but the team lacked enough context to refine them. Questions accumulated, refinement became a place to discover missing information, and important decisions waited for someone who was rarely available. Oluyomi first asked for more Product Owner availability, but that did not change the system because the competing responsibilities remained. He then created a stakeholder map for the major areas of work: who had the business problem, who owned the desired outcome, who had specialist knowledge, and who would be affected by the change. Inviting relevant stakeholders into refinement gave developers direct access to context. The lesson was not to remove product ownership, but to stop making the Product Owner the only messenger between the team and every stakeholder.   In this segment, we refer to behavior-driven development, product ownership, and stakeholder collaboration.   Self-reflection Question: Are you compensating for an unavailable Product Owner in a way that keeps the real organizational design problem hidden?   [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.   🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.   Buy Now on Amazon   [The Scrum Master Toolbox Podcast Recommends]   About Oluyomi Emmanuel   Oluyomi is a Scrum Master, Agile Coach, and Product Lead with over seven years of experience helping teams work better and deliver meaningful digital products. Having worked across energy, consumer platforms, and fintech, he is passionate about building high-performing teams, creating clarity, and turning Agile principles into real business and customer value.   You can link with Oluyomi Emmanuel on LinkedIn.

  4. 4d ago

    Constructive Independence as a Scrum Master Success Metric | Oluyomi Emmanuel

    Oluyomi Emmanuel: Constructive Independence as a Scrum Master Success Metric Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Success is when the team increases its capacity to notice, discuss, and solve the problems that stand between them and meaningful outcomes." - Oluyomi Emmanuel   Oluyomi's definition of Scrum Master success has changed over time. Today, he measures success by the team's growing ability to notice, discuss, and solve the problems that stand between them and meaningful outcomes. One practical signal is when someone in the team says or does something he would previously have needed to prompt: a developer challenges an unclear requirement, a tester raises a risk before anyone asks, or a team member names a problem directly. Oluyomi calls the strongest indicator "constructive independence." That does not mean the team no longer needs support. It means the team's mental model has matured enough that people act earlier, with more ownership and less dependency. To keep himself accountable, Oluyomi runs a small personal retrospective at the end of each workday. He starts the day with a few things he wants to measure himself by, then later uses Copilot as a reflection partner to compare intention with action. Vasco notes that this is one useful way AI tools can help Scrum Masters maintain the discipline of reflection without relying only on memory.   Self-reflection Question: What would tell you that your team is becoming constructively independent? Featured Retrospective Format for the Week: True or False Statements Oluyomi does not pick a retrospective format before understanding the sprint. He watches patterns during the iteration: how work waits, how conflict is handled, whether decisions are revisited, and whether people ask for help early. One format he often uses is a set of true-or-false statements about the sprint and collaboration. For example: "We finished work before starting more work" or "We asked for help early enough during the sprint." Team members vote silently first, either on a Miro board or with physical cards. The value is not the majority answer. The value appears when different people interpret the same sprint differently. Instead of asking who is right, Oluyomi asks what each group observed that led to its answer.   [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.   🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.   Buy Now on Amazon   [The Scrum Master Toolbox Podcast Recommends]   About Oluyomi Emmanuel   Oluyomi is a Scrum Master, Agile Coach, and Product Lead with over seven years of experience helping teams work better and deliver meaningful digital products. Having worked across energy, consumer platforms, and fintech, he is passionate about building high-performing teams, creating clarity, and turning Agile principles into real business and customer value.   You can link with Oluyomi Emmanuel on LinkedIn.

  5. 5d ago

    Creating Agile Value Stream Visibility Without More Administration | Oluyomi Emmanuel

    Oluyomi Emmanuel: Creating Agile Value Stream Visibility Without More Administration Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Transparency is not created by displaying more information. Transparency is created when people share enough meaning to interpret that information in the same way." - Oluyomi Emmanuel   Oluyomi's current challenge is helping an organization create end-to-end visibility and ownership across several value streams without turning the solution into another layer of administration. At first, the problem looked like a Jira hierarchy issue: initiatives, epics, stories, and tasks needed shared definitions. But the conversations exposed something deeper. Different groups used the same work item names to mean different things, and those differences made prioritization, dependency management, coordination, and reporting harder. Together with a colleague, Oluyomi framed the work as alignment experiments instead of a large rollout. One workshop asked what makes an initiative different from an epic, what information must exist before work moves forward, and when the next level of work should be created. The biggest tension was ownership, not terminology. A second experiment, a cross-value-stream visibility session, used real initiatives to expose overlapping work, unclear ownership, and weak links to outcomes. Vasco then pushed the conversation toward intake: perhaps the problem was not only shared meaning, but the absence of a single view of what the organization needs to do. Oluyomi's next experiment is linking initiatives to quarterly goals and OKRs to see what really deserves attention.   In this episode, we refer to value streams, OKRs, and portfolio management.   Self-reflection Question: Does your organization have one visible list of important work, or many competing lists with unclear ownership?   [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.   🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.   Buy Now on Amazon   [The Scrum Master Toolbox Podcast Recommends]   About Oluyomi Emmanuel   Oluyomi is a Scrum Master, Agile Coach, and Product Lead with over seven years of experience helping teams work better and deliver meaningful digital products. Having worked across energy, consumer platforms, and fintech, he is passionate about building high-performing teams, creating clarity, and turning Agile principles into real business and customer value.   You can link with Oluyomi Emmanuel on LinkedIn.

  6. 6d ago

    From My Task to Our Work in Agile Teams | Oluyomi Emmanuel

    Oluyomi Emmanuel: From My Task to Our Work in Agile Teams Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "We shifted their thinking from my task to our work." - Oluyomi Emmanuel   Oluyomi describes a destructive pattern many Scrum Masters will recognize: local responsibility inside a supposedly shared team. The team looked collaborative during Scrum events, but once the meetings ended, developers, testers, and reviewers behaved like separate specialists. Developers finished coding and moved on. Testers waited for the right context or environment. Pull requests sat in review. Everyone looked busy, and everyone could explain their own behavior, but work was not reaching Done. The board already showed the queues, yet visibility alone did not change behavior because the team still spoke in individual language: "my development is finished," "testing belongs to QA," and "my task is done." The change started in a retrospective, where the team stopped asking who caused the delay and began asking where work stopped flowing. They tested small experiments: swarming around items waiting in testing, reviewing aging work together, and avoiding new starts when existing work needed help. The daily standup became a place to ask a better question: what does this item still need before value can be delivered?   In this segment, we talk about flow, team ownership, and work in progress.   Self-reflection Question: What language in your daily standup reinforces "my task" instead of "our work"? Featured Book of the Week: Handbook of Facilitative Leadership by Pepe Nummi Oluyomi recommends Handbook of Facilitative Leadership: Concrete Ways to Boost Performance by Pepe Nummi. The book helped him see that leadership is not always about having the strongest opinion or offering the solution. Sometimes leadership means designing the process through which a group can think, contribute, decide, and take ownership together. For Scrum Masters, that distinction matters because the people in the room often already have the knowledge needed to solve the problem. The knowledge is just distributed across the team. Facilitative leadership helps bring that knowledge into the open.   [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.   🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.   Buy Now on Amazon   [The Scrum Master Toolbox Podcast Recommends]   About Oluyomi Emmanuel   Oluyomi is a Scrum Master, Agile Coach, and Product Lead with over seven years of experience helping teams work better and deliver meaningful digital products. Having worked across energy, consumer platforms, and fintech, he is passionate about building high-performing teams, creating clarity, and turning Agile principles into real business and customer value.   You can link with Oluyomi Emmanuel on LinkedIn.

  7. Oct 5

    When Agile Team Trust Breaks Before the Scrum Master Acts | Oluyomi Emmanuel

    Oluyomi Emmanuel: When Agile Team Trust Breaks Before the Scrum Master Acts Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Once that trust is broken, everything else, nothing else matters." - Oluyomi Emmanuel   Oluyomi Emmanuel started his Scrum Master journey after a strategic move toward Agile ways of working changed his project coordinator role into something deeper: helping people communicate when the answers were unclear. In this episode, he shares a hard lesson from a newly formed software team of eight people, where tension between a tech lead and a new developer first appeared in GitHub pull request comments. There were sarcastic replies, cameras switched off during the daily standup, and a growing distance when the team worked in the same office. Oluyomi initially treated it as a normal forming-stage conflict and waited for the team environment to absorb the tension. By the time the tech lead escalated concerns to the developer's line manager, trust had already deteriorated. A facilitated feedback session produced an improvement plan, but the developer experienced the feedback as judgment rather than support and left the team less than a month later. Oluyomi's lesson was clear: a Scrum Master needs to name trust concerns early, first in one-on-ones, then together, before the relationship becomes too damaged to repair.   In this episode, we refer to psychological safety, conflict resolution, and team trust.   Self-reflection Question: What early sign of broken trust have you noticed but not yet named with your team?   [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.   🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.   Buy Now on Amazon   [The Scrum Master Toolbox Podcast Recommends]   About Oluyomi Emmanuel   Oluyomi is a Scrum Master, Agile Coach, and Product Lead with over seven years of experience helping teams work better and deliver meaningful digital products. Having worked across energy, consumer platforms, and fintech, he is passionate about building high-performing teams, creating clarity, and turning Agile principles into real business and customer value.   You can link with Oluyomi Emmanuel on LinkedIn.

  8. Oct 3

    BONUS Why AI Needs More Than Silicon Valley Moonshots With Salima Bhimani

    BONUS: Why AI Needs More Than Silicon Valley Moonshots With Salima Bhimani AI is changing the work of software teams, but Salima Bhimani argues that the bigger question is not only what AI can automate. In this BONUS episode, Salima shares what she learned inside Alphabet's moonshot ecosystem, why breakthrough ideas may be hiding in plain sight, and how more people can become moonshot makers when technology meets lived intelligence. Invention Starts in Real-World Constraints "Invention is something that is always happening in relationship to something that's in the world."   Salima traces her view of invention back to a family history of migration, adaptation, and rebuilding under constraints. Her roots go from India to East Africa, where her family had to learn new languages, new land, and new ways to survive. That experience shaped a practical view of innovation: invention is not only the work of a lone genius in a lab. It often starts in friction, necessity, and the daily encounter between people and the systems around them. We May Be Thinking Too Small About Innovation "We've actually shrunk our ability to see what's out there in the world by limiting who's in the room."   Salima respects what Silicon Valley has built, from search to self-driving technology to AI. But her challenge is that the dominant innovation model often starts with a small group defining the problem, building a product, and then deploying it into the world. That can miss the collective intelligence already present in the places where the problems live. For software leaders and agile practitioners, the question becomes sharper: what would change if discovery started earlier, closer to the real ecosystem, with more forms of expertise present before the solution is framed? AI as Infrastructure, Not the Destination "The software itself is not just the solution. The software is the catalyst."   Salima argues that many organizations are still focused on AI as a tool for optimization: saving seconds, making teams more productive, or automating parts of the work. Those uses matter, but they can keep leaders thinking too narrowly. When AI becomes infrastructure, it becomes part of the platform that unlocks growth, capacity, and new ways to work across a system. In software organizations, that means shifting attention from "what tool should we apply?" to "what outcome could this platform make possible?" Breakthroughs Come From Asking What the World Needs "The greatest breakthroughs come from people really sitting down and asking what the world needs or doesn't need."   Working around Alphabet's moonshot environment taught Salima that breakthrough ideas are not only born from research labs or visionary founders. The next generation of innovation may come from people asking better ecosystem-level questions: how education changes with AI, how talent changes, how information is consumed, and how the labor market shifts around new infrastructure. The barrier to entry is lower now, which means more people can stand in the place where moonshots are imagined. Third-Space Moonshots Bring the Lab to the Street "Technology is not the breakthrough. Technology is a partner that allows us to unlock something in a system."   In Invent Now, Salima describes third-space moonshots as the convergence of three forces: technology as a co-partner, complex systems such as health, education, mobility, or energy, and human ingenuity from lived experience. This is not simply adding more people to a workshop. It is a different way of discovery, where an engineer, a scientist, a historian, and a street vendor may each see an opportunity the others would miss. As Vasco framed it, this is about bringing street smarts to the lab, and the lab to street smarts. Humanity Is the Moonshot "Humanity is the moonshot, not technology."   The Zimbabwe Bush Pump example in Salima's book challenges the usual mental model of moonshots. It may not look like a Silicon Valley breakthrough, but it asks a deeper question: who gets to define what counts as invention, and what kind of impact matters? AI may help us build more, faster, and with lower barriers. But Salima's point is that the real opportunity is not replacing human ingenuity. It is helping more people bring their lived experience into the act of building what their communities, teams, and systems actually need. Becoming a Moonshot Maker "It's a book to spar with. It's not a book to just read."   Salima does not describe Invent Now as a playbook. She describes it as an invitation to spar with ideas, disagree, and use the book to provoke new thinking. For Scrum Masters, agile coaches, product leaders, and software teams, that invitation is practical: stop treating AI as the whole story, and start using it as one partner in a broader discovery conversation. The biggest opportunities may already be visible to people inside the system. The work is to notice them, bring the right knowledge together, and build from there. About Salima Bhimani Dr. Salima Bhimani is the author of Invent Now: The Next Leap in Moonshots and CEO of 10X Responsible Tech. A former Alphabet chief strategist for responsible technology, business, and leaders, she worked across Waymo, Wing, DeepMind, and Google X. Her work focuses on AI, moonshots, and inclusive innovation. LinkedIn   You can link with Salima Bhimani on LinkedIn, learn more at salimabhimani.com, and read her book Invent Now: The Next Leap in Moonshots.

4.7
out of 5
181 Ratings

About

Every week day, Certified Scrum Master, Agile Coach and business consultant Vasco Duarte interviews Scrum Masters and Agile Coaches from all over the world to get you actionable advice, new tips and tricks, improve your craft as a Scrum Master with daily doses of inspiring conversations with Scrum Masters from the all over the world. Stay tuned for BONUS episodes when we interview Agile gurus and other thought leaders in the business space to bring you the Agile Business perspective you need to succeed as a Scrum Master. Some of the topics we discuss include: Agile Business, Agile Strategy, Retrospectives, Team motivation, Sprint Planning, Daily Scrum, Sprint Review, Backlog Refinement, Scaling Scrum, Lean Startup, Test Driven Development (TDD), Behavior Driven Development (BDD), Paper Prototyping, QA in Scrum, the role of agile managers, servant leadership, agile coaching, and more!

You Might Also Like