scrum - agile methodology

70
NIEL DECKX Freelance iOS Developer Certified ScrumMaster Certified Product Owner www.nieldeckx.be

Upload: niel-deckx

Post on 15-Jul-2015

2.894 views

Category:

Leadership & Management


0 download

TRANSCRIPT

Page 1: Scrum - Agile Methodology

NIEL DECKX

Freelance iOS Developer

Certified ScrumMasterCertified Product Owner

www.nieldeckx.be

Page 2: Scrum - Agile Methodology

HAVE A DECENT PROCESS WHEN CREATING A PRODUCT

What’s the main goal?

Page 3: Scrum - Agile Methodology

HAVE A DECENT PROCESS WHEN CREATING A PRODUCT

What’s the main goal?

Why?

CREATE THE BEST PRODUCT

Page 4: Scrum - Agile Methodology

SUMMARY

- Waterfall- The Agile Manifesto- SCRUM Principles - SCRUM Framework - Roles & Team - Artefacts - Activities

Page 5: Scrum - Agile Methodology

WATERFALL

Page 6: Scrum - Agile Methodology

OVERVIEW

IdeaAnalysis

Design

Development

Testing

FinalProduct

Page 7: Scrum - Agile Methodology

OVERVIEWDesign

…Testing

FinalProduct

FeedbackCollaboration

Business Value

Page 8: Scrum - Agile Methodology

PUSH SYSTEM

Input Capacity Delivery

overwhelm capacitycreating waste and delay

Page 9: Scrum - Agile Methodology

QUALITY

Scope

BudgetTime

Quality

If budget, time and scope are fixed,quality will vary.

Page 10: Scrum - Agile Methodology

THE AGILE MANIFESTO

Page 11: Scrum - Agile Methodology

Individuals and Interactions

over processes and tools

Working software

over comprehensive documentation

Customer collaboration

over contract negotiation

Responding to change

over following a plan

Page 12: Scrum - Agile Methodology

BE AGILE- Team and collaboration- Incremental - Iterative- Value driven - Frequent delivery - Product quality- Inspect and adapt- Self-organisation

Page 13: Scrum - Agile Methodology

SCRUM PRINCIPLES

Page 14: Scrum - Agile Methodology

BE ADAPTIVEDesign, Testing, Development

ProductIncrementBusiness Value

FinalProduct

Repeat!Feedback,Collaboration Repeat!

Page 15: Scrum - Agile Methodology

PDCA

ProductIncrement

Plan Do Check Act

Page 16: Scrum - Agile Methodology

VALUE DRIVEN

CONSTRAINTS:

ESTIMATES: Scope

Time Budget

Quality

Page 17: Scrum - Agile Methodology

PRIORITIZATION

MoSCoW

Must HaveShould HaveCould HaveWon’t Have Out of scope

Buffer

In scope

Page 18: Scrum - Agile Methodology

BENEFITSfor business

- Quicker ROI - Lower Total Cost- Respond to Change- Reduce Risk- Faster Time to Market- Stakeholder Relations

Page 19: Scrum - Agile Methodology

BENEFITSfor development

- Teaming- A Sense of Done - Quality Work- Rhythm - Visible Progress- Feedback and Iteration

Page 20: Scrum - Agile Methodology

SCRUM FRAMEWORK

Roles, Artefacts and Activities

Page 21: Scrum - Agile Methodology

ROLES & TEAM

- Product Owner - Scrum Master - Development Team

Page 22: Scrum - Agile Methodology

SCRUMTEAM

MEMBER

a good is focussedhas respect for others has courageis committedis open

Page 23: Scrum - Agile Methodology

5 - 9 members

TEAM

Self-organising

Cross functional

SCRUM TEAM

Page 24: Scrum - Agile Methodology

- Represents customers and stakeholders - Maximise product value- Track time and budget- Manage product backlog

PRODUCT OWNER

Page 25: Scrum - Agile Methodology

- Bring up impediments- Resolve impediments - Support the Scrum team in implementing Scrum

SCRUM MASTER

Page 26: Scrum - Agile Methodology

- Cross functional - Accomplishing the Sprint goal- Delivers a product increment

DEVELOPMENT TEAM

Page 27: Scrum - Agile Methodology

Scrum MasterProduct Owner

Development Team

SelectFeatures

ProductIncrement

Discuss

Work onFeatures

SupportsScrum Team

Page 28: Scrum - Agile Methodology

ARTIFACTS

- Product Backlog- Sprint Backlog- Product Increment- Definition of Done - Progress Monitors

Page 29: Scrum - Agile Methodology

PRODUCT BACKLOG

User Story

User Story

User Story

Epic Story

Epic Story

Page 30: Scrum - Agile Methodology

STORY FORMAT

AS A …

I WANT TO …

SO THAT …

Who?

What?

Why?

User role

Action

Business goal

Page 31: Scrum - Agile Methodology

STORY

Acts as- Requirement- Planning item- Reminder - Conversation trigger- Shared understanding

Page 32: Scrum - Agile Methodology

EPIC STORY

- Must be split in user stories

- Stories which do not satisfy INVEST criteria

Page 33: Scrum - Agile Methodology

INVEST CRITERIA

IndependentNegotiableValuableEstimableSmallTestable

Can deliver value by itself Details can be worked out by conversation Value to the user is clear Team understands it well to estimateFits in a sprintClear test criteria

Page 34: Scrum - Agile Methodology

PRODUCT BACKLOGBug

User Story

User Story

Epic Story

Epic Story

Refactoring

Page 35: Scrum - Agile Methodology

- Prioritised set of estimated items- Constantly in change as the situation changes- Contains stories, bugs, refactorings, …- Detailed appropriately - Source of work for the Development team

PRODUCT BACKLOG

Page 36: Scrum - Agile Methodology

SPRINT BACKLOG

User Story

User Story

User Story

Epic Story

Epic Story

User Story

User Story

PRODUCT BACKLOG

Page 37: Scrum - Agile Methodology

TASKEach user story can be separated into (technical) tasks.

As a plan to accomplish the work.

AS A …

I WANT TO …

SO THAT …

Set up the database

Create API call

Page 38: Scrum - Agile Methodology

User Story

User Story

Task

Task

Task

Task

Task

INITIALSPRINT BACKLOG

Page 39: Scrum - Agile Methodology

TO DO

User Story

User Story

Task

TaskTask

DOING BLOCKED DONE

SPRINT BACKLOG

Task Task

Dynamic representation of the work during a sprint.

Page 40: Scrum - Agile Methodology

DEFINITION OF READY

Sprint

Minimise Waste

When is a product backlog item sprintable?

Page 41: Scrum - Agile Methodology

DEFINITION OF DONE

Sprint ProductIncrement

Minimize Risk

When is a task really done?

Page 42: Scrum - Agile Methodology

PRODUCT INCREMENT

= Potentially shippable increment of the product.

It meets the Definition of Done!

Page 43: Scrum - Agile Methodology

PROGRESS MONITORS

First we have to understand what

a sprint and a sprint planning is.

Page 44: Scrum - Agile Methodology

PRODUCT BACKLOG

SPRINT BACKLOG

SPRINT PLANNING

DAILY SCRUM

SPRINT

PRODUCT INCREMENT

DEFINITION OF DONE

SPRINT REVIEW

SPRINT RETROSPECTIVE

PROGRESS MONITORS

Page 45: Scrum - Agile Methodology

ACTIVITIES

- Sprint- Sprint planning- Daily scrum - Sprint review - Sprint retrospective- Product backlog refinement

Page 46: Scrum - Agile Methodology

Be adaptive! Iterate!

Sprint

Fixed timebox in which the Scrum team delivers a product increment

according to the Definition of Done.

between 1 and 4 weeks

Page 47: Scrum - Agile Methodology

SPRINT

Project progresses in sprints

Sprint commitment by Development team

No new requirements during the spint

Scrum team delivers a product increment

Page 48: Scrum - Agile Methodology

How do we plan?

Sprint Planning

Timeboxed meeting for the Scrum Team,to pull work into the Sprint Backlog

max 2 hours per week of sprint

Page 49: Scrum - Agile Methodology

SPRINT PLANNING

SPRINT BACKLOG

PRODUCT BACKLOG

Which items can the team commit to?What is the sprint goal?

Which tasks can we identify for each story?

Page 50: Scrum - Agile Methodology

ITEM ESTIMATES

The development team plays planning poker

Page 51: Scrum - Agile Methodology

RELATIVE ESTIMATES

- Story points are more then just time - Compare to reference item- Faster, more accurate planning- Independent of developer skills

Fibonacci: 1 2 3 5 8 13 ..

Page 52: Scrum - Agile Methodology

PLANNING POKER

1 - Product Owner explains item2 - Developer compares with a reference item 3 - All cards are shown together 4 - Highest and lowest explained5 - Team gets to a consensus, possible other round

Page 53: Scrum - Agile Methodology

Track progress during the sprint?

Daily Scrum

Timeboxed meeting for the Development team to make sure the sprint goal is reached.

max 15 minutes

Page 54: Scrum - Agile Methodology

What did you do yesterday? What will you be doing today? Are there any blocking issues?

Everyone. Short. Turn by turn.

And take necessary steps after the Daily Scrum

Page 55: Scrum - Agile Methodology

Sprint improvements?

Sprint Retrospective

Timeboxed meeting for the Scrum team to discuss the sprint and improve further.

max 1 hour per week of sprint

Page 56: Scrum - Agile Methodology

What did we do good in last sprint? What did we do less in the last sprint?

Are there any questions or uncertainties? Are there any open items from last retrospective?

Everyone. Write down.

Group the items and discuss. Plan and take action.

Page 57: Scrum - Agile Methodology

Delivered product?

Sprint Review

Timeboxed meeting for the Scrum team and stakeholders to review the product increment

max 1 hour per week of sprint

Page 58: Scrum - Agile Methodology

Updated backlog!

Product Backlog Refinement

Scrum team keeps the product backlog up to date,to have a shared understanding of what needs to be done

ongoing activity

Page 59: Scrum - Agile Methodology

Add stories.

Remove stories.

Split stories.

Add detail to stories.

Prioritise stories.

Estimate stories.

Product Backlog Refinement

Page 60: Scrum - Agile Methodology

PRODUCT BACKLOG

SPRINT BACKLOG

SPRINT PLANNING

DAILY SCRUM

SPRINT

PRODUCT INCREMENT

DEFINITION OF DONE

SPRINT REVIEW

SPRINT RETROSPECTIVE

PROGRESS MONITORS

Page 61: Scrum - Agile Methodology

PROGRESS MONITORS

Now we understand what

a sprint and a sprint planning is.

Page 62: Scrum - Agile Methodology

A story point is more then just time.

How do we know how many story points we can handle as a development team?

MEASURE!

Page 63: Scrum - Agile Methodology

STORY POINTS DONE

SPRINTVELOCITY =

Page 64: Scrum - Agile Methodology

VELOCITY

used by developers for better sprint estimations and to stabilise progress

Page 65: Scrum - Agile Methodology

VELOCITY

used by the product owner to make forecasts that help

to prioritise items

Page 66: Scrum - Agile Methodology

VELOCITY GRAPH

| | | | | | | |

Long Term ?

Remainingstory points

Sprints | | | | | | | |

Stability ?

Predictability ?

Page 67: Scrum - Agile Methodology

VELOCITY GRAPH

| | | | | | | |

Remainingstory points

Sprints | | | | | | | |

Deadline

Page 68: Scrum - Agile Methodology

VELOCITY GRAPH

| | | | | | | |

Remainingstory points

Sprints | | | | | | | |

Deadline

Will deliverMight deliver

Not delivered

Page 69: Scrum - Agile Methodology

PRODUCT BACKLOG

SPRINT BACKLOG

SPRINT PLANNING

DAILY SCRUM

SPRINT

PRODUCT INCREMENT

DEFINITION OF DONE

SPRINT REVIEW

SPRINT RETROSPECTIVE

PROGRESS MONITORS

Page 70: Scrum - Agile Methodology

THANK YOU

www.nieldeckx.be