41631 lecture 3 pt3 scrum

SCRUM project managementAn ‘Agile’ MethodologyThomas J. Howardhttps://sites.google.com/site/thomasjameshowardhomepage/[email protected]

Unless otherwise stated, this material is under a Creative Commons 3.0 Attribution–Share-Alike licence and can be freely modified, used and redistributed but only under the same licence and if including the following statement:

“Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark”

https://sites.google.com/site/thomasjameshowardhomepage/

mailto:[email protected]

2013Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark

2

UPDATEEach team has a table at the event to display ideas.

You are not pitching to get funding but to get people interested in your business. Put the word out that you have an exciting technology that has x,y,z benefits and your business which can be suitable to a,b,c market segments. If interested in details, please contact us...

Bring a prototype!Send email to Lisbeth Lassen ASAP: [email protected]

mailto:[email protected]


3

Patent lecture

• Which teams during the lecture applied Verena’s approach to see when their patents are valid and expire?

• Which teams found our in which countries their patents are valid?

• Which teams broke down their claims to understand their IP coverage?

• Who checked whether their brand is trademarked or not?

• Who gave some feedback on the lecture?


4

Cynefin(Welsh word meaning

habit)

Matrix of Chaos and decision making

Build ->

Measure ->

Learn


5

How should we as lecturers assess the

quality of your project management?


6

The Agile Manifesto

Individuals and Interactions

WorkingProduct

Customer Collaboration

Responding toChange

Processes and Tools

Comprehensive Documentation

Contract Negotiation

Following aPlan

Over

Over

Over

Over


7

SCRUM

• Scrum is an ‘Agile’ framework

• Predominantly for software development

• Works well for complex products

• Even more suitable for start-ups/spin-outs


8

The SCRUM process

Stakeholders /Customer

Product Owner

Product Backlog

Requirements

Backlog Creation and Grooming

Development Team

SCRUM Master

Sprint Planning

Sprint Backlog

1-4 week sprint cycle

24 hrs

Daily SCRUM meeting

Sprint Review

Finished Work


9

The Penny Game

Designer

Manufacturer

Assembler

Customer

Company President

Packager

= Manager


10

The Penny Game - Results

20 10 5 1

1

2

3

4

Cust.

Pres.


11

SCRUM team roles

Product Owner

The person responsible for the product and conveying customer requirements.

Also responsible for prioritising design features.

Responsible for satisfying stakeholders and “getting the product out”

Development Team

Turning the requirements into product related outputs.

Responsible for agreeing workload in sprint cycle and then executing it!

Working with the development teams to achieve sprint agreements and goals.

SCRUM Master

The ‘servant leader’ who removes obstacles of the development team.

Fosters training an self-organising teams. Makes sure sprint reviews and daily reviews stay on schedule


12

Product Owner

The person responsible for the product and conveying customer requirements.

Also responsible for prioritising design features.

Responsible for satisfying stakeholders and “getting the product out”

Development Team

Turning the requirements into product related outputs.

Responsible for agreeing workload in sprint cycle and then executing it!

Working with the development teams to achieve sprint agreements and goals.

SCRUM Master

The ‘servant leader’ who removes obstacles of the development team.

Fosters training an self-organising teams. Makes sure sprint reviews and daily reviews stay on schedule

Who’s who in your project?


13

The Product Backlog

1

2

3

Common practice:

• Post-its on a canvas

• Design features

• Modular

For Sprint Release

Pre Sprint Release

Incr

ease

in P

rior

ity &

Dec

reas

e in

Gra

nula

rity

Product Owner’s

Baby


14

Where is your product/business backlog?


15

Product BacklogGrooming

1

2

3

STEP 1:

Add Items


16


1

2

3

STEP 2:

Prioritise

Move higher priority items towards release line


17


1

2

3

STEP 3:

Item breakdown

Each item should represent a business unit of value and be achievable in 1 sprint cycle


18

Sprint Planning

• Product owner confirms to development team what each released backlog item means and what is required to complete it to match the definition of ‘done’.

• Product owner communication priorities and dependences

• Development team agree with Product Owner which items will be completed during the next sprint cycle.

• Development team then discusses how the tasks will be separated and worked on.

1


19

Where can this be indicated in the development log?


20

Daily SCRUMS

• 15 minutes total

• Every day at same time

• Don’t be late and be prepared

• In turn state 3 things:

• What you did yesterday

• What you will do today

• What’s in your way

• Everyone stands up

(Even if via video link)

http://askthecmmiappraiser.blogspot.dk

https://www.youtube.com/watch?feature=player_detailpage&v=YBKuYzqvZmI


21

Managing a sprint backlog

Product Backlog Item

(PBI)To Do In Progress Done


22

Product Burndown

– Used to monitor and respond to project Progress

– Four types:• Backlog items (Stories) • Backlog points (Story Board points)• Backlog items (Stories) to MVP• Backlog points (Story Board points) to

MVP

MVP: Minimum Viable Product


23

Product Burndown1. Backlog Items

1

2

3

Total number of Backlog Items = 21


24

Product Burndown2. Backlog Points

1

2

35 4

2

2

7

2

54

53

43

42

1

22

22

21

Total number of Backlog Points = 64


25

Product Burndown3. Backlog Items to MVP

1

2

3

MVP Items

Bonus Items

Total number of Backlog Items to MVP = 37


26

Product Burndown4. Backlog Points to MVÅP

1

2

3

4

53

43

42

1

22

22

21

MVP Items

Bonus Items

Total number of Backlog Points to MVP = 37


27

Product Burndown


28

Burndown Exercise


29

Sprint burndown

? ?


30

Exercise

With your levels of experience it takes 1 day to design, make and assemble (position) one piece.

http://www.toyshopuk.co.uk/lego-minotaurus/


31

Exercise Description• Get into teams of 4 or 5• Select a Product OwnerThe rest will be the Development Team• Tom will act as the customer• No SCRUM Master• Product Owner to ask customer for requirements• Product owner to Create backlog with inputs from Team• Create sprint cycles and begin to get to work (draw up the

elements of the design on scraps or onto the plan)• Show customer the work done and listen to changing

requirements• Continue until work is done


32

Where would SCRUM be useful for you to apply?


33

Exercises

1. Create a Product Backlog for your projects.

2. Plan how to organise your project using SCRUM.


34

Questions

?

41631 lecture 3 pt3 scrum

Documents

Transcript of 41631 lecture 3 pt3 scrum