YEG-Agile-planning
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • 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
458
On Slideshare
458
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
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. AMIR BARYLKO AGILE PLANNING EDMONTON AGILE USER GROUP JUNE 2011Amir Barylko - Agile Planning MavenThought Inc.
  • 2. WHO AM I? • Quality Expert • Architect • Developer • Mentor • Great cook • The one who’s entertaining you for the next hour!Amir Barylko - Agile Planning MavenThought Inc.
  • 3. RESOURCES • Email: amir@barylko.com • Twitter: @abarylko • Blog: http://orthocoders.com • Materials: http://orthocoders.com/presentations • Website: http://maventhought.comAmir Barylko - Agile Planning MavenThought Inc.
  • 4. INTRO Why projects fail? Reality Check The agile manifesto Agile PrinciplesAmir Barylko - Agile Planning MavenThought Inc.
  • 5. WHY PROJECTS FAIL? • Delivering late or over budget • Delivering the wrong thing • Unstable in production • Costly to maintainAmir Barylko - Agile Planning MavenThought Inc.
  • 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.Amir Barylko - Agile Planning MavenThought Inc.
  • 7. AGILE MANIFESTO (HTTP://AGILEMANIFESTO.ORG/ Individuals and interactions OVER Process and Tools Customer collaboration OVER Contract negotiation Comprehensive Working software OVER documentation Responding to change OVER Following a planAmir Barylko - Agile Planning MavenThought Inc.
  • 8. AGILE PRINCIPLES • Continuous Delivery • Businessand developers • Embrace Change collaboration • Self-organize • Team ownership • Self-sustainedAmir Barylko - Agile Planning MavenThought Inc.
  • 9. FEASIBILITY High Level Estimates RisksAmir Barylko - Agile Planning MavenThought Inc.
  • 10. HIGH LEVEL ESTIMATE (ONLY A GOOD GUESS) 10x Time 24 weeks 12 weeks 6 weeks 2 weeks (The Agile Samurai) 2xAmir Barylko - Agile Planning MavenThought Inc.
  • 11. RISKS • Low availability of the client • Developers may leave • No QA team • New architecture • ...Amir Barylko - Agile Planning MavenThought Inc.
  • 12. REQUIREMENTS User Stories Size Planning PokerAmir Barylko - Agile Planning MavenThought Inc.
  • 13. USER STORIES • Short description of a “feature” • Avoid technical mumbo-jumbo • Focus on goals no “how-to” • Should fit in a cardAmir Barylko - Agile Planning MavenThought Inc.
  • 14. ADD MOVIES As a User I want to add a movie So I can register the detailsAmir Barylko - Agile Planning MavenThought Inc.
  • 15. 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?Amir Barylko - Agile Planning MavenThought Inc.
  • 16. PLANNING POKER • The Customer reads a story • The team asks questions • At the same time, each member shows a card • Discuss until reach consensusAmir Barylko - Agile Planning MavenThought Inc.
  • 17. DEMO (VOLUNTEERS?) •Add a movie •Get reviews •Sort movies by titleAmir Barylko - Agile Planning MavenThought Inc.
  • 18. WHERE’S THE PLAN? Back to realityAmir Barylko - Agile Planning MavenThought Inc.
  • 19. STATIC PLAN • Team changes • Requirements change • Low quality increases development time • What can we do?Amir Barylko - Agile Planning MavenThought Inc.
  • 20. AGILE PLAN • Know your backlog of stories • Use iterations (one to two weeks) • Estimate velocity (how many points per iteration) • Update estimationsAmir Barylko - Agile Planning MavenThought Inc.
  • 21. PLAN UPDATE •How many iterations? effort / team velocityAmir Barylko - Agile Planning MavenThought Inc.
  • 22. EXAMPLE • Iteration 1: 15 points • Iteration 2: 20 points Velocity (avg): 19 points • Iteration 3: 18 points • Iteration 4: 22 points How many iterations? 190 points / 19 points per iteration = 10 iterationsAmir Barylko - Agile Planning MavenThought Inc.
  • 23. HOW TO START? • Create your user story backlog • Add a movie • Search movies by title • Get reviews • Get posters • List movies by date and titleAmir Barylko - Agile Planning MavenThought Inc.
  • 24. HOW TO START? II • Let the customer choose a release (grouping) • Sort them by priority Release 1 Release 2 Add a movie Get reviews Search movies by title List movies by date and title Get postersAmir Barylko - Agile Planning MavenThought Inc.
  • 25. 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 pointAmir Barylko - Agile Planning MavenThought Inc.
  • 26. HOW TO START IV • Have a good guess • Best case? • Worst case? • Start working on iterations • Estimation after 4th iteration should be stableAmir Barylko - Agile Planning MavenThought Inc.
  • 27. ITERATIONS Iteration 0 .. N Quality as a Driver Visual Communication Metrics Manage ScopeAmir Barylko - Agile Planning MavenThought Inc.
  • 28. 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.Amir Barylko - Agile Planning MavenThought Inc.
  • 29. ITERATION 1.. N • Start by Story Planning • Pair programming (switching often) Every day! • Daily Scrum • End with RetrospectiveAmir Barylko - Agile Planning MavenThought Inc.
  • 30. QUALITY AS A DRIVER Red BDD Red Refactor Refactor TDD Green GreenAmir Barylko - Agile Planning MavenThought Inc.
  • 31. VISUAL COMMUNICATIONAmir Barylko - Agile Planning MavenThought Inc.
  • 32. METRICSAmir Barylko - Agile Planning MavenThought Inc.
  • 33. BURN DOWN CHART (REMAINING POINTS PER ITERATION) Burdown Chart • Axis X = iterations 100 • Axis Y = remaining 75 points to completion 50 25 0 It 0 It 1 It 2 It 3 It 4 It 5 It 6 it 7Amir Barylko - Agile Planning MavenThought Inc.
  • 34. MANAGE SCOPE •Budget •Time •Quality •ScopeAmir Barylko - Agile Planning MavenThought Inc.
  • 35. QUESTIONS?Amir Barylko - Agile Planning MavenThought Inc.
  • 36. RESOURCES • Email: amir@barylko.com • Twitter: @abarylko • Materials: http://orthocoders.com/presentations • Blog: http://orthocoders.com • Website: http://maventhought.comAmir Barylko - Agile Planning MavenThought Inc.
  • 37. RESOURCES IIAmir Barylko - Agile Planning MavenThought Inc.
  • 38. RESOURCES IIIAmir Barylko - Agile Planning MavenThought Inc.