4. Scrum PDF

Preview

Summary

4. Scrum...

Description

Agile Software Development TU Munich, 7-22 December 2020

Torgeir Dingsøyr

Scrum

IKT

Source: www.scrum.org

The Elements of Scrum

Roles

Processes

Artefacts

Product Owner Scrum Master Scrum Team (Stakeholders)

Sprint Sprint Planning Meeting Daily Scrum Meeting Sprint Review Meeting Sprint Retrospective Meeting

Product Backlog Sprint Backlog Burndown Chart

12

Scrum

IKT

Source: www.scrum.org

Product backlog Backlog item

Estimate

Allow a guest to make a reservation

3

As a guest, I want to cancel a reservation.

5

As a guest, I want to change the dates of a reservation.

3

As a hotel employee, I can run RevPAR reports (revenue-per-available-room)

8

Improve exception handling

8

...

30

...

50

Source: Mountain Goat Software

IKT

Product backlog

Source: Philippe Kruchten / Eltjo R. Poort, ““Agilizing” the Architecture department”

Scrum

IKT

Source: www.scrum.org

Team capacity

Sprint planning meeting

Product backlog Business conditions

Sprint prioritization

Sprint goal

• Analyze and evaluate product •

backlog Select sprint goal

Sprint planning

• Decide how to achieve sprint goal Current product

• •

(design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog in hours

Sprint backlog

Technology

Source: Mountain Goat Software

IKT

Sprint planning ! Team selects items from the product backlog they can commit to completing ! Sprint backlog is created ! Tasks are identified and each is estimated (1-16 hours) ! Collaboratively, not done alone by the ScrumMaster ! High-level design is considered

As a vacation planner, I want to see photos of the hotels. Source: Mountain Goat Software

Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4)

Estimation; Planning poker

Henrik Kniberg: Scrum and XP from the Trenches, 2007.

IKT

Exercise

! How long does it take to make “Pasta Carbonara”? ! Make an individual estimate in minutes

Exercise Download a planning poker app such as ScrumeTime or use hands. In breakout groups, try estimating the following dishes using planning poker: ! Pizza ! Spaghetti Bolognese ! Fish soup

Scrum

IKT

Source: www.scrum.org

Sprint backlog

Henrik Kniberg: Scrum and XP from the Trenches, 2007.

Physical artefacts ! Increases awareness within the team, and also for people outside of the team ! Physical artefacts represent tokens of responsibility ! Physically moving artefacts have been found to give more reflection than electronic manipulation ! Physical artefacts are easy to consult ! Physical artefacts are hard to ignore

Source: Sharp, H. and Robinson, H., Collaboration and co-ordination in mature eXtreme programming teams, International Journal of Human-Computer Studies 66 (2007) 506-518.

Sprint backlog Tasks Code the user interface Code the middle tier Test the middle tier Write online help Write the foo class Add error logging

Source: Mountain Goat Software

Mon Tues Wed Thur Fri 8

4

8

16

12

10

4

8

16

16

11

8

8

8

8

8

8

4

12 8

IKT

Sprint “burndown chart” 1!000

Hours

800 600 400 200 0 Source: Mountain Goat Software

IKT

Scrum

IKT

Source: www.scrum.org

Daily meetings

1 What did you do yesterday?

2 What will you do today?

3 Is anything in your way? ! These are not status for the ScrumMaster ! They are commitments in front of peers Source: Mountain Goat Software

Many use daily meetings

Rodriguez, P., Markkula, J., Oivo, M., and Turula, K., "Survey on agile and lean usage in finnish software industry," presented at the Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement, Lund, Sweden, 2012.

Daily meetings “…improve communications, eliminate other meetings, identify and remove impediments to development, highlight and promote quick decision-making, and improve everyone´s level of project knowledge …from just 15 minutes a day” page 40, Schwaber, K. and Beedle, M., Agile Software Development with Scrum. Upper Saddle River: Prentice Hall, 2001

Time distribution; Daily meetings

Source: Viktoria Stray, University of Oslo

Scrum

IKT

Source: www.scrum.org

Sprint review

Moe, N. B., Dingsøyr, T., and Dybå, T., "A teamwork model for understanding an agile team: A case study of a Scrum project," Information and Software Technology, vol. 52, pp. 480–491, 2010.

Sprint review ! Team presents what it accomplished during the sprint ! Typically takes the form of a demo of new features or underlying architecture ! Informal ! 2-hour prep time rule ! No slides ! Whole team participates ! Invite the world

Source: Mountain Goat Software

Retrospectives “the single most important practice in agile development” Agile practice guide

“number-one-most-important thing in Scrum” Henrik Kniberg IKT

Project Management Institute and Agile Alliance”, Agile Practice Guide: Project Management Institute, 2017. Kniberg, H., Scrum and XP from the Trenches, 2nd edition ed.: InfoQ, 2015.

Postmortem reviews / Retrospectives ! ! ! ! ! ! !

Performed after a project or a project milestone Sums up the good and bad experiences A group process lasting approximately half a day As many people as possible are gathered Everyone get to say their opinion Everything is exposed and discussed in the group The experiences is documented for later use (externalisation)

Telecom and Informatics

27

Timeline

Moe, N. B., Dingsøyr, T., and Dybå, T., "A teamwork model for understanding an agile team: A case study of a Scrum project," Information and Software Technology, vol. 52, pp. 480–491, 2010.

IKT

Wrap-up ! Read before lecture tomorrow: ! Dingsøyr, T.; Falessi, D.; Power, K. (2019): Agile Development at Scale: The Next

Frontier. IEEE Software 36(2): 30-38 (Article 2).

IKT...