"In the first week of each Sprint, we testers don't have much to do. Then we are going crazy the last few days."

"The developers don't have much to do in the last few days of each Sprint, so they are usually getting started on the next Sprint."

"It's not unusual for the team to have nothing that is deliverable at the end of the Sprint. Everything's been coded, but the testing isn't done."

Scrum sprints can be tricky. Agile teams often fall into the trap of turning their Scrum sprint into a mini-waterfall. They take on work and save testing until the end of a Sprint, which tends to create more carryover than truly done work. This session focuses on how to combat the mini-waterfall pitfall and save your Scrum sprint by swarming as a team, breaking work down, and tasking effectively.


Outline/Structure of the Talk

  1. Mini Waterfall Model – the symptoms
  2. Strategies to avoid waterfall in sprint
  3. Key Principles
  4. The Anti Patterns
  5. The Benefits of Avoiding Mini-Waterfalls
  6. Q&A

Learning Outcome

The session would help to avoid mini waterfall trap

It would help to build D-D-T, D-D-T, D-D-T... model in sprint than D-D-T model

Target Audience

Agile Practitioners, Product Owners, Team members, Scrum Masters, ScrumTeam, Change Agents

Prerequisites for Attendees

Basic knowledge of agile framework

schedule Submitted 3 years ago

Public Feedback