Iterations-zero-n
Upcoming SlideShare
Loading in...5
×
 

Iterations-zero-n

on

  • 650 views

Presentation done at the WPG agile user group about iterations zero and one to N

Presentation done at the WPG agile user group about iterations zero and one to N

Statistics

Views

Total Views
650
Views on SlideShare
650
Embed Views
0

Actions

Likes
0
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Iterations-zero-n Iterations-zero-n Presentation Transcript

    • MARC JEANSON & AMIR BARYLKO AGILE PLANNING ITERATIONS 0 - N AGILE USER GROUP OCT 2011Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • WHO ARE WE? • Architects • Developers • Mentors • Great cook (not Marc) • The ones who are entertaining you for the next hour!Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • RESOURCES • Email: amir@barylko.com marc@redlinesoftware.com • Twitter: @abarylko, @marcjeanson • Blog: http://www.orthocoders.com • Materials: http://www.orthocoders.com/presentationsMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • EPISODE I Why projects fail? Feasibility Requirements Agile planningMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • WHY PROJECTS FAIL? • Delivering late or over budget • Delivering the wrong thing • Unstable in production • Costly to maintainMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • 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.Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • AGILE PRINCIPLES • Continuous Delivery • Businessand developers • Embrace Change collaboration • Self-organize • Team ownership • Self-sustainedMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • HIGH LEVEL ESTIMATE (ONLY A GOOD GUESS) 10x Time 24 weeks 12 weeks 6 weeks 2 weeks (The Agile Samurai) 2xMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • USER STORIES • Short description of a “feature” • Avoid technical mumbo-jumbo • Focus on goals no “how-to” • Should fit in a cardMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • PLANNING POKER • The Customer reads a story • The team asks questions • At the same time, each member shows a card • Discuss until reach consensusMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • AGILE PLAN • Know your backlog of stories • Use iterations (one to two weeks) • Estimate velocity (how many points per iteration) • Update estimationsMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • EPISODE IIMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • 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.Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • NOT SO LONG AGO IN A COMPANY NOT SO FAR AWAY...Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • A NEW AGILE PROJECT Peer review web applicationMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • OUR COMPANYMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • OUR VPMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • OUR AGILE TEAM • Agile Coach • Project Manager • Developer • QA • you!Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • 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 responsesMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • ITERATION 0 Process & Communication Architecture Testing harness Continuous integration DeploymentMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • 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.Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • PROCESS & COMMUNICATION • Kanban Board • No fixed iterations • Weekly releases • Weekly 15 min status update (or when needed) • Minimize meetingsMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • 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%)Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • 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?Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • ARCHITECTURE • Ruby On Rails • Model - View - Controllers • Internal usage • Security is a concernMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • TESTING • Acceptance tests: we are going to use Cucumber and Capybara • Unit tests: we are going to use rSpecMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • CONTINUOUS INTEGRATION • Team City server • Detect changes in the source • Builds and notify if tests are brokenMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • DEPLOYMENT • Scripting using Capistrano • At then end of the week a new release is deployed • We can roll back if something goes wrongMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • ITERATION I - N DEMOMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • FEATURES • User login • Manager: CRUD review questions • See list of pending reviews • Manager: See review • Complete peer review summary • Admin: create users • Statistics? • Manager: CRUD reviewsMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • SUMMARY What did we learn today?Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • 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 readyMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • 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” rolesMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • QUESTIONS?Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • RESOURCES • Email: amir@barylko.com marc@redlinesoftware.com • 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_reviewerMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • RESOURCES IIMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • RESOURCES IIIMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
    • CLOJURE TRAINING • When: Nov 6, 7 & 8 • More info: http://www.maventhought.com • Goal: Learn Clojure and functional programming with real hands on examplesMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011