Being Agile

Are you happy with your process?

Why me?

Why me?

  • Agile for 6+ years.
  • Initially a skeptic - now i’m a believer
  • I know what works and what doesn't
  • I’m not an agile purist

Why agile?

No process?

  • Not scalable
  • Discipline is important
  • Not everyone is on the same page

Waterfall is not the answer

Waterfall is inefficient

Very long cycles

  • tough to estimate

  • can't adjust requirements

Waterfall

Danger! Technical Debt

  • impact release date

  • long hours

Waterfall

Agile to the Rescue

Adjust to changes quickly

Agile

Plan better

Agile

Constantly evolving process

Agile

Frequent testing

Agile

More attention to detail

Agile

Agile Myths

You must use notecards

Agile myths

Software is bad

Agile myths

You have to do it "my way"

Agile myths

The Spirit of Agile

Sprints

short feature work cycles

Have a goal

Release

MVP

There's always next sprint

Be mindful of technical debt

Sprints

Getting started

before your first sprint...

Map out your project

Getting started

Start storypointing

Getting started

Relentlessly break down stories

Getting started

Storypoint as a group

Getting started

Establish velocity

Getting started

Define "done"

Getting started

Are we done yet?

  • automated tests passing?

  • accepted by stakeholders?

  • demonstrable?

  • ...?

Getting started

A typical sprint

Establish a schedule

Get committed

A typical sprint

Daily standups

A typical sprint

Groom the backlog

A typical sprint

The end: part 1

Demo

A typical sprint

The end: part 2

Retrospective

A typical sprint

Being Agile

By Ray Nicholus

Being Agile

An introduction to developing software with the help of the agile development methodology.

  • 751
Loading comments...

More from Ray Nicholus