We take initiative and ask for forgiveness instead of permission.
Sprint
Why
At Kabisa we work in sprints with a fixed length of two weeks, in order to:
- Be able to focus on the most valuable user stories & bugfixes
- Deliver a working product at least every two weeks
- Get into a good rhythm of working together
- To get early feedback from the Product Owner, users and other stakeholders
- To be able to retrospect the team and progress
- Be able to plan realistically, and do forecasts
Prepare for success
- Take time for a proper project kick-off and good co-preparation.
- As soon as the start date of the first sprint is known, invite all team members for all Backlog Refinement meetings, Sprint Planning meetings, Sprint Reviews and Retrospectives.
- Confer with the Product Owner[1] to invite the key stakeholders to all Sprint Reviews.
How
- Start every sprint with a Sprint Planning.
- Build awesome software!
- End every sprint with a Sprint Review and a Retrospective.
- Take time for proper Backlog Refinement, and when needed plan additional co-preparation[2].
Definition of Done[3]
- Sprint Review and the Retrospective[4] are done.
- Project Status Report has been delivered.
Real Life Example
For a semi-public organisation in the energy sector, a Kabisa team took over and improved the development of their web application in three sprints at the end of 2016. The customer quickly became confident that Kabisa was the right choice, and chose for 14 consecutive sprints in 2017. Once the start of the first sprint of those 14 sprints was set, the Scrum Master and Product Owner immediately planned all Daily Standups, Sprint Planning meetings, Sprint Reviews, Retrospectives and Backlog Refinements for all 14 sprints. Meeting rooms were booked and team and stakeholders were invited.
