31
AGILE 101 by Pradeep Nayar

Agile 101

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Agile 101

AGILE 101by

Pradeep Nayar

Page 2: Agile 101

We’re talkingSDLC

SOFTWAREDEVELOPMENTLIFECYCLE...........................................zzzzZZZZ (Snore!)

Page 3: Agile 101

THE WATERFALL

Page 4: Agile 101

THE CHALLENGES

Took too long to build

Was over budget

Original estimates were wrong

Uncertain requirements

Is it truly what they needed?

Discovery

Design

Development

Deployment

Maintenance

4

Page 5: Agile 101

THE PERFECT EXAMPLEThe Death Star

Page 6: Agile 101

AGILE WAS BORN

Page 7: Agile 101

THE REBELLION

KENT BECK MIKE BEEDLE ARIE VAN BENNE ALISTAIR COCKBURN WARD CUNNINGHAM MARTIN FOWLER JAMES GRENNING JIM HIGHSMITHANDREW HUNT RON JEFFRIES JON KERN BRIAN MARICK ROBERT C. MARTIN STEVE MELLOR KEN SCHWABER JEFF SUTHERLAND DAVE THOMAS

Page 8: Agile 101

FEBRUARY 11 to 13, 2001The Lodge at Snowbird Ski ResortWasatch mountains, Utah

Page 9: Agile 101

9

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

AGILE MANIFESTO

Individuals and interactions

Working software

Customer collaboration

Responding to change

Source: http://agilemanifesto.org/

Page 10: Agile 101

SCRUMXPKANBAN

FLAVORSOF

AGILE

SCRUM

Page 11: Agile 101

11

ROLES

Product Owner TEAM Scrum MasterScrum Team

Responsible for “Why & What”

Owns the vision

Prioritize & validate requirements

Responsible for “HOW”

Self-Organized

Estimate & produce working product

Facilitate & Coach

Remove impediments

Focus on culture & practice

Page 12: Agile 101

FLOW

Potentially ShippableProduct Increment

The Requirements

Portion of the Requirements

Work on it for2 weeks

Page 13: Agile 101

BUZZWORD BINGO

Page 14: Agile 101

THE BACKLOG

Page 15: Agile 101

Potentially ShippableProduct Increment

ProductBacklog

“The Requirements”

SprintBacklog

“Portion of the Requirements”

Sprint Duration2 - 4 weeks

ProductOwner

Breakdown requirements

Prioritize Backlog

THE BACKLOG

Page 16: Agile 101

HOW DO WE CREATE A BACKLOG?

ProductOwner

ProductBacklog

Requirements

Theme n

Theme 0

Epic

Story

.

.

.

.

.

.

Page 17: Agile 101

A STORY

As a _____________,

I would like to ______________

so that I could ______________.

Page 18: Agile 101

Potentially ShippableProduct Increment

ProductBacklog

SprintBacklog

“Portion of the Requirements”

Sprint Duration2 weeks

SPRINT BACKLOG

Page 19: Agile 101

SPRINT PLANNINGDAY 1 : Beginning of a sprint

Page 20: Agile 101

Potentially ShippableProduct Increment

ProductBacklog

SprintBacklog

Sprint Duration2 - 4 weeks

ProductOwner

Review Prioritized Backlog

Estimate work

SPRINT PLANNING

TEAMScrumTeam

ScrumMaster

Page 21: Agile 101

STORY POINTS

1, 2, 3, 5, 8, 13, 21, ?

Page 22: Agile 101

DAILY STAND-UPDid yesterdayDoing today

Any impediments?

Page 23: Agile 101

CRAWL. WALK. RUN.

This has nothing to do with Agile

Page 24: Agile 101

BURN DOWN CHART

Work left Vs. Time left

Baked into JIRA

Page 25: Agile 101

BURN DOWN CHART

25

Page 26: Agile 101

VELOCITY

Story Points / Sprint

Calculated for an individual & the team

Page 27: Agile 101

BURN DOWN CHART

Page 28: Agile 101

SPRINT DEMO

Review work done in a Sprint

Day 9 - 10

Page 29: Agile 101

THE RETROSPECTIVE

At the end of a Sprint

Team reflects on the good, the bad and the ugly

Day 10

Page 30: Agile 101

I KNOW IT’S SCARY OUT THERE...

Page 31: Agile 101

Questions, Comments, Feedback?

THANK YOU