Scrum Framework. Agile Software Development Process.

1. The SCRUM Framework

17. TEAM Self-Assesment
Area / Question Score Comments
Product Ownership Health
Product Ow ner facilitates user storydevelopment, prioritization and negotiation 3.0
Product Ow ner collaborates proactively with Product Management and other
stakeholders 3.0
User Stories are small, estimated, functionaland vertical 3.0
Product ow ner facilitates development of acceptance criteria which are used in
planning, review and story acceptance 3.0
Teams refine the backlog every sprint 3.0
Total Product Health Score 15.0 60%
PSI/Release Health
Team participates fully in Release Planning and Inspect and Adapt 3.0
Product backlog for the PSI is itemized and prioritized 3.0
Teams proactively interact with other teams on the train as necessary to resolve
impediments 3.0
Team participates in System Demo every tw o weeks, illustrating realprogress towards
objectives 3.0
Team reliably meet 80-100% of non-stretch PSI Objecives 3.0
Total PSI/Release Health Score 15.0 60%
Sprint Health
Team plans the sprint collaboratively, effectively and efficiently 3.0
Team alw ays has clear sprint goals, in support of PSI objectives, and commits to
meeting them 3.0
Teams apply acceptance criteria and Definition of Done to story acceptance 3.0
Team has a predictable, normalized velocity w hichis used for estimating and planning 3.0
Team regularly delivers on their sprint goals 3.0
Total Sprint Health Score 15.0 60%
Team Health
Team members are self-organized, respect each other, help each other complete sprint
goals, manage interdependencies and stay in-sync with each other 3.0
Scrum Master attends Scrum of Scrums and interacts w ith RTE as appropriate 3.0
Stories are iterated through the sprint w ith multiple define-build-test cycles(e.g. the
sprint is not a w aterfalled) 3.0
Team holds collaborative, effective and efficient planning and daily meetings w here all
members participate, status is given clearly, issues are raised, obstacles are removed
and information exchanged 3.0
Team holds a retrospective after each sprint and makes incremental changes to
continually improve its performance 3.0
Total Team Health Score 15.0 60%
Technical Health
Teams actively reduce technicaldebt in each sprint 3.0
Team has clear guidance and understanding of intentional architecture guidance, but is
free and flexible enough to allow emergent design to support optimal implementation 3.0
Automated acceptance tests and unit tests are part of story DoD 3.0
Refactoring is alw ays underway 3.0
CI, build and test automation infrastructure is improving 3.0
Total Technical Health Score 15.0 60%
Total Team Score 75.0 60%
Radar Chart Data
Product Ownership Health 60%
PSI/Release Health 60%
Sprint Health 60%
Team Health 60%
Technical Health 60%