Mario Lucero

🎯 Agile transformation isn’t about frameworks. It’s about people. One key takeaway from our recent ICP-LEA (ICAgile Leadership) workshop: Organizations that thrive don’t just “do” Agile. They develop internal coaching capabilities to engage teams, challenge limiting beliefs, and guide behavioral change at scale. This is where leadership coaching becomes powerful: ✔️ Builds self-awareness and decision-making courage ✔️ Encourages authentic engagement, not just compliance ✔️ Sustains transformation by growing leadership at every level Grateful for the deep reflections and real conversations from this cohort 🙏 Let’s continue building leaders who coach, not command. #CoachingMatters #AgileLeadership #CoachingCulture #AgileTransformation #LeadershipCoaching

12

What is the difference between an Agile coach and a Productivity coach? Productivity coaches focus on how to accelerate flow of value into the hands of your users. We use many techniques to do this, including many Agile techniques. The main difference is that the goal is always to increase flow. Like agile coaches, we also aim to improve culture. A difficult culture is one of the biggest impediments to flow, so it is always front and center when looking at how to improve productivity. For example, if your culture punishes red metrics, most people will fear showing red metrics. The red will still be there, but you will be blind to it. If you want to improve flow, you need to learn the "green is bad, red is good" mindset. Fear based cultures crush productivity in many different ways. Some agile coaches have always done this. You might be one of them. But many were more interested in following the rules, or saw the goal as "go agile" or "be agile" or "transform to an agile organization." Those are all valid strategies, but are not business goals. When asked "why do we have to work this new/different way?" I've seen agile coaches say "because that is what scrum says you should do." A productivity coach would show how the new way removes an impediment to flow, or would not introduce the change. Take a fundamental "rule" like writing Acceptance Criteria for a story. If a team wasn't, an agile coach might tell them they had to. A productivity coach would not unless it removed an impediment to flow. If the team wasn't having trouble getting work accepted or getting surprised by changes in the ask at story close, writing acceptance criteria might actually slow such a team down. So they wouldn't force it just because it is in the rule book. I have learned faster ways to write stories, write acceptance criteria, estimate work and teach those to my teams. Agilists sometimes argue with my approaches when the approaches don't follow the traditional rules. Productivity coaches evaluate if the approaches are faster, and do no harm down the road. Then adopt them into their teams too if convinced. Productivity coaches are most effective at leadership levels and portfolio levels, but can also accelerate large teams of teams and small agile teams as well. And our resumes are usually full of metrics that show how we accelerated our clients. ----- If you want to learn more about how a productivity coach can help level up your organization, or get an ROI on your investments into agile, SAFe, or business agility initiatives, I offer a free first hour call. Send me a direct message to set it up! You will get to ask your toughest questions, get some great answers, and understand what it is like to engage a coach with my level of experience and insight. I've led 21 large scale transformations, participated in a total of 29 and have captured reusable patterns across all of them. I look forward to our first talk!

49

53 comentarios

Excited to share that Grokipedia has a dedicated page for Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions by Scott M. Graffius. Published in 2016, “Agile Scrum” provides clear, visual, step-by-step guidance for implementing Scrum, the most widely used Agile approach to the development and delivery of products and services. The book helps teams deliver products and services in short cycles, adapt rapidly to change, accelerate time-to-market, and drive continuous improvement and innovation. The book has been well received, earning an average rating of 4.8 out of 5 stars on Amazon, with praise for its clarity, organization, user-friendly tone, and helpful visuals. It has won several awards, and it was recognized by BookAuthority as one of the top books on Agile. Content from the book has been cited by businesses, professional associations, government agencies, universities, media outlets, and publications around the world. This recognition from Grokipedia adds to Scott M. Graffius’ broader body of work — through which he has generated over $2.51 billion in business value for organizations across technology, entertainment, finance, healthcare, and other sectors — and underscores his continued commitment to helping individuals and teams achieve breakthrough results. The Grokipedia entry reflects the book’s enduring relevance. → Explore the Grokipedia page for “Agile Scrum”: https://lnkd.in/gK_nGDpY . → Learn more and view purchase options for "Agile Scrum" on Amazon: https://amzn.to/4soYw3i . #Agile #Scrum #ProjectManagement #Grokipedia

5

64% of knowledge workers agree that their team is constantly being pulled in too many directions. 70% of knowledge workers agree that it would be easier to make progress if they had fewer, more specific goals. OKRs are a lightweight approach to get alignment top to bottom. Atlassian's new Goals feature is a great way to start. Find out more in our 4-hour micro-credential tomorrow. https://lnkd.in/eE4F4Ums

14

2 comentarios

"An SM is like a pilot ... An RTE is like an air traffic controller... A pilot is not a junior controller, a controller is not a senior pilot" Don't think I've ever heard a better explanation.

3

The Era of "Human-in-the-Loop" is Over. Is Your Scrum Team Ready for the Agentic Economy? I have just updated First Principles in Scrum (Vol. 3) with a critical new chapter: The Physics of Abundance. The data is clear: We are moving toward a Machine-to-Machine (M2M) economy where AI agents don't just assist us—they are the workforce. But this hyper-velocity workforce faces a fatal bottleneck: The Global Banking System. Imagine a Super-Intelligence capable of executing 10,000 decisions per second, forced to wait 3 days for an ACH transfer. It is like putting a speed limiter on a Formula 1 engine. In this new chapter, I breakdown the infrastructure required for the machine economy: 🔹 AI provides the 100x Kinetic Energy. 🔹 Scrum@Scale provides the Coordination Protocol to align the swarm. 🔹 Bitcoin provides the Thermodynamic Floor for instant, permissionless settlement. We also cover the Execution Gap: A recent MIT survey shows that 95% of enterprise AI pilots are failing to deliver financial value because they force AI to use human tools. The 5% who give their agents Economic Autonomy (programmable money) are building an exponential advantage. If your competitor's agents are coding 24/7 and settling payments in milliseconds, and you are waiting on a wire transfer, you are mathematically eliminated. Download the updated edition on Leanpub to read the full chapter. https://lnkd.in/e8Ni38aQ #Scrum #Agile #AI #Bitcoin #FutureOfWork #Leanpub #Management

60

21 comentarios

Psychological safety is the foundation of true agility. Because without it, teams might follow Scrum—but fear honesty. I once coached a team that checked every Scrum box. Daily Scrum? ✅ Sprint Planning? ✅ Retrospective? ✅ But every event felt… flat. No one challenged ideas. No one raised blockers. Everyone just played it safe. It wasn’t a process issue. It was a safety issue. I started asking quiet questions, holding 1:1s, observing reactions. The truth emerged: “We don’t speak up because we’re not sure how it’ll be received.” That was the real impediment. So we made changes—team agreements, anonymous feedback, and most importantly, follow-through. Slowly, the silence gave way to real conversations. And with it came improvement, innovation, and true agility. 🎯 INTERVIEW TIP: If asked, “How do you create a high-performing Scrum Team?”, Say: “I start by building psychological safety—because agility can’t grow where fear exists.” 💡 Ask this at your next Retrospective: “What’s one thing we’re not saying out loud—and why?” Scrum is the engine. Safety is the fuel. 𝘐 𝘴𝘩𝘢𝘳𝘦 𝘤𝘰𝘯𝘵𝘦𝘯𝘵 𝘥𝘦𝘴𝘪𝘨𝘯𝘦𝘥 𝘵𝘰 𝘩𝘦𝘭𝘱 𝘺𝘰𝘶 𝘣𝘶𝘪𝘭𝘥 𝘢 𝘱𝘶𝘳𝘱𝘰𝘴𝘦𝘧𝘶𝘭 life & 𝘤𝘢𝘳𝘦𝘦𝘳. 𝘍𝘰𝘭𝘭𝘰𝘸 Anand Pandey 𝘪𝘧 𝘺𝘰𝘶 𝘭𝘪𝘬𝘦 𝘴𝘶𝘤𝘩 𝘤𝘰𝘯𝘵𝘦𝘯𝘵. #coachanand #strategyforsuccess

18

4 comentarios

Involvement versus Commitment: The Pig and Chicken Paradox in Agile There is a classic Agile story about a bacon-and-egg breakfast. The chicken is involved. The pig is committed. The chicken contributes the eggs. The pig becomes the bacon. It is a simple metaphor, but it carries a powerful leadership lesson for project teams, Scrum teams, PMOs, and organizations trying to deliver real value. Many people are involved in a project. They attend meetings. They give opinions. They provide updates. They comment on risks. They participate when convenient. They support the initiative from a distance. That is involvement. And involvement matters. But high-performance teams are not built only with involvement. They are built with commitment. Commitment means ownership. Commitment means the team does not simply ask, What is my task? They ask: What outcome are we responsible for delivering? In Agile, this distinction is critical. A committed team does not hide behind activity. A committed team does not confuse busyness with value. A committed team does not wait passively for perfect requirements. A committed team does not throw problems over the wall. A committed team does not say, “That is not my job,” when the Sprint Goal is at risk. A committed team collaborates deeply. The leadership question is not whether people are attending the meeting. The real question is: Who is truly committed to the outcome? In my experience, successful projects are rarely saved by perfect plans. They are saved by committed people. People who step forward. People who own the problem. People who tell the truth early. People who protect value. People who understand that delivery is not a spectator sport. Involvement helps. Commitment transforms results. What do you see more often in your organization: involvement or real commitment? #Agile #Scrum #ProjectManagement #Leadership #PMO #PMP #HighPerformanceTeams #ValueDelivery #AgileLeadership #ProjectLeadership #DrTonyPrensa767

19

1 comentario

The Backlog Admin Trap: Why Your Product Owner Isn’t Driving Strategic Value We often tell Product Owners they are the “CEO of the product,” accountable for maximizing value. But in practice, many end up trapped in backlog administration—writing stories, updating tickets, and endlessly grooming details. Does this sound familiar? Your PO is excellent at managing Jira, but struggles to articulate the “Why” behind features. They spend little time with customers, market research, or senior stakeholders. Instead, they get buried in the mechanics of delivery. The result is predictable: the team turns into a feature factory. They ship outputs, not outcomes. Business impact becomes an afterthought, while velocity becomes the false measure of success. A true Product Owner is not a backlog clerk—they are a strategic leader. Their job is to: - Relentlessly define customer problems worth solving. - Validate opportunities with market data and customer conversations. - Prioritize based on economic impact, not personal preference. - Connect strategy to execution, ensuring the team’s work drives measurable business results. Value is not created in Jira. Value is created in the market. So, here’s the question: Is your Product Owner driving strategy and customer impact, or are they trapped in the backlog admin role? #ProductOwner #ProductManagement #AgileLeadership #BusinessAgility #ValueDelivery #OutcomeDriven #AgileTransformation

25

2 comentarios

Continuing the series of author reading The Innovation PROCESS Book over at my new company page for Global NP Solutions. Check out the new page and follow along with Episode 14 discussing the phases and tools for Scrum Product Development. Remember you can get your copy of The Innovation PROCESS Book at Amazon to follow along and catch up on the YouTube series for Part 1 Waterfall Product Development and Chapters 7 and 8 on Agile New Product Development. https://lnkd.in/gugKR_vC

2

🚀 Agile transformation starts with a decision—not just a framework. Too often, organizations expect agility to emerge simply by introducing ceremonies, roles, or new terminology. But an Agile transition doesn’t truly begin until the organization makes a conscious decision to change how it thinks and operates. 🧠 Agility requires more than adopting a methodology. It requires an organizational commitment and a shift in mindset. 🔄 When leadership clearly conveys that agility is a strategic choice—and backs it up with action—the results go far beyond process changes. Teams begin to accept the methodology, but more importantly, they start to internalize the principles behind it. 📈 That’s when Agile begins to influence how decisions are made, how collaboration happens, and how value is delivered. 🤝 For this to happen, the organization must embrace the transformation and support it at every level. Mindset change cannot live in a single team or department. It needs to be distributed across all layers of the organization. 🌐 This is where transformation agents play a critical role. 🧭 These individuals help structure the change, guide teams and leaders, and influence the organization to adapt its ways of working. They help bridge strategy and execution, ensuring that both the methodology and the mindset are truly adopted. Agile transformation is not something you install. ⚙️ It’s something the organization must actively choose, support, and cultivate. 🌱 And when that happens, agility becomes more than a framework—it becomes part of the organization’s DNA. 🧬

2

Agile practices are designed to push authority toward the development team. If that's not happening in your "Agile Transformation" then something has gone severely wrong. 0:31 Something has gone wrong 1:03 A few statements from agilemanifesto_org 1:54 Those statements make it obvious don't they? 2:13 Let's think about the business world in the 90s 3:08 Strict bureaucracies and hierarchical command 3:38 Command control piecework specialization centralization 3:56 It was dehumanizing 4:20 Ideas like scrum and crystal and openagile resonated 4:41 Limited by the micromanaging nature of the establishment 4:53 Tension between transparency and scrutiny, autonomy and anarchy 5:28 Agile practices are designed to push authority toward the development team 6:12 Self-managing teams are supported, transparency is expected 6:44 Transparency should lead to empowerment 7:08 But developers can feel exposed 7:23 Scrum might be hijacked for surveillance 7:44 Measure outcomes, not activity 7:57 Thanks

7

1 comentario

🎥 Agile Coaching Exchange – Back to Basics Series - LeSS Video Live on You Tube 🎥 What if the best way to scale Agile is actually to scale… leSS? In this #Agile #Coaching Exchange Back to Basics session, 🌴 Rickard Jones 🌴explored the principles behind Large-Scale Scrum (LeSS) and challenged many of the assumptions organisations make when attempting to scale Agile. Rather than adding more roles, more processes, more tooling, and more coordination layers, Rickard looked at why successful scaling often comes from simplifying the organisation, reducing dependencies, and focusing relentlessly on customer value. Topics covered included: 💡Descaling over scaling 💡Why “Agile versions” of traditional hierarchies often reduce agility 💡The power of one Product Owner and one Product Backlog 💡Organisational design and structural change in LeSS 💡Removing complexity, silos, and organisational “muck” A great session for anyone frustrated with “Agile-in-name-only” transformations and interested in a more pragmatic and evidence-based approach to organisational agility. 📺 Watch the session here: https://lnkd.in/esgqqvu7 🔥 Last chance for LeSS Basics 🔥 This also links perfectly with the news that Agile Affinity’s Certified LeSS Basics course on 20th March will be the final time they run this class before LeSS retires it. If you’ve been considering taking the course, now’s the time to grab a place. #Agile #LeSS #Scrum #ScalingAgile #AgileCoaching #Lean #OrganisationalDesign #ContinuousImprovement

2

1 comentario

Retrospectives are a critical practice for teams to engage in, as they offer a space for reflection and improvement. One fantastic resource available for free is the "Sails and Anchors" retrospective template on Miro . This straightforward template provides an easy yet effective way for teams to reflect on their performance and identify areas for improvement. The 'Sails and Anchors' template facilitates a meaningful discussion among team members about what went well (the wind in our sails) and what might be holding them back (the anchors). By encouraging everyone to contribute one sticky note for each area, the template ensures that all voices are heard and diverse perspectives are considered when identifying successes and challenges. Additionally, the "Sails and Anchors" template comes with a dot voting tool, which enables teams to prioritise specific actions for improvement. After the retrospective discussion, the team can use dot voting to identify the most crucial points raised and determine which actions to focus on moving forward. This allows for quick and efficient decision-making, ensuring the retrospective leads to actionable insights. It's important to remember that the value of retrospectives lies in the actions taken afterwards. By using a tool like the Sails and Anchors template, teams can ensure that their reflections lead to tangible improvements in their performance. Engaging in retrospectives is not just about reflecting on past experiences; it's about using those reflections to drive positive change within the team. This is where the true power of the Sails and Anchors template lies. This resource allows teams to begin their journey towards empowerment and continuous improvement. The "Sails and Anchors" retrospective template provides a structured and effective way for teams to engage in reflective discussions and take meaningful actions based on their insights. With this tool, teams can unlock their full potential and work towards achieving their goals. The free "Sails and Anchors" retrospective template on Miro offers teams a valuable resource for conducting retrospectives and driving positive change. This template empowers teams to enhance their performance and collaborate effectively by encouraging thoughtful reflection and providing a mechanism for prioritising actions. Take advantage of this opportunity to leverage retrospectives for continuous improvement and team empowerment. If you would like to experiment with the "Sails and Anchors" retrospective template and explore Miro's capabilities for retrospectives, visit the following link: https://lnkd.in/eqWcWSDZ

3

1 comentario

Agile Coaching in the Enterprise: Mastering Complexity Through Systems Thinking and NLP Coaching A conversation with Bernie Maloney https://lnkd.in/dV_sW-7u #agile #lean #kanban #scrum #lean #leadership @duarte_Vasco

4

ARE YOU REALLY RUNNING SAFe—OR JUST CALLING IT “SCALED SCRUM”? Swipe through the carousel to see • The eight SAFe events every Scrum Master must own or join • Key differences between team-level and train-level facilitation • One-line reminders you can take straight into your next sprint Want to practice each ceremony with live boards, breakout rooms, and instant feedback? Go for 100 percent practical SAFe workshop digital recording toolkit. Here is the details - https://lnkd.in/gpS_qQ8r Drop your hardest SAFe question in the comments, hit Like if the carousel clarifies the chaos, and repost so your network can step up their game too. See you inside the workshop. Note - Daily Scrum called to "Team Sync," Scrum of Scrums is transitioning to "Coach Sync in SAFe 6.0

129

14 comentarios

Agile Coaches Can’t Fix What Leadership Keeps Breaking 🚨 Too often, coaches are asked to “fix the teams.” The real issue? Leadership behaviors that undo progress. 👉 Coaches can guide. 👉 Teams can adapt. 👉 But if leaders send mixed messages, shift priorities, or micromanage—Agility stalls. True change starts at the top. Align leadership actions with Agile values, or no coach in the world can help! Link in first comment! #Agile #Leadership #BusinessAgility #Scrum

6

1 comentario

Spanish edition blog by PST Alex Ballarin: 5 prompts que potenciarán tu trabajo como Scrum Master - https://ow.ly/AJvL50YAVVr #ScrumMaster #AI #Agile

10