Mastering scrum

Post on 12-May-2015

2.416 views 0 download

Tags:

Transcript of Mastering scrum

Mastering AgileGEERT.THEYS@ALTAGE-CONSULT.COM

VERSION Beta

http://www.flickr.com/photos/fengschwing/3278956517/

Thursday 16 December 2010

Agenda

Thursday 16 December 2010

Agenda

The ancient ways

Different Agile Styles

Scrum Style

Results

How to test your Scrum

Thursday 16 December 2010

To improve our kungfu we need to know what went wrong.

Po: I know you're trying to be all mystical and Kung Fu-ey, but could you tell me where we're going?

Thursday 16 December 2010

Traditional Software Development

Thursday 16 December 2010

Traditional Software Development

Plan everythingStick to the PlanFollow the process

Thursday 16 December 2010

Building the wrong thing

We assume:

The customer knows what he wantsThe Developers know how to build itNothing will change during execution

Thursday 16 December 2010

Most IT projects fail

What is definition of Succes?

Standish Group used :

on-time, on-budget and with most of the expected features

This is not succes but a failure in estimation.

Project success is more about whether the software delivers value that's greater than the cost of the resources put into it - but that's very tricky to measure. (Martin Fowler)

23%

49%

28%

Succes Challengedfail

Thursday 16 December 2010

What are the different Agile styles?

Thursday 16 December 2010

ScrumDaily Scrum

Sprint Backlog

BurndownChart

SprintPlanningMeeting

SprintDemo

Scrum Master

Product Owner

Product Backlog

Team

XPCollectiveOwnership

Whole team Coding Standard

CustomerTests

PairProgramming Refactoring Planning

Game

ContinousIntegration Simple

Design

SustainablePace

Metaphor Small Releases

Scrum & XP

http://blog.crisp.se/henrikkniberg/

Thursday 16 December 2010

Agile Assumes

http://www.flickr.com/photos/b2tse/3960471608/sizes/o/

We assume:

The customer discovers what he wantsThe developers discovers how to build itThings change on the way

Thursday 16 December 2010

Let’s focus on SCRUM

Thursday 16 December 2010

Agile Mind

Tries to be predictable

Fixes Time, Price and scope on projects

Values Methodology and its processes more than the people

Measures succes of project by their conformance to plan

Resist Change in software requirements and development process

Sees the system specification as the generated documentation

Accepts that predicatbility in business software is impossible

Time and price are fixed but not the scope

Values people more than the process, hence it accepts a process instead

Success of the project is measured by the value it gives to the customer

Welcomes Change in software requirements and development process

Sees the system specification as the development code

Thursday 16 December 2010

TransparancyInspectionAdaption

Three Legs

http://www.flickr.com/photos/chrisafer/2427399932/sizes/l/

Thursday 16 December 2010

Scrum Roles

http://www.flickr.com/photos/clintjcl/305229885/

Thursday 16 December 2010

Product Owner

Thursday 16 December 2010

Product Owner

Must have authority to manage the product log

The product owner is not a comittee

Thursday 16 December 2010

The Team

Thursday 16 December 2010

The Team

Self Organised - Cross functional - max 9 membersThursday 16 December 2010

Scrum Master

Thursday 16 December 2010

Scrum Master

Teaches Scrum by coaching an leading it

Removes all impediments

Thursday 16 December 2010

Chicken and Pig

Thursday 16 December 2010

Chicken and PigProduct owner Scrum MasterThe Team

UsersManagersOthers

Thursday 16 December 2010

Scrum Process

Thursday 16 December 2010

Product BacklogFirst person

Shooter

MultiplayerSinge Player

TutorialMissions

Storyline

OnlineCooperative

GameplayPlayer

Control

AI Death Match

Split Screen

Thursday 16 December 2010

Product Backlog

Thursday 16 December 2010

Product Backlog

Owned by the product ownerNever completeBest-understood requirementsEvolvesSorted in order of priority

Thursday 16 December 2010

Sprints

Thursday 16 December 2010

Sprint Planning

Defining the sprint length and goalWhat are we going to buildHow are we going to build itWhen will it be “done”

Thursday 16 December 2010

Sprint Backlog

Owned by the teamTeam allocates tasksNo additions from outside the team

Thursday 16 December 2010

Taskboard

Thursday 16 December 2010

Sprint Burndown

Thursday 16 December 2010

Daily Standup

http://www.flickr.com/photos/jonnimont/3763340830/

Thursday 16 December 2010

Daily Standup

Answer: What did I do and what am I going to do?Comitment to the team not the Scrum MasterTake responsibility on your own work!MAX : 15 and don’t sit down!

http://www.flickr.com/photos/jonnimont/3763340830/

Thursday 16 December 2010

Sprint Review

Everybody is welcome

No mockups - Show working code

Get feedback on your product

Accept or Reject features

Thursday 16 December 2010

Done?

Avoid 90% problem

General concensus needed what is done...

Done should be clear to everyone!

Thursday 16 December 2010

Sprint Retrospective

Thursday 16 December 2010

Sprint Retrospective

GoodBadDo more Do Less

Evolution

Thursday 16 December 2010

Results

Thursday 16 December 2010

Incremental Change

Deliver feature by feature - Highest value first

Quick Results - Quick Fail

Shorter time to market

Thursday 16 December 2010

Flexibility

Respond easily to change

No danger of missing a deadline

Thursday 16 December 2010

Higher Quality

Continous testing

Continous integration

Inspect - Adapt

Thursday 16 December 2010

http://www.flickr.com/photos/mcanevet/289262598/

More fun - happy teams

http://www.flickr.com/photos/32034590@N04/4657598751/

Thursday 16 December 2010

Grading your mastery

http://www.flickr.com/photos/mcanevet/289262598/

Thursday 16 December 2010

Shu-Ha-Ri stages of learning

Shu = Follow the rules

Ha = Change the rules

Ri = Never mind the rules

Thursday 16 December 2010

Scrum.org

Thursday 16 December 2010

ScrumAlliance

Graduate Proffesional Guide

Certified Product Owner

Certified Scrum Master

Certified Scrum Developer

Certified Scrum Proffesional Certified Scrum Trainer

Certified Scrum Coach

Thursday 16 December 2010

Questions?

Thursday 16 December 2010

slideshare.net/geerttheys

twitter/toadi

be.linkedin.com/in/gtheys

geert.theys@altage-consult.com

geerttheys

geerttheys.com

Thursday 16 December 2010

This presentation was inspired by the works of many people, and I cannot possibly list them all. Though I did my very best to attribute all authors of texts and images, and to recognize any copyrights, if you think that anything in this prevention should be changed added or removed, please contact me at geert.theys@altage-consult.com

http://creativecommons.org/licenses/by-nd/3.0/

Thursday 16 December 2010