5-7 minutes<\/p>\n
Scrum has short fixed schedule of release cycles with adjustable scope known as sprints to address rapidly changing development needs. A Scrum process is distinguished from other agile processes by specific concepts and practices, divided into the three categories of Roles , Ceremonies (also Events or meetings) and Artifacts as shown in the Figure below:<\/p>\n
Scrum \u2013 Roles, artifacts, ceremonies<\/p>\n
Each Scrum Project could have multiple Release Cycles and each release could have multiple sprints. There are a number of repeating sequence of meetings , to be held before, within and after the sprint cycle.<\/p>\n
Scrum suggests three roles: the team, Scrum Master , and product owner ; four ceremonies: the sprint planning meeting , Daily Scrum , sprint review meeting , and sprint retrospective meeting ; and three artifacts: the product increment, product backlog , and sprint backlog as shown in the Figure:<\/p>\n
The Agile Scrum Framework<\/p>\n
Meetings or \u201cceremonies\u201d are an important part of agile development. They help to disseminate timely information, bring common goal and vision, and share team progress to all team members. The complete Scrum team attends all the ceremonies except there trospective, which the product owner may or may not attend. Scrum calls for ceremonies mentioned above that forms structure to each sprint:<\/p>\n
Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised.<\/p>\n
As mentioned above, Product Backlog refinement is an ongoing activity, and unless it is being conducted at scale it does not restricted to be a time-boxed event (or meeting) . However, there is nothing to stop teams from time-boxing each refinement session anyway. In general it is good practice to use time-boxing.<\/p>\n
The goal of Sprint Planning is to answer the questions \u201cWhat are we going to work on, and how are we going to do it?\u201d It\u2019s also important for the team to have a shared goal and a shared commitment to this goal before beginning their Sprint \u2013 the list of items the team plans to work on during that specific Sprint. The team then breaks down these items into tasks, typically no bigger than a 2 days\u2019 worth of work.<\/p>\n
Once we begin a Sprint, we have what we call a Daily Scrum every day. Organized by the Scrum Master, Daily Scrum is typically a 15-minute stand-up meeting to synchronize the work of team members, i.e. what\u2019s done on the prior day, what needs to be done today, identify any impediments, and creates visibility around the work that everyone is doing in the Sprint.<\/p>\n
At the end of the Sprint, the goal is to have a Potentially Shippable Product Increment(PSPI). We\u2019re trying to get something of incremental value done every Sprint.<\/p>\n
Held at the end of each sprint to demonstrate the added functionality. The goal is to get feedback from the product owner and other stakeholders to ensure that the delivered increment met the business need and to revise the Product Backlog based on the feedback. This feedback will then become items that will be looped back into the Product Backlog, where it can be ordered and pulled in by the team in a future Sprint.<\/p>\n","protected":false},"excerpt":{"rendered":"