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

Like this? Share it with your network

Share

Iterations-zero-n

  • 721 views
Uploaded on

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

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
721
On Slideshare
721
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
4
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. MARC JEANSON & AMIR BARYLKO AGILE PLANNING ITERATIONS 0 - N AGILE USER GROUP OCT 2011Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 2. 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
  • 3. 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
  • 4. EPISODE I Why projects fail? Feasibility Requirements Agile planningMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 5. 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
  • 6. 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
  • 7. 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
  • 8. 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
  • 9. 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
  • 10. 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
  • 11. 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
  • 12. EPISODE IIMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 13. 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
  • 14. NOT SO LONG AGO IN A COMPANY NOT SO FAR AWAY...Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 15. A NEW AGILE PROJECT Peer review web applicationMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 16. OUR COMPANYMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 17. OUR VPMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 18. OUR AGILE TEAM • Agile Coach • Project Manager • Developer • QA • you!Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 19. 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
  • 20. ITERATION 0 Process & Communication Architecture Testing harness Continuous integration DeploymentMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 21. 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
  • 22. 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
  • 23. 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
  • 24. 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
  • 25. ARCHITECTURE • Ruby On Rails • Model - View - Controllers • Internal usage • Security is a concernMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 26. 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
  • 27. 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
  • 28. 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
  • 29. ITERATION I - N DEMOMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 30. 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
  • 31. SUMMARY What did we learn today?Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 32. 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
  • 33. 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
  • 34. QUESTIONS?Marc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 35. 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
  • 36. RESOURCES IIMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 37. RESOURCES IIIMarc Jeanson & Amir Barylko Iterations 0 to NTuesday, October 11, 2011
  • 38. 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