A Scrum project typically involves several phases, and A Guide to the Scrum Body of Knowledge (SBOK?) suggests five phases consisting of nineteen processes. The first phase, known as the Initiate phase, marks the starting point for any Scrum project.
The Initiate phase comprises six processes that encompass the specific activities and flow of a Scrum project. It is important to note that these processes are not necessarily performed in a strict sequential or isolated manner. Depending on the project's unique requirements, some processes may be combined or adjusted accordingly.
- The Project Vision Statement is developed by reviewing the Project Business Case. This statement serves as the project's inspiration and provides a focal point. It is crucial for the vision to address the problem rather than focusing solely on the solution. The Product Owner, representing the Voice of the Customer, is responsible for achieving maximum business value during the Create Project Vision process.
- Identify Scrum Master and Stakeholder(s):
- The Scrum Master and Stakeholders are identified using specific Selection Criteria. The Scrum Master acts as a facilitator and a "servant leader" to ensure an environment conducive to project success. Stakeholders, including customers, users, and sponsors, interact with the Scrum Core Team and influence the project throughout the product development process.
- The Scrum Team members are identified. Typically, the Product Owner holds primary responsibility for selecting team members, often in collaboration with the Scrum Master. The Scrum Team consists of individuals responsible for understanding the business requirements defined by the Product Owner, estimating User Stories, and delivering project outcomes. The team collectively determines the amount of work to commit to in a Sprint and identifies the best approach for completing the work.
- Building upon the Project Vision Statement, Epics are developed. Epics are large, high-level User Stories within the Prioritized Product Backlog. User Group Meetings may be conducted to discuss appropriate Epics. During the initial stages of the project, Epics are created when most User Stories are broadly defined and focused on high-level functionalities and product descriptions. As the project progresses, these Epics are further broken down into smaller, more detailed User Stories that are easier to implement within a Sprint.
- Create Prioritized Product Backlog:
- Epics are refined, elaborated, and prioritized to form the Prioritized Product Backlog for the project. The Product Owner takes the lead in developing the Prioritized Product Backlog, which comprises a prioritized list of business and project requirements in the form of Epics. The prioritization considers factors such as value, risk or uncertainty, and dependencies. In this process, the Done Criteria is established as a set of rules applicable to all User Stories. A clear definition of Done removes ambiguity from requirements and ensures adherence to quality standards. A User Story is considered Done when it is approved by the Product Owner, who evaluates it based on the Done Criteria and individual User Story Acceptance Criteria.
- Conduct Release Planning:
- The Scrum Core Team reviews the User Stories in the Prioritized Product Backlog to develop a Release Planning Schedule, which outlines the phased deployment of the project and can be shared with stakeholders. The Product Owner and Scrum Team determine the Length of Sprint for the project, which typically remains consistent throughout but can be adjusted if necessary or appropriate.
By following these six processes of the Initiate phase, a solid foundation is established for any Scrum project. It's important to remember that these processes can be adapted to suit the specific requirements of each project, and they need not be strictly sequential or separate. Before moving on from the Initiate phase, it is crucial to create a robust project vision and define the various Scrum
