agile-planning

Amir Barylko - Agile User Group Apr ‘11 MavenThought Inc.

AMIR BARYLKO

AGILE PLANNING

AGILE USER GROUPAPRIL 2011

1Tuesday, April 5, 2011


WHO AM I?

•Quality Expert

• Architect

•Developer

•Mentor

• Great cook

• The one who’s entertaining you for the next hour!



RESOURCES

• Email: [email protected]

• Twitter : @abarylko

• Blog: http://www.orthocoders.com

•Materials: http://www.orthocoders.com/presentations


mailto:[email protected]


http://www.orthocoders.com/presentations



INTROWhy projects fail?

Reality CheckThe agile manifesto

Agile Principles



WHY PROJECTS FAIL?

•Delivering late or over budget

•Delivering the wrong thing

•Unstable in production

•Costly to maintain



REALITY CHECK

• It is impossible to gather all the requirements at the beginning of a project.

•Whatever requirements you do gather are guaranteed to change.

•There will always be more to do than time and money will allow.



AGILE MANIFESTO(HTTP://AGILEMANIFESTO.ORG/

Individuals and interactions OVER Process and Tools

Customer collaboration OVER Contract negotiation

Working software OVERComprehensive documentation

Responding to change OVER Following a plan


http://agilemanifesto.org/

http://agilemanifesto.org/


AGILE PRINCIPLES

•Continuous Delivery

•Embrace Change

•Self-organize

•Self-sustained

•Business and developers collaboration

•Team ownership



FEASIBILITYHigh Level Estimates

Risks



HIGH LEVEL ESTIMATE(ONLY A GOOD GUESS)

10x

2x

Time

(The Agile Samurai)

2 weeks

6 weeks

12 weeks

24 weeks



RISKS

• Low involvement from the client

•Developers may leave

•No QA team

• ...



REQUIREMENTSUser Stories

SizePlanning Poker



USER STORIES

•Short description of a “feature”

•Avoid technical mumbo-jumbo

•Focus on goals no “how-to”

•Should fit in a card



ADD MOVIES

As a User

I want to add a movie

So I can register the details



SIZE

•Measured in “story points”

•Based on complexity

•Size stories relative to each other

•Relativity is more important that accuracy

•Wait, how do I translate to hours/days?



PLANNING POKER

•The Customer reads a story

•The team asks questions

•At the same time, each member shows a card

•Discuss until reach consensus



DEMO(VOLUNTEERS?)

•Add a movie

•Get reviews

•Sort movies by title



WHERE’S THE PLAN?Back to reality



STATIC PLAN

•Team changes

•Requirements change

•Low quality increases development time

•What can we do?



AGILE PLAN

•Know your backlog of stories

•Use iterations (one to two weeks)

•Estimate velocity (how many points per iteration)

•Update estimations



PLAN UPDATE

•How many iterations?

effort / team velocity



EXAMPLE

• Iteration 1: 15 points




Velocity (avg): 19 points

How many iterations? 190 points / 19 points per iteration = 10 iterations



HOW TO START?

•Create your user story backlog

• Add a movie

• Search movies by title

• Get reviews

• Get posters

• List movies by date and title



HOW TO START? II

• Let the customer choose a release (grouping)

• Sort them by priority

Release 2Get reviews

List movies by date and title

Release 1Add a movie

Search movies by title

Get posters



HOW TO START III

• Size the stories

• Add a movie: 5 points

• Search movies by title: 2 points

• Get reviews: 5 points

• Get posters: 5 points

• List movies by date and title: 1 point



HOW TO START IV

•Have a good guess

•Best case?

•Worst case?

•Start working on iterations

•Estimation after 4th iteration should be stable



ITERATIONSIteration 0 .. N

Quality as a Driver Visual Communication

MetricsManage Scope



ITERATION 0

• Flush out architecture.

• Setup Testing harness for TDD and BDD.

• Setup continuous integration.

• Setup scripts to build, deploy, etc.

• Setup visual communication tools.



ITERATION 1.. N

• Start by Story Planning

• Pair programming (switching often)

•Daily Scrum

• End with Retrospective

Every day!



QUALITY AS A DRIVERRed

GreenRefactor

BDD

TDD

Red

GreenRefactor



VISUAL COMMUNICATION



METRICS



BURN DOWN CHART(REMAINING POINTS PER ITERATION)

• Axis X = iterations

• Axis Y = remaining points to completion

0

25

50

75

100

It 0 It 1 It 2 It 3 It 4 It 5 It 6 it 7

Burdown Chart



MANAGE SCOPE

•Budget

•Time

•Quality

•Scope34Tuesday, April 5, 2011

Amir Barylko - .NET UG Mar ‘11 MavenThought Inc.

QUESTIONS?



RESOURCES

• Email: [email protected]

• Twitter : @abarylko

• Slides: http://www.orthocoders.com/presentations







RESOURCES II



RESOURCES III



TDD TRAINING

•When: May 26 & 27

•More info: http://www.maventhought.com

• Goal: Learn TDD with real hands on examples


http://www.maventhought.com

http://www.maventhought.com

agile-planning

Technology

resources

titleamir

presentationsamir

amirbarylko

amir barylko

good guess

reality check

projects fail