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


Definition of Done[3]

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.


  1. Product Owner - The Product Owner plays a crucial role in the development of a great software product. He or she is responsilble for maintaining the Product Backlog.
  2. Co-preparation - The Product Owner (PO) meets the Team with their technical skills to define the best solution for the business case challenges. Best ideas arise in offsite meeting(s) in a relaxed and inspiring atmosphere. Various techniques are used to explore possibilities and to discover business values and ways to mitigate risks.
  3. Definition of Done - A shared understanding of expectations that the Increment must live up to in order to be releasable into production. Managed by the Development Team.
  4. Retrospective - Sprint ceremony about improving the process