You keep using the word agileI DO NOT THINK IT MEANS WHAT YOU THINK IT MEANS

@NathanGloyn

Quick poll

Who’s “doing” agile?

silhouettes human group by Gerd Altmann used under CC 0

What most people think is agile Work in 2 week iterations User Stories Story points/Planning Poker Backlog of items Meetings Board with post it notes or Jira

You’re telling me this isn’t agile?

If You're Not Confused by Brian Talbot used under CC BY

Why isn’t this agile?

Cargo Cult

Why isn’t this agile? Focus on completing the tasks/stories Software is not deployable KPI’s based on tasks/stories Team not self organising Meetings do not add value

How did we get here?

1995 - 2000

2001 - 2008

2008 - 2012 2012 - today

How did we get here? The problem delivering a product is the development process

How did we get here? It will be cheaper

How did we get here? Software will be “delivered” more frequently

How did we get here? Able to change requirements right up to the last minute with no problems

How did we get here? Want a “named” method with process & practices

How did we get here? Certification implies knowledge

Stand back….

I’m certified! Derivative of Superhero Rob by Rob Cottingham used under CC BY

Where it goes wrong Mistaking practice for result Just renaming existing processes/roles Misunderstood/missed the point behind of a practice Not interested in agile outside of the development process Agile isn’t the right process

The result

an unwitting victim...bwahahhahahaa by Bark used under CC BYSelf Portrait As A Stressed-Out Bride To Be by Brittney Bush Bollay used under CC BY

What have I done!? by Miguel Angel used under CC BY

So what is agile?

Self-Portrait E by Steve Snodgrass used under CC BY

Agile ManifestoIndividuals and interactions over processes and tools

Working software over comprehensive documentation Customer collaboration over contract negotiation

Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Principles behind agile manifesto Highest priority is customer satisfaction through early and continuous delivery of valuable software Welcome changing requirements, even late in development, to harness change for customers competitive advantage Deliver working software frequently with a preference to the shorter timescale Business people & developers to work together daily

Principles behind agile manifesto Build projects around motivated individuals, giving them environment & support they need, and trust them to get the job done Most efficient way of conveying information is face-to-face conversation Working software is the primary measure of progress Promote sustainable development. Sponsors, developers & users should be able to maintain constant pace indefinitely

Principles behind agile manifesto Continuous attention to technical excellence & good design Simplicity – art of maximising work not done – is essential Best architectures, requirements & designs emerge from self-organising teams Team should meet at regular intervals to reflect on how to improve

Why would you want to use agile? Communication Transparency Trust Collaboration Delivering value to the business

What is value?

Today I bring value to the world by Kimberly King used under CC BY

What is “value”? Value likely to be specific to your team/business/organisation Determine what your value (or values) Work out how to measure it Use your “value” to help with decision making around work to be done

Agile isn’t… Completing tasks User stories, Story points & planning poker Meetings Working through Product Owner “to-do” list Following an Agile methodology

Agile is… Working software Focused on vision & goals Feedback loops Delivering value People from across the business/organisation all work together

Its not a set of rules

"Rules and Regulations...Threshing Committee of the U.S. Food Administration for Knox Co." by Unknown or not provided used under CC BY

Technical practices

Unit testingRefactoring

YAGNIPair Programming

Continuous IntegrationVersion control

ATDD

BDD

TDD

Refactoring

Collective ownershipContinuous Deployment

Iterative development

Mob programming

Product practices

User Stories

Product backlog

Product canvas

Value stream mappingCustomer on site

PersonasVision & Goals

MVPProduct Roadmap

MoSCoW

Project practicesStory Points

flow

Story mapping

No Estimates

Definition of done

Impact Mapping

options

Visual work trackingRestrict WIP

Classes of work

KaizenRetrospectives

Eliminate waste

Pull basedRisk Storming

Release Train

cynefin

The difference Working software is the priority Focused on goals for the project/product Looking to add value Everyone involved collaborates around the work

How to “reclaim” agile? Nothing wrong with starting with a methodology You do not have to “follow the rules” The wider business becoming involved Become involved with the wider business Evolve

What does evolution look like? Variety of practices from methodologies Pick the practices that work Focus on vision/goal for project Keep delivering working software Keep collaborating

What to take away Always focus on delivering working software Make whatever process you have transparent Communication & Collaboration is key Don’t be bound by “the rules” Evolve to help you deliver value

Questions?@NathanGloyn

www.designcoderelease.blogspot.com