In the Agile way of working and Scrum, we all talk about
team's maturity. What are the characteristics of a maturing team? In this
article, I am listing few of the characteristics of a maturing team.
- Duration of Sprint Planning Meeting start reducing due to better and better refinement of PBIs
- Refinement sessions start becoming shorter and shorter because DevTeam and Product Owner are refining Product Backlog on continuous basis
- DevTeam starts ignoring presence or absence of Scrum Master during Daily Standup
- Impromptu Retrospectives start happening
- Fifteen minutes time box for Daily Standup starts feeling long
- After Daily Standup, Scrum Master has shorter and shorter To Do list w.r.t. impediment resolution and DevTeam members are tackling impediments themselves
- PBIs are of similar size
- Burn Down chart is pretty smooth over many many Sprints
- Product Backlog is DEEP enough and holding INVESTable PBIs for next one to two Sprints
- In a truck hitting a DevTeam member thought experiment, effect on velocity in short term start reducing
- Technical debt has steady or downward trend
- Scrum Master in getting more and more involved with organizational level impediments because DevTeam is tackling team level impediments
- DevTeam is interacting with end users though work is routing via Product Owner
I am sure you have your own list. Let's share that list with
the wider community.
No comments:
Post a Comment