49. Agile Scrum in Two Minutes + FREE CHEAT SHEET // Grab your FREE Scrum vs Kanban Cheat Sheet: http://bit.ly/scrum-vs-kanban-cheatsheet
Scrum is perhaps the best-known of the various Agile software development methodologies. In very broad terms, software development is a process where: the Product Owner decides what to build; the Development Team build it; customers use it, experience it, benefit from it in some way.
What makes software development AGILE is that value is delivered to customers in small increments, and feedback from the customer is “fed back” into the process.
The Product Owner takes input from various sources to create a prioritised a list of Features and User Stories: the Product Backlog.
What make Scrum “Scrum” is how things happen between Product Backlog and the Customer:
– Scrum teams work in a series of SPRINTS, most commonly two weeks in length.
– Each Sprint it proceeded by a Sprint Planning Meeting, the outcome of which is a SPRINT BACKLOG.
– Each day during the Sprint there is a Daily Scrum Meeting,
– At the end of the Sprint, the work completed during the Sprint is packaged for release.
– The Sprint ends with two rituals: the SPRINT REVIEW and the SPRINT RETROSPECTIVE.
Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186
Scrum is one of many Agile software development methodologies In very broad terms… The Product Owner decides what to build The Development Team build it Customers use it, experience it, benefit from it in some way That’s software development. What makes it AGILE is that value is delivered to customers in small, regular increments and any feedback from the customer is “fed back” into the process. It’s the Product Owner’s job to take input from customers – and from a range of other sources and use it to create a prioritised a list of features and user stories. The list is known as the Product Backlog As it stands, this picture could apply to a range of different Agile methodologies. What make Scrum “Scrum” is how things work in here. As we’ll see, there are a number of routines and rituals that go along with Scrum, and it’s the job of the SCRUM MASTER to help the Product Owner and Development Team to develop and maintain good habits. Scrum teams work in a series of SPRINTS, most commonly two weeks in length. Each Sprint it proceeded by a “Sprint Planning Meeting.” – attended by the the Development Team meets and Product Owner Together they select HIGH PRIORITY items from the product backlog that the Development Team believe it can commit to delivering in a SINGLE Sprint. The selected items are known as the SPRINT BACKLOG. For the next two weeks, the Development Team focus on working through the items in the Sprint Backlog. Each day during the Sprint there is a Daily Scrum Meeting, where the attendees take turns to say what they did yesterday what they plan to do today and whether they have any blockers At the end of the Sprint, the work completed during the Sprint is packaged for release. The Sprint ends with two rituals: The Sprint Review, which is a demonstration of new functionality to Stakeholders. and the Sprint Retrospective, which is an examination of what went well, what went badly and what could be improved. The aim of the Retrospective is to ensure that the next Sprint is more efficient and effective than the last. And that’s Scrum on two minutes.