back to notes

Scrum Team Maturity Assessment Elements

1. What training has the team received (formal or informal)?
Delivery Team ( i.e. Scrum basics, XP, Kanban as needed)
Product Owner (PO Training, Scrum basics as needed)
ScrumMaster (Detailed Scrum, XP training, others as needed)
Managers (Scrum Basics, Lean as needed)
2. As the product owner do you …?
Participate in Release(PI) planning
Participate in value stream Trainx Planning
Establish and participate in HIP(Hardening Innovation Planning) Sessions
Use INVEST criteria for each User Story
Refine the Product Backlog
Participate in Program Backlog Item (PBI) refinement with Delivery Team
Participate in Sprint Planning
Participate in establishing a Sprint Goal for each Sprint
Define acceptance criteria and verify the acceptance criteria are met
Accept completed User Stories throughout the Sprint
Accept completed User Stories based on an agreed-on definition of DONE
Participate in the Sprint Review
Collaborate with the Delivery Team - always available to them
Collaborate with the stakeholders
3. As the ScrumMaster do you …?
Operate as a coach and process authority
Promote team ownership and continuous improvement
Run interference for the Delivery Team
Manage impediments backlog resolution for the Delivery Teams
Facilitate refinement of the Product Backlog with team
Facilitate planning the Sprints
Facilitate establishing a Sprint Goal for each Sprint
Facilitate a properly focused, 15 min. max. Daily Scrum (Stand Up)
Facilitate a Sprint Retrospective with immediately actionable, process improvement items each Sprint.
Track daily, with a Sprint burn-down / burn-up charts
Track velocity by Sprint
Track Release burn-up chart
4.  As a member of the Delivery Team do you …?
Participate in the refinement of the Product Backlog
Participate in estimating Product Backlog Items
Participate in planning the Sprints
Participate in establishing a Sprint Goal for each Sprint
Perform Sprint execution tasks including design, build and test.
Work with the Product Owner and get rapid answers to questions as they arise
Always try to work on the highest priority incomplete Story first
Apply Pairing with (QAs, BAs or Devs.) = continuous code check
Write unit tests for all code - for high test coverage
Apply TDD - the Test First approach
Apply Continuous Refactoring - always leave code you touch more maintainable
Hold yourself and other team members to a defined standard of DONE
Participate in Sprint Reviews
Participate in Sprint Retrospectives with actionable improvements
5. Does the Delivery Team … ?
Have a cross functional feature team - with all necessary business, technical/code and QA knowledge
Have the recommended team size of 3-9
Own the code as a team vs. individual, siloed ownership
Have agreed upon CODING STANDARDS that are enforced by team on themselves
Have agreed upon standard of DONE that the team holds themselves to
Conduct Sprint Planning
Have conversations with the Product Owner (Card-Conversation-Confirmation process)
Use Acceptance Criteria
Use INVEST criteria for each User Story
Use planning poker / relative sizing for estimating User Stories
Use ideal days only for initial project estimation and planning
Have test to User Story traceability
Create Tasks for each User Story
Estimate Tasks in hours for each User Story
Conduct Daily Scrum
Conduct Sprint Review
Conduct Sprint Retrospective with improvement action items
Include Sprint Retrospective actions items in next Sprint Planning
Track daily with a Burn-down or Burn-up chart
Use Capacity metrics (total team hours available to meet Sprint objectives)
Use Velocity metrics for Sprint Planning
Do not log defects resolved within the Sprint
Use Jira for Epics, Features, User Stories and Tasks
Participate in Product Backlog refinement sessions
Pairing normally with QAs, BAs or Devs.
Use TDD or ATDD - Test First discipline
Use Automated Continuous Integration (CI)
"Use Automated Testing coverage:
0=none; 1= 5-33%; 2 = 34-66%, 3 = 67-100% "
Track Technical debt and burn it down
Perform Continuous refactoring - "relentlessley"
Train new team members on Agile, Scrum, XP, Jira