iterations-zero-n

Marc Jeanson & Amir Barylko Iterations 0 to N

MARC JEANSON &AMIR BARYLKO

AGILE PLANNINGITERATIONS 0 - N

AGILE USER GROUPOCT 2011

Tuesday, October 11, 2011


WHO ARE WE?

• Architects

• Developers

• Mentors

• Great cook (not Marc)

• The ones who are entertaining you for the next hour!



RESOURCES

• Email: [email protected] [email protected]

• Twitter : @abarylko, @marcjeanson

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

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



EPISODE IWhy projects fail?

FeasibilityRequirementsAgile planning



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 PRINCIPLES

•Continuous Delivery

•Embrace Change

•Self-organize

•Self-sustained

•Business and developers collaboration

•Team ownership



HIGH LEVEL ESTIMATE(ONLY A GOOD GUESS)

10x

2x

Time

(The Agile Samurai)

2 weeks

6 weeks

12 weeks

24 weeks



USER STORIES

•Short description of a “feature”

•Avoid technical mumbo-jumbo

•Focus on goals no “how-to”

•Should fit in a card



PLANNING POKER

•The Customer reads a story

•The team asks questions

•At the same time, each member shows a card

•Discuss until reach consensus



AGILE PLAN

•Know your backlog of stories

•Use iterations (one to two weeks)

•Estimate velocity (how many points per iteration)

•Update estimations



EPISODE II



DISCLAIMER

• All characters appearing in these work are fictitious.

• Any resemblance to real persons, living or dead, is purely coincidental.

• Any resemblance to your current company, team, manager is intentional.



NOT SO LONG AGOIN A COMPANY

NOT SO FAR AWAY...



A NEW AGILE PROJECTPeer review web application



OUR COMPANY



OUR VP



OUR AGILE TEAM

• Agile Coach

• Project Manager

• Developer

• QA

• you!



PEER REVIEW APP

• Allows employees to answer questions about their peers

• Every member in the team reviews the other members

• The review process is private

• Higher management will have access to the summary of responses



ITERATION 0Process & Communication

ArchitectureTesting harness

Continuous integrationDeployment



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.



PROCESS & COMMUNICATION

• Kanban Board

• No fixed iterations

• Weekly releases

• Weekly 15 min status update (or when needed)

• Minimize meetings



KANBAN BOARD

• Backlog: Features to be done

• Analysis: Features that are being defined (should be sized)

• Working: Features that are in development

• Review (QA): Features that need review before deployment

• Archive: Deployed features (finished 100%)



WIP LIMIT

• Why do we need it?

• How do we choose them?

• Backlog: How many should go here?

• Analysis: 1

• Working: 2

• Review: 1

• What happens if the numbers are wrong?



ARCHITECTURE

• Ruby On Rails

• Model - View - Controllers

• Internal usage

• Security is a concern



TESTING

• Acceptance tests: we are going to use Cucumber and Capybara

• Unit tests: we are going to use rSpec



CONTINUOUS INTEGRATION

• Team City server

• Detect changes in the source

• Builds and notify if tests are broken



DEPLOYMENT

• Scripting using Capistrano

• At then end of the week a new release is deployed

• We can roll back if something goes wrong



ITERATION I - NDEMO



FEATURES

• User login

• See list of pending reviews

• Complete peer review

• Admin: create users

• Manager: CRUD reviews

• Manager: CRUD review questions

• Manager: See review summary

• Statistics?



SUMMARYWhat did we learn today?



ITERATION 0

• Setup your communication tools

• Make sure you can deploy from day 1

• Make sure you “trace” you app across the board

• Make sure BDD and TDD are part of your process

• Make sure you have statistics and alarms ready



AGILE LIFE CYCLE

• Use meetings judiciously when needed

• Rely on the visual tools to get status

• Testing is a key factor, high quality all the way!

• Look at the metrics to understand what’s going on

• Work as a team embracing the product

• Don’t be afraid of “blurred” roles



QUESTIONS?



RESOURCES

• Email: [email protected] [email protected]

• Twitter : @abarylko, @marcjeanson

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

• KanbanFu: https://github.com/amirci/KanbanFU(agilewpg branch)

• KanbanStats: https://github.com/amirci/zenboard (kanbanfu branch)

• Demo Code: https://github.com/marcjeanson/peer_reviewer



RESOURCES II



RESOURCES III



CLOJURE TRAINING

• When: Nov 6, 7 & 8

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

• Goal: Learn Clojure and functional programming with real hands on examples


iterations-zero-n

Technology

xed iterations weekly

review process

development review qa

setup continuous integration

backlog of stories

setup testingharness

setup scripts

kanban board backlog