Scrum's Initiate Phase

The Initiate phase consists of following six processes:

  • Create Project Vision In this process, the Project Business Case is reviewed to create a Project Vision Statement that will serve as the inspiration and provide focus for the entire project. The Product Owner is identified in this process;

  • Identify Scrum Master and Stakeholder(s) In this process, the Scrum Master and Stakeholders are identified using specific Selection Criteria;

  • Form Scrum Team In this process, Scrum Team members are identified. Normally the Product Owner has the primary responsibility of selecting team members, but often does so in collaboration with the Scrum Master;

  • Develop Epic(s) In this process, the Project Vision Statement serves as the basis for developing Epics. User Group Meetings may be held to discuss appropriate Epics;

  • Create Prioritized Product Backlog In this process, Epic(s) are refined, elaborated, and then prioritized to create a Prioritized Product Backlog for the project. The Done Criteria is also established at this point; and

  • Conduct Release Planning Conduct Release Planning-In this process, the Scrum Core Team reviews the User Stories in the Prioritized Product Backlog to develop a Release Planning Schedule, which is essentially a phased deployment schedule that can be shared with the project stakeholders. The length of the Sprint is also determined in this process.

Following is the data flow diagram of the Initiate phase, broadly showing how different processes are connected to each other. For more details on different processes, please refer to SBOKā„¢ Guide - get a free copy here


scrum initiate phase 1

Login to post comments