Meeting Structure
Duration development sprint cycle: 2 weeks
Deliverables – CIN
- Implemented, tested and documented user stories
- Show & Tell session after each sprint
- Described manual test cases per user story
- Automated test cases for delivered user stories to ensure the quality of future delivery
- Regression defect free consolidation environment
To dos – Customer
- User Acceptance Test after each sprint
- Provide final Acceptance Criteria for each User Story two weeks before Sprint Start at the latest
- Inform CIN about Scope changes two weeks before beginning of sprint
Show & Tell Sessions
When:
Wednesdays after each sprint (dry run with the development team on Tuesday in the Consolidation system)
How:
The Product Owner presents the results and the delivered User Stories from that previous sprint to the customer
(IT & Business)
User Acceptance Test (UAT):
After the S&T we hand over those User Stories that are ready for UAT to the customer. Should the customer not test the user stories within 10 days, it is assumed that the respective User Stories are accepted, and their status will be set to closed (i.e. accepted by user).
Product Backlog to Sprint Backlog
Teams select the stories that they want to work on from the Product Backlog and move these stories to the Sprint Backlog
Each story is assigned to a Team of Ten in the Sprint Backlog
Workflow Status
The progress of the project is fully transparent to the customer at all times.
