This will only take you several minutes to complete Team Self-Assessment survey. It helps our relentless improvement.
Which APT are you in? If you are working across two APTs, please do twice with different APT.If you are not in specfic APT, like BO/CPO/RTE, please select one APT each time you would like to survey.
Development APT
Solution Eng. APT
Deployment APT
Product Ownership HealthScoring: 0 - Never, 1 - Rarely 2 - Occasionally, 3 - Often, 4 - Very Often, 5 - Always
Product Owner facilitates user story development, prioritization and negotiation ★ ★ ★ ★ ★
Product Owner collaborates proactively with Chief Product Owner and other stakeholders ★ ★ ★ ★ ★
User Stories are small, estimated, functional, vertical, and fit in an iteration ★ ★ ★ ★ ★
Product Owner facilitates development of acceptance criteria which are used in planning, review and story acceptance ★ ★ ★ ★ ★
Team refines the Team Backlog every Iteration ★ ★ ★ ★ ★
PI HealthScoring: 0 - Never, 1 - Rarely 2 - Occasionally, 3 - Often, 4 - Very Often, 5 - Always
Team participates fully in PI Planning and Inspect and Adapt ★ ★ ★ ★ ★
Team proactively interacts with other teams on the ART as necessary to resolve impediments ★ ★ ★ ★ ★
Team participates in System Demo (iteration review) every two weeks, illustrating real progress towards objectives ★ ★ ★ ★ ★
Team reliably meets 80-100% of committed PI Objectives business value ★ ★ ★ ★ ★
Iteration HealthScoring: 0 - Never, 1 - Rarely 2 - Occasionally, 3 - Often, 4 - Very Often, 5 - Always
Team plans the Iteration collaboratively, effectively and efficiently ★ ★ ★ ★ ★
Team always has clear Iteration Goals, in support of PI objectives, and commits to meeting them ★ ★ ★ ★ ★
Team applies acceptance criteria and Definition of Done to story acceptance ★ ★ ★ ★ ★
Team has a predictable, normalized velocity which is used for estimating and planning ★ ★ ★ ★ ★
Team regularly delivers on their Iteration goals ★ ★ ★ ★ ★
Team HealthScoring: 0 - Never, 1 - Rarely 2 - Occasionally, 3 - Often, 4 - Very Often, 5 - Always
Team members are self-organized, respect each other, help each other complete Iteration Goals, manage interdependencies and stay in-sync with each other ★ ★ ★ ★ ★
Scrum Master attends Scrum of Scrums and interacts with RTE as appropriate ★ ★ ★ ★ ★
Stories are completed throughout the Iteration with multiple define-build-test cycles (i.e., the Iteration is not waterfalled) ★ ★ ★ ★ ★
Team meets each day at the same time and place for the Daily Stand-up to coordinate their work and resolve impediments ★ ★ ★ ★ ★
Team holds a retrospective after each Iteration and makes incremental changes to continuously improve its performance ★ ★ ★ ★ ★
Technical HealthScoring: 0 - Never, 1 - Rarely 2 - Occasionally, 3 - Often, 4 - Very Often, 5 - Always
Team actively reduces technical debt in each Iteration ★ ★ ★ ★ ★
Team has clear guidance and understanding of intentional architecture guidance, but is free and flexible enough to allow emergent design to support optimal implementation ★ ★ ★ ★ ★
Automated acceptance tests and unit tests are part of story DoD ★ ★ ★ ★ ★
Refactoring is always underway ★ ★ ★ ★ ★
CI, build and test automation infrastructure is improving ★ ★ ★ ★ ★
Team is coming up with new hypotheses and testing them continuously ★ ★ ★ ★ ★
Team is continuously deploying to production ★ ★ ★ ★ ★
Team architects their work to allow for continuous deployment, release on demand and recovery ★ ★ ★ ★ ★
