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.
How to identify an agile organization is — given the market-entry of the late majority to agile development practices – nowadays more important than ever: No matter how large the pay cheque, life is just too short to spend it on unfulfilling projects!
I can support your quest as an agile practitioner for the next suitable employer or client with this article, covering the three different phases of gathering information on the agile maturity level of an organization.
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.