The Scrum but Test

Question 1 : Iterations

No iteration
Iteration > 6 weeks
Variable length < 6 weeks
Fixed iteration length 6 weeks
Fixed iteration length 5 weeks
Fixed iteration length 4 weeks or less

Question 2 : Testing

No dedicated testers on team
Unit tested
Feature tested
Feature tested as soon as completed
Software passes acceptance testing
Software is deployed

Question 3 : Agile Specification

No requirements
Big requirements documents
Poor user stories
Good requirements
Good user stories
Just enough, just in time specifications
Good user stories tied to specifications as needed

Question 4 : Product Owner

No Product Owner
Product Owner who doesn't understand Scrum
Product Owner who disrupts team
Product Owner not involved with team
Product Owner with clear product backlog estimated by team before Sprint Planning meeting
Product Owner with release roadmap with dates based on team velocity
Product Owner who motivates team

Question 5 : Product Backlog

No Product Backlog
Multiple Product Backlogs
Single Product Backlog
Product Backlog clearly specified and prioritized by ROI before Sprint Planning meeting
Product Owner has burndown release with release date based on velocity
Product Owner can measure ROI based on real revenue, cost per story point, or other metrics

Question 6 : Estimates

Product Backlog not estimated
Estimates not produced by team
Estimates not produced by planning poker
Estimates produced by planning poker by team
Estimate error < 10%

Question 7 : Sprint Burdown Chart

No Burndown chart
Burndown chart not updated by team
Burndown chart in hours/days not accounting for work in progress (partial tasks burn down)
Burndown chart only burns down when task is done
Burndown chart only burns down when story is done

In addition, Team knows its velocity
In addition, Product Owner Release plan based on known velocity

Question 8 : Team Disruption

Manager or Project Leader disrupts team
Product Owner disrupts team
Manager, Project Leaders or Team Leaders telling people what to do
Have Project Leader and Scrum roles
Noone disrupting team, only Scrum roles

Question 9 : Team

Tasks assigned to individuals during Sprint Planning
Team member o not have any overlap in their area of expertise
No emergent leadership - one or more team members designated as a directive authority
Team does not have the necessary competency
Team commits collectively to sprint goal and backlog
Team members collectively fights impediments during the sprint
Team is in hyperproductive state