TL;DR: Webinar Sprint Review Anti-Patterns
The ninth Hands-on Agile webinar sprint review anti-patterns addresses twelve anti-patterns of the sprint review—from death by PowerPoint to side-gigs to none of the stakeholders cares to attend.
📅 Agile Camp Berlin 2019: April 26–27, 2019
Save the Date: Agile Camp Berlin 2019
The Agile Camp Berlin 2019 will happen from April 26 to April 27, 2019 and the Agile Camp Berlin 2019 venue will be the Evangelische Schule Berlin Zentrum right in the middle of Berlin.
Speaking Truth to Power — Taking A Stand as an Agile Practitioner
TL;DR: Speaking Truth to Power
Do you need an emergency fund as a change agent—whether you are acting as Scrum Master, Product Owner or agile coach—because conflict is inevitable, but change is not?
In my experience, speaking truth to power, pointing at the emperor’s new clothes and the reality in the trenches, is necessary a trait for every change agent — including Scrum Masters and agile coaches — in organizations that lack strong leadership.
Learn more, how this form of professional honesty can backfire when the incumbents, privileged by the existing system, strike back.
Hiring: 38+9 Scrum Master Interview Questions to Avoid Agile Imposters [PDF and Video]
Scrum Master Hiring: Demand Creates Supply and the Job Market for Agile Practitioners is No Exception
Maybe, “Agile” in general is a management fad and not trend at the moment. But what we can say for sure is that Scrum has become very popular for software development purposes. A seasoned Scrum master is nowadays in high demand. And that demand causes the market-entry of new professionals from other project management branches, probably believing that reading one or two Scrum books will be sufficient.
If you are looking to fill a position for a Scrum master (or agile coach) in your organization, you may find the following 38+9 interview questions useful to identify the right candidate. They are derived from my ten years of practical experience with XP as well as Scrum, serving both as Product owner and Scrum master as well as interviewing dozens of Scrum master candidates on behalf of my clients.
Webinar #8: Scrum Master Anti-Patterns [Video]
TL;DR: Webinar Scrum Master Anti-Patterns
The eighth Hands-on Agile webinar Scrum Master Anti-Patterns addresses twelve anti-patterns of your Scrum Master—from ill-suited personal traits and the pursuit of individual agendas to frustration with the team itself.
Solving Impediments as a Team
TL;DR: Solving Impediments as a Team
The main message of the retrospective was clear: there are too many interruptions by stakeholders and the senior management. The interruptions impeded the flow of work through the team. Consequently, achieving the sprint goal had been at risk several times in the past. Moreover, the team missed the sprint goal twice recently. Solving impediments as a team has become a necessity.
Learn more on how to tackle impediments as a team by running experiments and iterating on the solution.
Scrum Master Duties, Serving a Single Team (Survey Results)
TL;DR: Scrum Master Duties, Serving a Single Team
Scrum Master Duties: supposedly, a great scrum master serves only one scrum team — that's at least a popular narrative in the scrum community. Nevertheless, there is also a loud voice that doubts that approach: what would you do the whole day - with a single team? Aren't they supposed to become self-organizing over time? And if so, does the scrum then need a scrum master 24/7?
As I worked for years as a product owner on scrum teams without a dedicated scrum master-which was working well-I was curious to learn more about that question, too. Hence I ran a survey in late June and early July 2018, the results of which are presented here.
In total, 261 scrum masters participated in this non-representative survey in the two weeks before July 5th, 2018. 19 participants chose not to provide their consent to Google processing and to store their answers. Hence their contributions were deleted, resulting in a sample size of 242 responses.
Scrum Stakeholder Anti-Patterns
TL; DR: Scrum Stakeholder Anti-Patterns
Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in scrum stakeholder anti-patterns which easily can impede any agile transition.
Agile Failure Patterns in Organizations 2.0
TL;DR: Agile Failure Patterns — Why Agile is Simple and Complex at the Same Time
Agile failure seems to be increasingly more prominent nowadays despite all the efforts undertaken by numerous organization embarking on their journeys to become agile.
The funny thing is: Who would disagree that the four core principles of the Agile Manifesto —
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
— are derived from applying common sense to a challenging problem? Moreover, that the application of those principles might be suited to fix numerous organizational dysfunctions and reduce an error-prone and complex social setting to maybe just a complicated one?
Scrum Master Anti-Patterns — 20 Signs Your Scrum Master Needs Help
TL;DR: Scrum Master Anti-Patterns
Scrum Master Anti-Patterns: The reasons why scrum masters violate the spirit of the Scrum Guide are multi-faceted. They run from ill-suited personal traits and the pursuit of individual agendas to frustration with the team itself.
Read on and learn in this final post on scrum anti-patterns how you can identify if your scrum master needs support from the team to up his or her agile game.
28 Product Backlog and Refinement Anti-Patterns
TL;DR: 28 Product Backlog and Refinement Anti-Patterns
Scrum is a practical framework to build products, provided you identify in advance what to build. But even after a successful product discovery phase, you may struggle to make the right thing in the right way if your product backlog is not up to the job. Garbage in, garbage out – as the saying goes. The following article points at 28 of the most common product backlog anti-patterns – including the product backlog refinement process – that limit your Scrum team’s success.
Hiring: 42 Scrum Product Owner Interview Questions to Avoid Agile Imposters
TL;DR: 42 Scrum Product Owner Interview Questions That Will Benefit Your Organization
This second publication in the Hands-on Agile Fieldnotes series provides 42 questions and answers for the Scrum Product Owner interview.
Co-authored with Andreea Tomoiaga, 42 Scrum Product Owner Interview Questions to Avoid Hiring Agile Imposters represents the most important learnings of our more than 20 years combined hands-on experience with Kanban, Scrum, XP, and several product discovery frameworks. We have worked as Scrum Product Owners, Scrum Masters, agile coaches, and developers in agile teams and organizations of all sizes and levels of maturity.
We have each participated in interviewing dozens of Scrum Product Owner candidates on behalf of our clients or employers. The questions and answers herein are what we have learned.
Agile Metrics — The Good, the Bad, and the Ugly
TL;DR: Agile Metrics
Suitable agile metrics reflect either a team’s progress in becoming agile or your organization’s progress in becoming a learning organization.
At the team level, qualitative agile metrics typically work better than quantitative metrics. At the organizational level, this is reversed: quantitative agile metrics provide better insights than qualitative ones.
Food for Agile Thought #172: Taylorism & Agility, Agile Planning Myths, Product Discovery, Leadership in an Agile World
Food for Agile Thought’s issue #172—shared with 20,138 peers—focuses on Taylorism Agility and its contribution to imposing ‘agile,’ why agility and governance do not have to be mutually exclusive, and busts several agile planning myths.
We also refresh our memory why the engineers need to participate in product discovery, how you prepare for product experiments, and what this whole customer journey mapping is about.
Lastly, we learn what good leadership has to do with intrinsic motivation in the trenches.
This is the last edition of the ‘Food for Agile Thought’ newsletter in 2018. Thank you so much for your feedback and continued support; we will be back on January 6th, 2019, with issue #173.
Enjoy the rest of 2018!
Did you miss last week’s Food for Agile Thought’s issue #171?
Food for Agile Thought #171: Pushing Agile, Psychological Safety, Netflix’ Failures, Team Charter How-to
Food for Agile Thought’s issue #171—shared with 20,122 peers—focuses on pushing agile, or better its futility as ‘agile’ needs to be pulled, we analyze current trends in corporate transformation efforts, and we ask: how safe did the attendees of your last workshop feel?
We also try to learn from Netflix’ failures, we come back to technical debt and its influence on product creation once more, and we compare our problems to the most pressing issues Marty Cagan has identified in today’s product-driven companies.
Lastly, we appreciate a great recipe on how to run a team charter creation workshop.
Have a great week!
Did you miss last week’s Food for Agile Thought’s issue #170?
Food for Agile Thought #170: Agile Transformation Lessons, Agile’s 10,000-Hour Rule, UX Is a Team Sport
Food for Agile Thought’s issue #170—shared with 20,108 peers—focuses on agile transformation lessons. We learn that becoming ‘agile’ is one but not the only answer, that agile teams are no causation for business agility, and that the 10,000-hour rule applies to agile practitioners, too.
We also remind ourselves that user research is always a team sport, that NPS detractors are not necessarily bad-mouthing your product, and why there is a difference between cooperation and collaboration.
Lastly, we go back to Scrum basics and revisit the idea of delivering a ‘done’ product increment every single Sprint—without making excuses.
Have a great week!
Did you miss last week’s Food for Agile Thought’s issue #169?
