2015-09-21 - where do you want to get to · 'would you tell me, please, which way i ought to...

Jim YorkMelissa Yorkwww.FoxHedgeLtd.com

John Tenniel / Wikimedia Commons / Public Domain

Where do you want to get to?

A goal-based approach to adopting Scrum

1Wednesday, November 11, 15

Content © 2015 FoxHedge Ltd

Who We Are

Melissa YorkPrincipal

[email protected]

Jim YorkPrincipalCoach

[email protected]

FoxHedge Ltdwww.FoxHedgeLtd.com




Where do youwant to get to?



Alice’s Dilemma'Would you tell me, please, which way I ought to go from here?'

'That depends a good deal on where you want to get to,' said the Cat.

'I don't much care where—' said Alice.

'Then it doesn't matter which way you go,' said the Cat.

'—so long as I get SOMEWHERE,' Alice added as an explanation.

'Oh, you're sure to do that,' said the Cat, 'if you only walk long enough.'

Alice’s Adventures in Wonderland, Lewis Carroll





A better world

Begin with the end in mind

Connect practice to strategy

Imagine your better world


Be choosyJoin a team

Identify practices

Share




A better world






Identify practices

Share



A better world —the promise of Agile


Content © FoxHedge Ltd




A better world






Identify practices

Share



Why is this important?



70% of change initiatives fail!

“over 70 percent of the situations where substantial changes were clearly needed, either they were not fully launched, or the change efforts failed, or changes were achieved but over budget, late, and with great frustration”

— John P. Kotter



Satir Change Model



Begin with the End in Mind

‘“Begin with the end in mind’ is based on the principle that all things are created twice. There is a mental or first creation, and a physical or second creation to all things.

— Stephen Covey




A better world






Identify practices

Share



Scrum15Wednesday, November 11, 15


“Scrum was designed to achieve a hyperproductive state where productivity increases by an order of magnitude over industry averages.”

— Jeff Sutherland



Scrum Delivery Cycle



Scrum Delivery Cycle with Practices

Modeling

User Stories

Standup

Review

Retrospectives

Points

Small team

Sit Together

Customer in the Room

DoD

Pair Programming

TDD

Frequent Integration

Automated Testing

1-click Build & Deploy

PrioritizationEmpowered

Team

Adaptive Planning

Release PlanningSustainable Pace

YAGNI

Information Radiator



• acceptance tests• adaptive planning• Agile Champion• automated build

and deploy• automated

testing• backlog• Boot Camp• Boundaries• Build Quality In• Burn Chart• Business Value

Analysis•Center of

Excellence•Co-location•Coach• coding standards•Collective Code

Ownership•Conditions of

Satisfaction•Constraints•Containers•Continuous

Integration•Core Team

•Cross-functional team

•Customer Acceptance TDD

• customer feedback

• customer-in-the-room

•Cycle time• daily meeting• dedicated team• definition of done• eliminate waste• Empowered Team• Enterprise

Transition Team• Evolutionary

Architecture• Evolutionary

Design• Fast Delivery• Feedback• Flow• frequent

feedback loops• frequent

integration•Goal

• Impediment List• incremental

development• Information

Radiator• Innovation

Games• Iteration Planning

Meeting• Iterations• just enough, just-

in-time requirements

• Kaizen• Kanban•Management

Tests•Minimum

Meaningful Feature Set

•Muda•One Team•Open Workspace• pair programming• Pareto (80/20)• Pay as you go• Personas

• Pigs and Chickens

• Pilots Projects• Planning Poker• prioritized

backlog• Product Lifecycle• Product Owner•Quality Criteria• Reduce Waste• refactoring• regression testing• Regular Cadence• Relative

Estimation• Release Often• retrospectives• Review• Scrum

Development Team

• Scrum of Scrums• Scrum Roles• ScrumMaster• Self-Organizing

Team• shared goal• Shared Vision

• Simple Design• single business

decision maker• Sit Together• small releases• Spikes• Sprint Backlog• Sprint Review• Stakeholder

Analysis• Story Points• Success Criteria• sustainable pace• Swarming• Test First

Development• Theory of

Constraints• timeboxes• Tune Up• unit-level TDD• user stories• Velocity• visual recording•Whole team•Working Software• YAGNI

~101 Practices




A better world






Identify practices

Share



Strategy Dimension Outcome Measure

Teamwork Team Focus Team Satisfaction

Quality Skills Craftmanship Production Defects

Focus on Customer

Customer Effectiveness Customer Satisfaction

Time to Market

Flow Fast Delivery Cycle Time

Alignment to Strategy

© 2013 Jim York



Sample PracticesStrategy: TeamworkMantra: ”We’re a team!”

Core Supplemental

• small, dedicated team• shared goal• co-location• daily meeting• shared environments• customer-in-the-room• coach• team estimation• definition of “done”• retrospectives

• team room• timeboxes (iterations)• incremental delivery• paired programming• Customer Acceptance TDD• story cards• empowered team

© 2013 Jim York



Sample PracticesStrategy: QualityMantra: ”We do good work!”

Core Supplemental

• coding standards• unit-level TDD• pair programming• refactoring• frequent integration• acceptance tests• regression testing• retrospectives

• shared goal• timeboxes (iterations)• incremental development• customer feedback• automated testing• automated build and deploy• definition of done• Customer Acceptance TDD

© 2013 Jim York



Sample PracticesStrategy: Focus on CustomerMantra: ”We build the right stuff!”

Core Supplemental

• customer-in-the-room• single business decision

maker• user stories• prioritized backlog• Customer Acceptance TDD• frequent feedback loops• adaptive planning

• timeboxes• incremental development• retrospectives• just enough, just-in-time

requirements

© 2013 Jim York



Sample PracticesStrategy: Time to MarketMantra: ”We deliver fast!”

Core Supplimental

• just enough, just-in-time requirements

• timeboxes• incremental development• small releases• dedicated team• frequent feedback loops• adaptive planning

• sustainable pace• daily meeting• YAGNI• eliminate waste• retrospectives

© 2013 Jim York


2015-09-21 - where do you want to get to · 'would you tell me, please, which way i ought to...

Documents