A process for product development

bor!sgloger Scrum FlowScrum defines the frame in which all activities of product development take place. The product development process is divided into clearly defined intervals called sprints, which last between two and four weeks. At the end of each sprint, the product team has to deliver potentially releasable software, which would even work if the rest of the production would be cancelled. The course of a sprint, its roles, meetings and artefacts is what we call the Scrum Flow. The main idea behind the sequence of the meetings is continuous improvement. 

Click: Boris Gloger explains the Scrum Flow in this video.

 The Scrum Flow is made up of the following elements:

  • Roles
    • ScrumMaster
    • Product Owner
    • (Development-) Team
    • Manager
    • Customer
    • (End) User
  • Meetings
    • Sprint Planning Meeting 1
    • Sprint Planning Meeting 2
    • Daily Scrum
    • Estimation Meeting
    • Sprint Review
    • Sprint Retrospective
  • Artefacts
    • Vision
    • Product Backlog Item
    • Product Backlog
    • Sprint Goal
    • Selected Product Backlog
    • Tasks
    • Sprint Backlog
    • Release Plan
    • Impediment Backlog
    • Product increment – usable software

Each sprint is made up of a strategic planning process. The Product Owner continuously works on his product vision, updates and re-prioritizes his Product Backlog (the list of functionalities that have to be developed) and establishes an overall Release Plan together with the Development Team. Impediments that may occur while developing the functionalities are immediately gotten rid of by the ScrumMaster.

Level of Done

The crucial principle behind Scrum is that at the end of each sprint, the Development Team delivers potentially usable functionality. However, the extent of this principle has to be adjusted to the development conditions of each organisation. For this reason, the Product Owner and the Development Team define a shared Level of Done. The ScrumMaster then works together with the Development Team to steadily increase this Level of Done, so that ideally the product increment can be delivered to the End User at the end of each sprint.