AGILE METHODOLOGY AND SCRUM - University of Toronto

18
AGILE METHODOLOGY AND SCRUM 17 / 18 1 / 18

Transcript of AGILE METHODOLOGY AND SCRUM - University of Toronto

Page 1: AGILE METHODOLOGY AND SCRUM - University of Toronto

AGILE METHODOLOGY AND SCRUM

17 / 181 / 18

Page 2: AGILE METHODOLOGY AND SCRUM - University of Toronto

SOFTWARE ENGINEERINGHistorically, software used to often be written by a single developerAs software grew more complex, teams of people started working on singleprojectsIncreased budgets and risk caused companies to start �nding ways to tryand minimize potential pitfalls

17 / 182 / 18

Page 3: AGILE METHODOLOGY AND SCRUM - University of Toronto

DEVELOPMENT METHODOLOGIESTwo major kinds of development methodologies are Waterfall and Agile

Waterfall:Rigid, linear approachAll requirements set before design, frozen before developmentGo through each phase one at a timeHostile to changeNo back-tracking

Agile:Iterative approachA little bit of work done on each phase everydayFunctional product (deliverables) ready after every incrementEmbracing changeContinuous revisions; frequent feedback

1 / 183 / 18

Page 4: AGILE METHODOLOGY AND SCRUM - University of Toronto

WHAT DOES THAT LOOK LIKE?

2 / 184 / 18

Page 5: AGILE METHODOLOGY AND SCRUM - University of Toronto

WHAT DOES THAT LOOK LIKE?

3 / 185 / 18

Page 6: AGILE METHODOLOGY AND SCRUM - University of Toronto

SOME VIDEOS ON WATERFALL VS AGILEhttps://www.youtube.com/watch?v=swWmVdaMloIhttps://www.youtube.com/watch?v=PHS-ycbRwqI

4 / 186 / 18

Page 7: AGILE METHODOLOGY AND SCRUM - University of Toronto

SCRUMAn agile methodologyWork is done in short (2-4 week) iterations called "sprints"Should have a visible, functional product at end of each sprint

5 / 187 / 18

Page 8: AGILE METHODOLOGY AND SCRUM - University of Toronto

SCRUM PROCESS

6 / 188 / 18

Page 9: AGILE METHODOLOGY AND SCRUM - University of Toronto

SCRUM PROCESS

7 / 189 / 18

Page 10: AGILE METHODOLOGY AND SCRUM - University of Toronto

CORE IDEA FOR SCRUM

8 / 1810 / 18

Page 11: AGILE METHODOLOGY AND SCRUM - University of Toronto

STEPS TO SOFTWARE DESIGNRequirements, design, construction, testing"Rather than doing all of one thing at a time, Scrum teams do a little ofeverything all the time"

Source: The New New Product Development Game by Takeuchi and Nonaka. Harvard Business Review,January 1986.

9 / 1811 / 18

Page 12: AGILE METHODOLOGY AND SCRUM - University of Toronto

ROLES IN SCRUMProduct Owner (PO)

Knows what the product is supposed to do.Maintains a Product Backlog (prioritized list of user stories, i.e., features) and communicates with theteam about vision.

Scrum MasterResponsible for the scrum processFacilitates scrum eventsServices both the Product Owner and the Team

TeamDesigns and builds what the Product Owner wantsAnalysts, Designers, Developers, Testers, …

10 / 1812 / 18

Page 13: AGILE METHODOLOGY AND SCRUM - University of Toronto

SCRUM PROCESS SUMMARYSprint planning meeting

A meeting with PO, SM and Team. Take highest priority user stories and create the Sprint Backlog (thefeature list for the current sprint).

Sprint (1 to 3 weeks)Team works on delivering the Sprint Backlog. They architect, code, test, document etc.Daily Scrum meeting -- A meeting with SM and Team. 15 Minute standup meeting, each team membersays: What I did yesterday, What I am doing today, Obstacles I face.

Sprint Review:A meeting with PO, SM and Team. Show off product to PO. Acceptance test as well as discussion ofScrum Process improvement.

Sprint RetrospectiveDiscuss how to improve the Scrum process

11 / 1813 / 18

Page 14: AGILE METHODOLOGY AND SCRUM - University of Toronto

SPRINT PLANNING MEETINGDe�nes what will be delivered in the incrementTeam selects items from the product backlog and de�nes a sprint goalDe�nes how the increment will be achievedItems are converted into tasks and estimated

12 / 1814 / 18

Page 15: AGILE METHODOLOGY AND SCRUM - University of Toronto

SPRINT PLANNING MEETING EXAMPLE

13 / 1815 / 18

Page 16: AGILE METHODOLOGY AND SCRUM - University of Toronto

SPRINT REVIEWProduct owner identi�es what has been doneTeam discusses what went well, what problems it ran into and those thatwere solvedTeam demonstrates what it has done in a demoProduct owner discusses the backlog as it standsEntire group collaborates on what to do next

14 / 1816 / 18

Page 17: AGILE METHODOLOGY AND SCRUM - University of Toronto

SPRINT RETROSPECTIVEInspect how the last Sprint wentIdentify and order the major items that went well and potentialimprovements; and,Create a plan for implementing improvements

15 / 1817 / 18

Page 18: AGILE METHODOLOGY AND SCRUM - University of Toronto

SOME VIDEOS ABOUT SCRUMhttps://www.youtube.com/watch?v=2Vt7Ik8Ublwhttps://www.youtube.com/watch?v=9TycLR0TqFA

16 / 1818 / 18