Introduction to Scrum - A Real World Example (Case Study) Before Starting The First Sprint Alex works as the Scrum Product Owner of a new software development project. One of his first tasks is to assess and find out requirements to deliver business value his client is looking for.
During those sessions, Anna, the Scrum Master, ensures that everyone speaks the same language. So, the Scrum Product Owner, the Scrum Team Members, and their stakeholders are aligned with the anticipated goals. So they have an adequate understanding of potentially new concepts for them, such as Use Case, Backlog, Sprint, and so on. And most importantly, the Scrum software development and delivery process is correctly applied in the store.
He needs to make sure that his client will get the correct software to achieve tangible business results. He writes down the essential use cases and discusses them with the architects, client representatives, and other stakeholders from IT and business units.
Now Alex, the Scrum Product Owner, begins to break down the high-level requirements into the first draft of smaller-grained user stories. With this list, he then calls for the first Sprint Planning Meeting.
After assembling the high-level use-cases and requirements, he writes them into the Scrum Product Backlog and initiates an estimation and prioritization session with the Scrum Team. As a result of this session, all items in the Scrum Product Backlog get an initial rough estimate and priority.
Sprint 1 - Day 0 During the Sprint Planning Meeting, Alex presents the Scrum Product Backlog items from the highest priority to the lowest. The Scrum Team asks and clarifies open questions. For each item, the team discusses if they have enough
25
