I don't

care

about

your

agile

process

Preface

Don't be mad Im just a developer.

Trigger
Warning

- Oppinions ahead!

- Everything is on a gradient (even if I might hint otherwise)

- There are no universal truths, context matters!

- I welcome any different oppinions to my points ❤

Patrick

- 10+ years experience in prof. software development

- 3 years as Lead Dev

- 85% of projects used variation of Scrum or Kanban

- 0% of projects done agile

If you wanna talk, rant, discuss agile, reach out to me :)

Why should we listen to

Go to

www.menti.com

Code: 8975 1037

Agile is simple

Allen Hollup (probably)

Starting doing the most important thing

When finished, immediately give it to people who use it

Get feedback from customer and adapt if needed

This also applies to the process itself!

Main Concepts:

Customer

VALUE

PRIORITY

Iteration

Neil on Software

Customer

Tech people MUST directly talk to the customer.

What is a customer?

Somebody that pays or consumes your product (I guess).

Means we are not doing it for ourself.

Everybody MUST understand the business model.

Go to

www.menti.com

Code: 8975 1037

More on Customer

Personas: Focus on a single customer

What is a customer? Somebody who pays for or consumes the product.

Your Product Owner, Product Manager, Project Manager is not the customer.

Yes, developer CAN talk to customer if they can talk to a human beeing.

VALUE

But what is VALUE?

Something that makes the business money?

Something that solves a problem?

Something that the customer wants?

If the customer DOESNT want to pay for it, can it EVER have VALUE?

Value needs to be measured by data

The cost of NOT delivering something.

Jez Humble, Lean Enterprise

Other Methods

  • A/B Testing
  • Business Metrics
  • Experimental: Hypothesis, Test, Measure

Estimates

Estimations

Jez Humble, Lean Enterprise

are mostly USELESS

Dev Cost does not have big impact on ROI or lifecycle profit.

Douglas Hubbard

1.

2.

Estimation for duration is notoriously inaccurate. Best time to ship is right now.

A/B Testing

Business Metrics

Hypothesis->Test->Result

PO or Product Managers are always wrong what value is

PRIORTY

Pick the thing with the highest VALUE and do that first!

Focus on delivering VALUE not work items, stories, etc. (Output vs Outcome)

Iteration

Talk to the customer about their problems.

Find the first scope the customer would pay money for.

That's your first ITERATION.

The "Iced Tea" Iteration

Sprints are stupid

Sprints

Just doing the iteration

Release Blue
Release
Green
Release Blue
Release
Green

Takeaway

Following specific processes does not make you agile!

Shu Ha Ri: but its fine to start with a known process

What's not Agile?

(Certified) Process Frameworks

Agile Industrial Complex

Scaling Agile

Sprints

Estimates

Fixed Deadlines

Not doing the thing with highest value first

Not adapting your process all the time

Predictability over Outcome

Having fixed roadmaps months ahead

"We only deploy every X weeks"

Always using Agile

"We do it like this because all the other teams do it like that"

Calling everything squads, tribes, chapters

Never bending or breaking the rules

Middle Management

Not talking directly to customer

Martin Fowler, State of Agile 2018

Questions?

Sources