TL;DR: 28 Product Backlog and Refinement Anti-Patterns
Scrum is a practical framework to build products, provided you identified 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.
TL;DR: How to Make Agile Work in Fast-Growing Startups
From 2010 to 2017, I was working several years in three Berlin-based, fast-growing startups in my capacity as Scrum Master, agile coach, and Product Owner. These are my lessons learned on how to make ‘agile’ work in a fast-growing startup, and what anti-patterns to avoid at all costs.
Do you remember the good old days when the organization started with its first Scrum team? And the new engineering kid on the block was “merely” supposed to deliver a potentially shippable product increment at the end of a sprint?
The first team was to sound the bell for the upcoming change towards a learning organization. Little did we know back then about the challenges along that route. When teams 2, 3 and 4 joined, shipping a product increment at the end of a sprint became first complicated, and then complex.
It turns out that becoming agile does not only required to create (Scrum) teams. Reaping the full benefits of becoming agile, of becoming a learning organization built around software also requires changing engineering practices. Nowadays, it is all about continuous value delivery.
Happy New Year! 2016 was a very rewarding year of blogging in general and curating the ‘Food for Agile Thought’ newsletter in particular. Therefore, it is an easy decision to spend more time in 2017 on helping you to excel as an agile practitioner.
Age of Product’s roadmap 2017 is all about creating more ebooks, webinars and an online course to help you identify the right position as a Scrum Master or Product Owner. Additionally, I will also continue the ‘Agile Transition’ series on how to get started with an agile transition.
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.