Agile estimation and planning by bachan anand ( sep 10th)


Published on

Overview of Agile and Scrum
Vision and Product
Agile planning
Release Planning
Iteration Planning
Daily Planning

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Agile estimation and planning by bachan anand ( sep 10th)

  1. 1. Agile Estimation and Planning Prepared by Bachan AnandWe will be starting at 8:00 AM PST/ 11:00 AM ESTPlease dial in to +1 (775) 996-3560 PIN: 699601# Or Dial using VOIP
  2. 2. 2 Agenda• Overview of Agile and Scrum• Vision and Product• Agile planning• Release Planning• Iteration Planning• Daily Planning• Q&A Please dial in to +1 (775) 996-3560 PIN: 699601#
  3. 3. Overview of Agile and ScrumPlease dial in to +1 (775) 996-3560 PIN: 699601#
  4. 4. 4 Overview of Agile and Scrum Agile Manifesto• Agile is a set of values: ▫ Individuals and interactions over processes and tools ▫ Working software (Products) over comprehensive documentation ▫ Customer collaboration over contract negotiation ▫ Responding to change over following a plan Please dial in to +1 (775) 996-3560 PIN: 699601#
  5. 5. 5 Overview of Agile and Scrum Agile Principles• Highest priority is to satisfy the customer through early and continuous delivery of valuable software/products• Welcome changing requirements• Deliver working software (product) frequently• Business people and developers must work together daily throughout the project Please dial in to (218) 895-4640 PIN: 3289145
  6. 6. 6 Overview of Agile and Scrum Agile Principles• Build projects around motivated individuals• Most efficient and effective method of conveying information is face-to-face conversation• Working software (product) is the primary measure of progress• Agile processes promote sustainable development (maintain a constant pace indefinitely) Please dial in to +1 (775) 996-3560 PIN: 699601#
  7. 7. 7 Overview of Agile and Scrum Agile Principles …cont’d• Continuous attention to technical excellence and good design enhances agility• Simplicity (art of maximizing amount of work not done) is essential• Best architectures, requirements, and designs emerge from self-organizing teams• At regular intervals, team reflects on how to become more effective, then tunes and adjusts Please dial in to +1 (775) 996-3560 PIN: 699601#
  8. 8. 8 Overview of Agile and Scrum What is Scrum• Scrum is an Agile framework that supports lightweight processes that emphasize: ▫ Incremental deliveries ▫ Quality of Product ▫ Continuous improvement ▫ Discovery of people’s potential• Scrum is simple to understand, but requires discipline in order to be successful• Scrum is not a methodology
  9. 9. 9 Overview of Agile and Scrum Foundations of Scrum• Empiricism ▫ Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cycles• Self-Organization ▫ Small teams manage their own workload and organize themselves around clear goals and constraints• Prioritization ▫ Do the next right thing• Rhythm ▫ Allows teams to avoid daily noise and focus on delivery• Collaboration ▫ Leaders and customers work with the Team, rather than directing them
  10. 10. 10 Overview of Agile and Scrum Core Values• Transparency ▫ Everything about a project is visible to everyone• Commitment ▫ Be willing to commit to a goal• Courage ▫ Have the courage to commit, to act, to be open and to expect respect• Focus ▫ Focus all of your efforts and skills on doing the work that you have committed to doing• Respect ▫ Respect and trust the different people who comprise a team
  11. 11. 11 IterationSprint Cycle
  12. 12. Vision and ProductPlease dial in to +1 (775) 996-3560 PIN: 699601#
  13. 13. 13The Product Vision----Why?• The Vision serves as a common bonding to the Project, every participant needs to understand and share it, to be able to contribute effectively
  14. 14. 14 The Vision Board- Visible to the team- Maintained by the Product Owner/ Customer
  15. 15. 15 Role: Product Owner• Thought Leader and Visionary• Steers the Product Vision (for example, with Story Mapping)• Prioritizes the Goals - User Stories• Maintains the Product Backlog with the team• Accepts the Working Product (on behalf of the customer)
  16. 16. Agile planningPlease dial in to +1 (775) 996-3560 PIN: 699601#
  17. 17. 17Why Plan?• Gives the Product Owner & Customer Opportunity to explain the vision, goals and requirements.• Helps in fulfillment of customer specification.• Communicate the bigger picture to team members• Keep teams focus on what can be achieved
  18. 18. 18Why We Need Plans?• To predict the future• To communicate our expectation• To be able to compare our predictions with the reality we are facing• To guide us to the desired situation/state
  19. 19. 19What is a good plan?► A good plan is one that supports reliable decision-making► One that increases in accuracy and precision over time  We’ll be done in the fourth quarter  We’ll be done in November  We’ll be done November 7th “It is better to be roughly right than precisely wrong.” -John Maynard Keynes
  20. 20. 20What makes planning “Agile”?•Focus on planning – not the plan•Re plan based on reality•Involve people who are doing the work in planning•Balance benefit and investment•Adaptive to change and learning•Plans are easily changed•Planning is continuous throughout the project
  21. 21. 21Different levels of planning
  22. 22. 22Agile Planning Lifecycle Summary
  23. 23. 23The Goals Of Release Planning• A time question: How many iterations approximately will we need to deliver this rough scope having the resources we might have?• Scope question: How much of this rough product backlog can we do within this range of sprints and having the resources we might have?• Resources question: What resources do we need to accomplish this rough scope within this range of sprints?• How rough can this be? What level of accuracy do we need?• What things do we need to know to make each of these predictions?
  24. 24. 24The Goals Of Iteration Planning• Duration is fixed.• Resources are fixed and dedicated.• Scope is open for discussions: how many backlog items (stories) can we do during the sprint?• What level of accuracy do we need here?• What we need to know to make the prediction?
  25. 25. 25The Goals Of Daily Planning• Why we need this planning?• How formal should this level of planning be?• Who participated in Daily planning?• Should you do it more often?• Why is this usually out of scope in project running by a predictive process (e.g. waterfall)?
  26. 26. Release planningPlease dial in to +1 (775) 996-3560 PIN: 699601#
  27. 27. 27Release Planning• How many iterations?• How much scope?• At what costs?
  28. 28. 28Estimating Backlog• Backlog items expressed as User Stories• Team estimates the Product Backlog• Estimated in relative size• Estimated 1 or 2 days before start of your iteration• Discussing during the estimation more important that the estimates• Planning Poker
  29. 29. 29Sizing Release/Product BacklogProduct Backlog (Stories) Iteration Backlog (Tasks) Hours Story Points or Ideal Days
  30. 30. 30Estimate Size – Derive Duration
  31. 31. 31 Velocity• A rate at which the team is able to convert product backlog items into working product.• Measured for each iteration• Expressed in relative size ▫ Story points ▫ Number of Stories• Used as a reference by teams when committing for the next Iteration
  32. 32. 32 Release planning Release Burndown• Shows progress across Sprints• X-axis is the number of Sprints• Y-axis is the total number of stories
  33. 33. Iteration planningPlease dial in to +1 (775) 996-3560 PIN: 699601#
  34. 34. 34 Iteration planning Spirit behind User Stories• System requirements formulated as one or more sentences in the everyday or business language of the user ▫ As a <user>, I would like <function> so that I get <value>• Each User Story has an associated Acceptance Criteria that is used to determine if the Story is completed
  35. 35. 35 Iteration planning A Good User Story …• Independent ▫ Not overlap in concept and be able to schedule and implement them in any order• Negotiable ▫ Not an explicit contract for features; rather, details will be co-created by Product Owner and Team• Valuable ▫ Add business value• Estimated ▫ Just enough to help the Product Owner rank and schedule the storys implementation• Sized Appropriately ▫ Need to be small, such as a few person-days• Testable ▫ A characteristic of good requirements
  36. 36. 36Iteration Planning• Select the top PB items for the iteration ▫ PO’s involvement is key and mandatory• Team builds the task list for completing the stories• Output in an Iteration Plan or Sprint Backlog• Team makes a commitment at end of the planning session
  37. 37. Daily planningPlease dial in to +1 (775) 996-3560 PIN: 699601#
  38. 38. 38 Daily planning: Daily Standup• Meetings held in same location, same time, every day• Time boxed at 15 minutes• Helps the “team” to plan everyday• Each Team member speaks to: ▫ What did I accomplish in the last 24 hours ▫ What do I plan to accomplish in the next 24 hours ▫ Any impediments getting in the way of my work
  39. 39. 39 Daily Planning: Taskboard• Active visual indicator of flow of work• Should be visible to team members at all times• Kept current by the team• Reflection of Iteration commitment vrs reality
  40. 40. 40 Daily planning : Burndown• Shows daily progress in the Sprint• X-axis is the number of days in the Sprint• Y-axis is the number of remaining stories
  41. 41. 41 What is in it for me? (Customer)• As a customer , I am ▫ Kept closer to reality of the project during execution phase ▫ Involved in Release planning and prioritization ▫ Able to make priority changes at Iteration boundaries
  42. 42. 42What is in it for me? (Leadership)• As a Leader , I want ▫ To understand progress in terms of real progress made on product . ▫ Better deal with changing business priorities
  43. 43. 43What is in it for me? ( Team Member)• As a team member, I want ▫ Able to make a realistic commitments ▫ Provide estimated based of past data ▫ Right balance between planning and doing
  44. 44. 44Learn By Doing• Apply few practices at a time• Understand the values and foundations• Inspect and Adapt• Experience the Joy of Being Agile
  45. 45. 45Experiential Training
  46. 46. 46Pay-it-forward / Donation only-- 1 day Agile & Scrum Training- August 26th – Atlanta- Sep 30th - Boston- Sep 30th – San Diego- Oct 1st - Irvine- Oct 20th – Pheonix- Oct 21st – Denver- Nov 11th – Seattle- Nov 14th – Portland
  47. 47. 47User groups /Communities• APLN – Agile Project Leadership Network• Scrum Alliance – Scrum User Groups• Online User Groups Scrum Alliance
  48. 48. 48Q&A
  49. 49. 49Few thoughts….• Planning is important• Plan as often and spend as less time as possible each time• Plan changes, embrace reality and change your plan every time you plan
  50. 50. 50Donation only 1 day Trainings▫ Atlanta– September 26th▫ Boston – September 30th▫ San Diego – September 30th▫ Irvine – October 1st▫ Pheonix– October 20th▫ Denver– October 21st
  51. 51. 51Thank you !• More Resources at ▫ and-resources/ Contact Info Bachan Anand 949-232-8900