Scrum - agilix.nlagilix.nl/resources/Scrum why how what.pdf · Scrum Why and how? Cesario Ramos,...

ScrumWhy and how?

Cesario Ramos, Agile Coach & PST!

Agile Development Consulting Professional software development done right

!


Agenda

• A note on historical challenges.

• A note on root causes.

• A note on how Scrum tackles them?

!


A note on historical challenges

!


Project Success & failure

What percentage of you your projects are successful?

!


Getting better

!


Knowledge upfront?

What percentage of requirements do you know at the beginning of a project?

!


You learn a lot during a project

New or changed35%

Unchanged65%

Requirements

Source: Boehm & Papaccio, Understanding and Controlling software Costs

!


Logic/Design28%

Documentation2%

Human5%

Environment5%

Data6%

Interface6%

Others7%

Requirements Errors41%

Origin of defects

Source: Tom Gilb. 2002

!


Requirements use in systemsAlways used

7%

Often used13%

Sometimes used16%

Seldom used19%

Never used45%

Source: Johnson. 2002

!


What seems to be the problem?

!


What is the difference?

What about the approach?

Production vs development

!


Empirical vs Defined

Empirical•Unpredictable•There is no repeatable relationship between cause & effect•Control by constant measurement, inspection and feedback

Defined•Predictable & repeatable•Use of good or best practice.•Control based on deviations from the standard or plan

!


Empirical

Process Defined Process

Most of development is complex

!


Focus on utilization or flow?

Build the right thing right!Probe for feedback.

!


The waste of Talent & Creativity

•Problem solving conducted only by experts•Improvement ideas that are forced upon different sections of the company rather than invented within them.•Command & Control•Lack of visioning & goal setting

!


1. Develop and use full potential of people intellect and creativity

2. Empirical process control

3. Validate & adapt plans with early and continuous feedback

What do we need?

!


A note on how Scrum tackles this?

!


New New product development game in HBR, 1986.

Characteristics1. Build-in instability2.Self organizing teams3.Multilearning4.Subtle control5.Overlapping development phases6.Organizational transfer of learning

Leadership, Individuals & Teams

!


Scrum flow

$Market feedback

Product Backlog

Detailed

Vague

Sprint Planning

Daily Scrum

Sprint Review Retrospective....

Potentially shippable increment

Adapt actions

Inspection results

!


Scrum building

Scrum

Inspection Transparency Adaptation

Artefacts EventsRoles

!


Opportunity

In Scrum risk is managed in the following ways

• The definition of done ensures that real progress is measured, it is completely transparent what it means to be done and no undone work is left that is unknown.

• Frequent deployment to the UAT environment and frequent feedback mitigates building the wrong thing, finds defects and provides opportunity to fix them as early as possible.

• Short increments give frequent inspection points and opportunities to inspect & adapt based on the latest available information.

• Complete transparency with the sprint burn-downs and work in progress metrics provides accurate and relevant information to act upon daily.

!


What do we use today?

!


Measurement based6%

No methodology27% Waterfall

4%

Iterative19%

Agile44%

Organizations < 1000 people

No methodology15%

Agile22%

Iterative27%

Waterfall12%

Measurement based24%

Organizations >= 1000 people

Methodology Usage in 2010

Source: Forrester Research, 2010

“Select the methodology that most closely reflects the development process you are using.”

In 2001 0-5% used Agile

!


CMMI3%

Scrum12%

Agile Modeling7%

FDD4%RUP

3%XP3%

None34%

TDD4%

Iterative18%

ISO 90003%

Waterfall9%

“Please select the methodology that most closely reflects the development process you are currently using. Choose only one”

Source: Forrester Research, 2010

Process usage in 2010

!


Are you using Scrum?

!


Let’s see1. Is there a recognized Product Owner?2. Is there a product backlog that shows remaining work towards a goal?3. Is there a Development Team with 3 to 9 members?4. Is there a Scrum Master?5. Is there an ordered Product Backlog?6. Is there a Sprint Backlog that shows remaining work in the Sprint?7. Is each Sprint 1 month or less in duration?8. Is a potentially releasable product Increment produced each Sprint?9. Does the Scrum Team create a plan for the Sprint in a Sprint Planning

Meeting?10. Does the Development Team create a plan each day at a Daily Scrum?11. Is the Increment inspected by stakeholders at a Sprint Review?12. Does the Scrum Team conduct a Sprint Retrospective each Sprint?

Source: Ken Schwaber, 2011

Cesario [email protected]

!


Thanks for your attention!

www.agilix.nl

mailto:[email protected]

mailto:[email protected]

http://www.agilix.nl

http://www.agilix.nl

Scrum - agilix.nlagilix.nl/resources/Scrum why how what.pdf · Scrum Why and how? Cesario Ramos,...

Documents

Transcript of Scrum - agilix.nlagilix.nl/resources/Scrum why how what.pdf · Scrum Why and how? Cesario Ramos,...