What we’re about
Meet other Agile Practitioners from all over the world to discuss the latest challenges in our trade. Whether you are completely new to Scrum or an established Agile practitioner, certified or not, meet people like yourself in the comfort of your home or office. Suggest your discussion topics. Enjoy industry leaders speaking at our events. We'll be using an "inspect and adapt" approach to be sure our MeetUp is exactly what you would like it to be.
Upcoming events (1)
See all- One Of The Best Maturity Metrics: Why should DoR "shrink" and DoD expand?Link visible for attendees
When a team is not able to deliver a product increment (PSPI) at the end of a sprint, we should not automatically assume that its developers poorly estimated, refined or planned their work. There could be other reasons. In fact, there are many teams that can meet their own Definition of Done (DoD) pretty consistently, yet not able to ship, at the end of the sprint.
What could be other reasons to not being able to deliver PSPI?
The answer might be hidden in a team’s maturity of DoD. How complete is DoD? Does it include design and development only? Or does it also incorporate a peer code review, integration, packaging and staging? How about customer documentation, marketing materials? What kind testing is included in a team’s DoD: unit, integration, system, performance, stability, usability, stress, monkey, smoke…?
While some of the above listed steps could be very well within a team’s ability, some others – may not, and it could be due to organizational (NOT teams’) limitations/restrictions. These restrictions are caused by organizational design boundaries and areas of control. For example, traditionally, some (most?) downstream activities are handled by separate teams: testing, integration and deployment have been historically handled by another department. Similarly, all relevant operational work might be handled by another organizational structure, sometimes ironically called “DevOps team”. This makes a team’s DoD weak and low in maturity. Anything that a team cannot complete because of organizational design limitations/restrictions could be labeled as “Un-Done” work. Historically, component teams have had much less inclusive (low maturity) DoD and pretty extensive “Un-Done” work then feature teams. It would be very difficult for a component team to deliver a PSPI by the end of the sprint, because such activities, as integration with other components, full end-to-end testing etc., would be excluded from DoD.
Recommended reading:
https://www.keystepstosuccess.com/2022/03/following-ftam-by-expanding-dod-vs-becoming-a-hostage-to-traditional-org-structure/
