Agile in a nutshell

Agile in a Nutshell Steven “Doc” List

What’s coming?Seven sections, Pecha Kucha / Ignite style 20 slides, 15 seconds each = 5:00 7 * 5:00 (300) = 2100 seconds = 35:00 Plus short breaks (I’ve GOT to breathe!) Q&A (or get a break)

The Seven Sections

The Seven Sections Memorize this because there WILL be a test!1.History 5.Roles & People2.Principles 6.Practices3.Players 7.User Stories and more4.Lifecycle

Fasten your seatbelts!

1. History

1: ll? fa er What is atw

w at What is er fa l? l Dr. Winston Royce, 19701:

Project Plans 1:

BDUFBig Design Up Front 1:

Silos 1:

Isolation 1:

ReRe ac vo ti lu on tio , n 1:

Lightweight 1:

Collab oration 1:

Transparency 1:

Time toValue 1:

Schools of Thought 1:

Scrum 1:

ExtremeProgramming (XP) 1:

Snowbird Feb 2001 1:

Is this enough? 1:

Breathe! Take a drink of water.

2. Principles

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2:

Welcome changingrequirements, even late in development. Agileprocesses harness change for the customers competitive advantage. 2:

Responding to Change over Following a PlanWelcome changing requirements, even late in development. Agileprocesses harness change for thecustomers competitive advantage. 2:

Deliver working softwarefrequently, from a couple of weeks to a couple ofmonths, with a preferenceto the shorter timescale. 2:

Working Software overComprehensive DocumentationDeliver working software frequently, from a couple ofweeks to a couple of months, with a preference to the shorter timescale. 2:

Iterative DevelopmentDeliver working software frequently, from a couple ofweeks to a couple of months, with a preference to the shorter timescale. 2:

Business people and developers must worktogether daily throughout the project. 2:

Build projects aroundmotivated individuals. Givethem the environment and support they need, and trust them to get the job done. 2:

Individuals and Interactions over Processes and ToolsBuild projects around motivated individuals. Give themthe environment and support they need, and trust them to get the job done. 2:

The most efﬁcient and effective method ofconveying information toand within a development team is face-to-face conversation. 2:

Co-location Daily Stand-Up Retrospectives The most efﬁcient and effective method of conveyinginformation to and within a development team is face-to- face conversation. 2:

Working software primaryWorking software is theis theprimary measure of progress. measure of progress. 2:

Working software is theprimary measure of progress. 2:

Agile processes promotesustainable development. The sponsors, developers, and users should be able tomaintain a constant pace indeﬁnitely. 2:

Agile processes promotesustainable development. The sponsors, developers, and users ab le in ta e should be able to Sus ac Pmaintain a constant pace indeﬁnitely. 2:

Simple DesignContinuous attention totechnical excellence andgood design enhances agility. 2:

Simplicity--the art of maximizing the amount ofwork not done--is essential. Simple Design 2:

The best architectures,requirements, and designsemerge from self-organizing teams. 2:

Emergent Design,Evolutionary Architecture The best architectures,requirements, and designsemerge from self-organizing teams. 2:

At regular intervals, the teamreﬂects on how to become moreeffective, then tunes and adjusts its behavior accordingly. 2:

At regular intervals, the teamreﬂects on how to become moreeffective, then tunes and adjusts its behavior accordingly. Retrospectives 2:

Breathe! Take a drink of water.

3. Players

Ken Schwaber Scrum 3: Players

Ken Schwaber Scrum Jeff Sutherland 3: Players

Kent Beck ExtremeProgramming 3: Players

Kent Beck ExtremeProgramming Ron Jeffries 3: Players

Kent Beck Ron Jeffries ExtremeProgramming Ward Cunningham 3: Players

Kent Beck Ron Jeffries Extreme Programming Martin FowlerWard Cunningham 3: Players

Agile Alliance “AgileRetrospectives” Diana Larsen 3: Players

Agile Alliance “AgileRetrospectives” Esther Derby Diana Larsen 3: Players

Alistair Cockburn Crystal Methodology“Agile Software Development” 3: Players

Robert C. “Uncle Bob” Martin Software Craftsmanship “Clean Code” 3: Players

James Grenning Planning Poker 3: Players

Elisabeth Hendrickson Test Obsessed 3: Players

Adaptive Leadership “Agile Project Management” Jim Highsmith 3: Players

Lisa Crispin Agile Testing “Agile Testing” 3: Players

Mary PoppendieckLean Software Development“Lean Software Development” 3: Players

Take a breath.

4. Lifecycle Design & Operations /Inception Iteration 0 Build BAU

Let’s talk about the iterative model 4:

Let’s talk about the iterative model Lather, Rinse, Repeat 4:

Design & OperationsInception Iteration 0 Build / BAU 4:

Inceptio Design & Operation Iteration 0 n Build s / BAU Begin at the beginning 4:

Inceptio Design & Operation Iteration 0 n Build s / BAU Who What Why Value 4:

Inceptio Design & Operation Iteration 0 n Build s / BAU Workshops User Story (Epic) Writing Team Norms Plan Release 1 Plan Iteration 1 4:

Iteration Design & OperationInception 0 Build s / BAU Laying the foundation 4:

Iteration Design & OperationInception 0 Build s / BAU Software Hardware Furniture Network Infrastructure 4:

Design & OperationInception Iteration 0 Build s / BAU Iterate...ate...ate 4:

Design & OperationInception Iteration 0 Build s / BAU P r o j e c t 4:

Design & OperationInception Iteration 0 Build s / BAU P r o j e c tRelease Release Release 4:

Design & OperationInception Iteration 0 Build s / BAU P r o j e c tRelease Release Release Features Features Features MVPs MVPs MVPs Other Other Other 4:

Design & OperationInception Iteration 0 Build s / BAU Release 4:

Design & Operation Inception Iteration 0 Build s / BAU Release RetrospectivePlan Iterations 4:

Design & Operation Inception Iteration 0 Build s / BAU IterationPlan 4:

Design & Operation Inception Iteration 0 Build s / BAU Iteration Analyze Retrospective Showcase DesignPlan Code Test Deploy 4:

Design & Operation Inception Iteration 0 Build s / BAU PlanningRelative 4:

Design & Operation Inception Iteration 0 Build s / BAU PlanningRelative Collaborative 4:

Design & Operation Inception Iteration 0 Build s / BAU PlanningRelative Collaborative Iterative 4:

Design & Operation Inception Iteration 0 Build s / BAU PlanningInnovation Games Planning Poker Vertical Slice Story Mapping 4:

Design & Operation Inception Iteration 0 Build s / BAU PlanningInnovation Games Luke Hohmann 4:

Design & Operation Inception Iteration 0 Build s / BAU PlanningInnovation Games Planning Poker James Grenning 4:

Design & Operation Inception Iteration 0 Build s / BAU PlanningInnovation Games Planning Poker Story Mapping Jeff Patton 4:

Take a sip of water.

5. Roles & People

Product Owner /Product Manager 5: Roles &

Project Manager 5: Roles &

Iteration Manager / ScrumMaster 5: Roles &

Business Analyst 5: Roles &

User Experience Analyst / Designer 5: Roles &

Developer 5: Roles &

Architect / Technical Lead 5: Roles &

Tester / Quality Analyst 5: Roles &

QA / Test Lead 5: Roles &

BA Lead 5: Roles &

Scaling Projects 5: Roles &

Scrum of Scrums 5: Roles &

Huddles 5: Roles &

Inclusivity 5: Roles &

Shared... Responsibility,Accountability, Success 5: Roles &

Trust 5: Roles &

Courage 5: Roles &

Drink, Breathe, Pause

6. Practices

Co-location 6: Practices

Pairing 6: Practices

Showcase / Demo 6: Practices

Refactoring 6: Practices

Card Wall 6: Practices

Ready In Test Done Card Wall 6: Practices

Daily Stand-Up 6: Practices

Retrospective 6: Practices

Big Visible Charts 6: Practices

As a... I need... So that...User Story 6: Practices

I will know this is complete when...Acceptance Criteria Given... When... Then... 6: Practices

Test-First 6: Practices

TDD 6: Practices

BDD 6: Practices

FDD 6: Practices

DDD Eva ns E ric 6: Practices

DDDD 6: Practices

ATDD 6: Practices

Collaborative Estimation 6: Practices

Collaborative Planning 6: Practices

Iterations / Flow 6: Practices

Drink, Breathe, Pause

7: User Stories

Co-location 7: User Stories

The User Story Template Role: As a... Goal: I want/need... Value: So that... 7: User Stories

Role: As a... 7: User Stories

Goal: I want/need... 7: User Stories

Value: So that... 7: User Stories

Acceptance CriteriaHigh Level: I will know this is complete when...Detailed... 7: User Stories

Given...When...Then... Given: The context and setup 7: User Stories

Given...When...Then... When: The action 7: User Stories

Given...When...Then... Then: Expected results 7: User Stories

Hierarchy of DetailThemes: Planning 7: User Stories

Hierarchy of DetailEpics: BIG Stories 7: User Stories

Hierarchy of DetailStories: INVEST and the Three C’s 7: User Stories

INVESTI: Independent 7: User Stories

INVESTN: Negotiable 7: User Stories

INVESTV: Valuable 7: User Stories

INVESTE: Estimable 7: User Stories

INVESTS: Small 7: User Stories

INVESTT: Testable 7: User Stories

The Three C’s CardConversationConﬁrmation 7: User Stories

So much more! Planning Releases & Iterations Big Visible ChartsInformation Radiators ... 7: User Stories

I’m done!

Steven “Doc” List Agile CoachDoc@AnotherThought.com www.StevenList.com

http://localhost	176
http://a0.twimg.com	9
http://us-w1.rockmelt.com	7
http://juha7one.wikispaces.com	6
http://manage.rethinktraining.com	3
http://webdatapower.com	3
http://deschleib.tumblr.com	2
http://ribenmgx.jurentuangou.com	1
http://paper.li	1
http://www.linkedin.com	1

Agile in a nutshell

by Doc List

Accessibility

Categories

Upload Details

Usage Rights

10 Embeds 209

Statistics