Testing in Scrum

Practices
Planning Poker:
– Estimation in Story Points (SP), minimum of 1, maximum of 13 SPs per task
– Break complex tasks down into smaller units
– Acceptance criteria are to be agreed on and recorded in writing

eHome Controller project Team Charter
Team Charter
– How we will implement Scrum in the eHome Controller project –
Sprint
Duration: 4 weeks
Each Sprint is preceded by a Sprint Planning phase and ends with a review
Meetings
Daily Scrum: At 11am, maximum duration 15 minutes, Product Owner takes part
Sprint Planning: Wednesday at 9am (at the start of the Sprint), maximum duration 1 day
Review: Tuesday at 11am (at the end of the Sprint)

A successful Sprint delivers a potentially shippable product. Early Sprints should deliver at least a prototype to show the customer, while later Sprints should generate constantly improving releases that can be used in a productive environment

Testers help draft approval criteria
In order to draft the right approval criteria, the team’s testers need to be involved in the process. This also makes it easier for the testers to design appropriate acceptance tests later on

The project is given the go-ahead for a 12 month period and the marketing team has requested that the trial period includes four product releases. In other words, the first release has to be ready in three months!