by Stefan Wolpers|FeaturedAgile and ScrumAgile Transition
TL; DR: Why Too Much Transparency Can Have a Detrimental Effect
While transparency is often touted as essential in Agile, too much can have negative consequences. Oversharing can lead to micromanagement, misinterpretation, and loss of trust within the team. Examples include excessive scrutiny during Daily Scrums, misreading progress metrics, and creating a blame culture that erodes psychological safety.
Strategic opacity may sometimes be necessary to protect the team’s autonomy and maintain a healthy dynamic. Be transparent, but not at the expense of the team’s independence and well-being.
Scrum is just a tool; your job is to solve real customer problems and deliver value. Stop focusing on perfecting frameworks and start prioritizing outcomes that matter. It’s time to reassess what truly drives your success, particularly given the challenging business environment.
TL; DR: Hands-on Agile #62: From Backlog Manager to Product Manager w/ David Pereira
What does product success mean? In this energizing Hands-on Agile Meetup, David Pereira talked about the challenges of being a product manager and how to move from managing the Product Backlog to driving value. You can expect provoking thoughts, actionable insights, and a bit of unconventional product management.
TL; DR: Top Five Rookie Mistakes by Self-Proclaimed Scrum Masters
Are you struggling with imposter syndrome as a new Scrum Master? Avoid five common rookie mistakes Scrum Masters make. Instead, discover how to set clear Sprint Goals, build trust, balance metrics, and empower your team to make independent decisions.
Don’t let early missteps define your journey. Learn from these mistakes and transform them into stepping stones towards mastery. By understanding and addressing these pitfalls, you’ll gain confidence, enhance your leadership skills, and truly embody the principles of Scrum.
This article provides actionable insights and practical exercises to help you grow from a beginner into an effective and respected Scrum Master.
Combining the roles of Product Owner and Scrum Master in one individual is a contentious topic in the Agile community. A recent LinkedIn poll, see below, revealed that 54% of respondents consider this unification useless, while 30% might accept it in rare moments.
This blog post explores the implications of merging these roles, emphasizing the importance of distinct responsibilities and the potential pitfalls of combining them. We also consider exceptions where this approach might be temporarily justified and analyze the insightful comments from industry professionals.
by Stefan Wolpers|Agile and ScrumAgile TransitionWorkshops
TL; DR: Introducing the “Anti-Patterns Canvas”
Join me in developing the Anti-Patterns Canvas, a dynamic and free tool that extends the insights of the “Scrum Anti-Patterns Guide” book. Share your expertise through the survey, see below, and test-drive tools, practices, and exercises through a series of upcoming Hands-on meetups. In other words, help me create a resource that enhances agile practice and value creation.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
3rd Party Cookies
This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.
Keeping this cookie enabled helps us to improve our website.
Please enable Strictly Necessary Cookies first so that we can save your preferences!
