Keith Erik Wilson’s Post

Isn't agile supposed to be... well... agile? 🤔 If your organizationally-required practices like sprint metrics, sprint time boundaries, ceremonies, daily scrum questions, or anything else are getting in the way of delivering value to the customer BE AGILE and change them 🙌. All of the trappings of scrum exist ONLY to deliver quick, predictable, and regular value to customers. For example, the Daily Scrum is the beating ❤️ of a scrum team - it's the collaborative start to a good day, or the status-update-y start of a bad day. Fellow scrum masters, the Daily is for the team, not for us, so let the team lead and adapt however the team needs. You're a *servant leader*, make sure you serve the team and the customer however you can. Scrum is an adaptable framework designed to deliver value to customers quickly and iteratively. If this isn't happening, you're failing 💀 Alternatively, if you have carryover, your metrics aren't perfect, or your ceremonies are non-traditional, but you're delivering consistent value to the customer and meeting sprint goals, you're WINNING 🏆 Be value-delivery obsessed, focused on serving the team, and adaptable, and you'll see the fruit 🍉 of your labor. Every time I've seen a team or an organization fed up with agile, it's really just bad agile 🛑

In January 2021, I wrote an article for Serious Scrum called "Agile is dead, long live pimped frameworks". Strangely enough, the article is more relevant today than in 2001. I examined the shifting perceptions around Scrum and Agile, claiming them dead. I discussed that we may witness a natural evolution rather than a downfall.  My theory was rooted in the theory of early adopters and the Hype lifecycle, suggesting that agile principles remain relevant in our rapidly changing world. A reason why Agile fails lies in believing Scrum is its mechanics. The article highlights the tendency towards 'cargo-culting' in Scrum practice, where the focus is on the 'how' rather than the 'why', leading to a superficial application of its principles. As Scrum becomes mainstream, there will be no competitive advantage, yet this scrutiny can signify its evolution. What we see may not be the abandonment of agile but a move towards customized frameworks that align with organizations' unique cultures, structures, and needs. Where practitioners progress from merely executing practices (Shu) to adapting principles creatively (Ri). The future of Agile could be 'pimped' frameworks that are co-created by the teams using them, ensuring they serve the organization's specific context while retaining the agility to adapt and evolve. To abandon the one-size-fits-all approach. The article is here https://lnkd.in/d4nCT2Fx 

🌟 Exciting News! 🌟 🚀 Delighted to share my latest article on LinkedIn: "Unleashing the Power of Scrum in Agile: Navigating the Agile Universe" 🚀 In this engaging piece, I dive deep into the world of Agile and Scrum, demystifying these dynamic methodologies and exploring how they can revolutionize project management. From defining the essence of Scrum as a potent Agile implementation method to unraveling the key distinctions between Agile and Scrum, this article is your go-to guide for mastering the art of Agile project management. But wait, there's more! I've sprinkled in real-world examples, engaging anecdotes, and relatable analogies to make the concepts come to life. Whether you're a seasoned Scrum Master or just starting your Agile journey, there's something for everyone in this article. So, if you're ready to unlock the secrets of Agile success and discover the transformative power of Scrum, hop on over to LinkedIn and give it a read! Don't forget to like, comment, and share your thoughts—I can't wait to hear what you think! Read the article here: https://lnkd.in/gqzRRKE4 Let's embark on this Agile adventure together—see you there! 🚀 #Agile #Scrum #ProjectManagement #LinkedInArticle #AgileJourney

In the evolving agile landscape, Scrum's relevance is undisputed, yet its application remains a topic of critical discussion. Scrum, at its core, is about adaptability and rapid value delivery. However, in practice, we see many teams struggle with its implementation. We know the challenge lies not in Scrum's framework, but in its adaptation to diverse project environments. Often, teams rigidly adhere to Scrum events without understanding their purpose, leading to a mechanical process devoid of true agile spirit. The key issue: A misunderstanding of Scrum's flexibility. It's not a set of inflexible rules but a guide to navigate complexity. Successful Scrum teams adapt these guidelines, blending them with their unique workflows and project needs. Another critical point: Scrum is often seen as a silver bullet. It's not. Scrum is effective in certain contexts, but not a one-size-fits-all solution. Recognizing when to use Scrum and when not to is crucial. As agile professionals, our role is to demystify Scrum. We must guide teams and organisations in embracing its principles while adapting its practices to suit their specific challenges, foster a culture where Scrum is understood, not just implemented.

Agile. We all have heard the term, but do we all understand it the same way? Picture a Rubik's cube. Each side, a different color and pattern. That's Agile for you. Each of us sees and experiences it differently based on our perspective, our past interactions, and our current needs. One might think of scrum, kanban, or lean when they hear Agile. Others might focus on the values and principles from the Agile Manifesto. Some might even associate it with specific practices like daily stand-ups or retrospectives. But are any of these perspectives wrong? Not necessarily. The Agile space is a complex ecosystem, filled with diverse interpretations and implementations. This diversity can lead to misunderstandings, especially when we focus more on labels rather than the underlying principles. We might find ourselves in endless debates on whether something is 'truly Agile' or not, instead of focusing on delivering value to our customers. In the Agile space, we should aim to embrace this diversity and encourage dialogue. Instead of arguing about definitions, let's focus on understanding each other's perspectives and learning from them. Next time you discuss Agile, remember the Rubik's cube. Seek to understand the other person's perspective and share your own. You might find that you have more in common than you thought. Don't let labels get in the way of collaboration. Let's foster a mindset of continuous learning and improvement.

Improve your team's concern for quality! ✅ There is no point in Agile methodologies like Scrum when the work that teams deliver is of low quality. So it is important that teams develop a shared understanding of what high-quality means in their context. In Scrum, this shared understanding is captured in a "Definition of Done". First, the best strategy is to start conversations in teams about quality: 🤔 When is your work of high quality? 🤔 How do we know we're not gold-plating? 🤔 How does our understanding of quality matches the wider organization's understanding of quality? 🤔 What can be done or automated to ensure that level of quality more consistently? 🤔 What practices and techniques can increase quality? Second, actual stakeholders - like customers and users - play an important role here. They are often in the best position to evaluate the quality of the work that comes out of teams, so they should have a strong say in quality guidelines. Actions to start small and simple are: 1️⃣ Schedule a 60-minute workshop next Sprint to make sure that your Definition of Done captures what high-quality means to you. Anyone who cares about this can attend. 2️⃣ Investigate 3 critical bugs 🐞 that happened in recent Sprints/iterations and work together to identify a small step forward to prevent similar bugs in the future. Update your Definition of Done and work agreements as needed. 3️⃣ Interview 3 important stakeholders to learn from them how you could improve the quality of your product. What is your experience with "concern for quality" ❓ What recommendations do you have to help a team start improving❓ Concern for quality is one of the 20+ factors we measure to determine Agile & Scrum team effectiveness. Based on the results, teams receive evidence-based feedback on how to start improving. Why don't you give the Agile/Scrum Team Survey a try? We offer a free version focused on individual teams and a paid version that shows aggregated results of multiple teams. Check: http://bit.ly/2Pth7gu

Improve your team's concern for quality! ✅ There is no point in Agile methodologies like Scrum when the work that teams deliver is of low quality. So it is important that teams develop a shared understanding of what high-quality means in their context. In Scrum, this shared understanding is captured in a "Definition of Done". First, the best strategy is to start conversations in teams about quality: 🤔 When is your work of high quality? 🤔 How do we know we're not gold-plating? 🤔 How does our understanding of quality matches the wider organization's understanding of quality? 🤔 What can be done or automated to ensure that level of quality more consistently? 🤔 What practices and techniques can increase quality? Second, actual stakeholders - like customers and users - play an important role here. They are often in the best position to evaluate the quality of the work that comes out of teams, so they should have a strong say in quality guidelines. Actions to start small and simple are: 1️⃣ Schedule a 60-minute workshop next Sprint to make sure that your Definition of Done captures what high-quality means to you. Anyone who cares about this can attend. 2️⃣ Investigate 3 critical bugs 🐞 that happened in recent Sprints/iterations and work together to identify a small step forward to prevent similar bugs in the future. Update your Definition of Done and work agreements as needed. 3️⃣ Interview 3 important stakeholders to learn from them how you could improve the quality of your product. What is your experience with "concern for quality" ❓ What recommendations do you have to help a team start improving❓ Concern for quality is one of the 20+ factors we measure to determine Agile & Scrum team effectiveness. Based on the results, teams receive evidence-based feedback on how to start improving. Why don't you give the Agile/Scrum Team Survey a try? We offer a free version focused on individual teams and a paid version that shows aggregated results of multiple teams. Check: http://bit.ly/2Pth7gu

"📚 Excerpt from 'The Agile Scrum Revolution': 💡 'While many frameworks offer a cookie-cutter solution, Agile Scrum understands that each project is a unique recipe that demands its own spice mix. With its iterative cycles and regular feedback loops, Scrum ensures that the end product reflects the real needs of your stakeholders. It moves you from a mindset of delivering products to crafting solutions. This is not project management; this is project mastery.' 💡 Feel the need for a professional shift? Transform your approach with the comprehensive guide, 'The Agile Scrum Revolution.' Get your copy now! 👉 https://rb.gy/ll42t

Meetup: Let's Invent Rebellious Acts To Make Agile (Or Scrum) Work In Your Organization 💥 For an Agile Coach or Scrum Master, sparking change is a fundamental part of your role. It’s up to you to help create an environment where teams - and organizations as a whole - can be successful. There are various ways to ignite change. One of them is by embracing a rebellious attitude 😎. A rebellious attitude to challenge the status quo. During this meetup, we’ll work together to identify examples of rebellious acts. Some acts will only require a small bit of courage, others might demand all your bravery! 💪 Some examples are: 💥 Stop using meaningless, output-focused metrics (purpose: shift the focus towards outcome-focused metrics) 😎 Don't share mandatory digital Sprint reports (purpose: check if anyone actually reads them, invite them to the Sprint Review) 💥 Break free from a standardized company-wide Sprint rhythm (purpose: choose a rhythm that suits the team) 😎 Archive 50% of your Product Backlog (purpose: minimize waste and administration) 💥 Claim a team space in a ‘work from anywhere organization’ (purpose: encourage teamwork and improve team dynamics) 😎 Switch from Scrum to Kanban (purpose: don't work in iterations, focus on the flow of value) 💥 Don’t join the Daily Scrum as a Scrum Master (purpose: see how self-organizing your team is) I'm sure that together we can identify way more examples! If this proves as a success, Christiaan Verwijs and I might turn all the ideas into a nice card deck! Interested in joining? Sign up here: http://bit.ly/2StU2Im

📚 Excerpt from 'The Agile Scrum Revolution': 🌟 "In a world that's rapidly changing, clinging to traditional project management styles can be the anchor that sinks your ship. Agile Scrum isn't just an approach; it's a lifeline thrown to project managers navigating through the stormy seas of modern-day business. It's about quick adaptability, fostering team synergy, and focusing on delivering real value, not just ticking off tasks. With Agile Scrum, you're not just surviving the project chaos; you're mastering it. So why settle for just managing when you can lead the revolution? Dive deeper and discover how Agile Scrum can be your game-changer." 🌟 Eager to transform your project management skills? Get your copy of 'The Agile Scrum Revolution' today! 👉 https://rb.gy/ll42t