Agile Design and Development

315 views
286 views

Published on

How we design Woople using agile design and develop

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
315
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Agile Design and Development

    1. 1. How we build Woople Using Agile Design & Development Max Cameron, Product Manager, Woople
    2. 2. Table of Contents• Presentation goals• July 1st feature estimates• Woople release cycle• Why we estimate• How can we communicate effectively?
    3. 3. Presentation Goals
    4. 4. Presentation Goals• Answer the question: “When will we have reporting?”• Understand the challenge we face• Understand our methods & practices• Make good decisions moving forward• Learn about the pressure you encounter
    5. 5. Pivotal Tracker Reports
    6. 6. How did we get here?• Two countries• Stakeholders, Designers, Engineers,• Many tough decisions
    7. 7. Planning Hierarchy Product Roadmap 12-16 months Release Plan 6-8 weeks Iteration Plan 2 weeks Day Plan 5 hours
    8. 8. Release Cycle
    9. 9. Release Cycle RequirementsTesting & Acceptance User Goals Implementation Prioritization Design & Estimation
    10. 10. Requirements
    11. 11. Requirements• Business focused• Fuzzy• Visionary• Problem statements• Multiple stakeholders
    12. 12. Goal Centred Design
    13. 13. Goal Centred Design• Requirements to goals• Format of a defined user goal • Role: “As a...” • Goal: “I want to...” • Rationale: “So that...”• Implementation agnostic• Validation criteria baked in
    14. 14. Prioritization• Ownership of decision-making• Collaboration• Pragmatism
    15. 15. Design
    16. 16. Design ModellingSketches & Diagrams Personas Generation Workflows
    17. 17. Implementation 2 week iterations BugsDocumentation Detailed Design Programming Task Breakdown Unit Testing
    18. 18. Testing and Acceptance• Defects removed• Workflows optimized based on user feedback
    19. 19. Why Estimates?
    20. 20. Uncertainty
    21. 21. Sailing Across the Ocean ... without a GPS
    22. 22. Safety in Commitment• Padded• Wrong
    23. 23. What Gives?Price Speed Quality
    24. 24. What Gives?Fixed Budget Efficiency is skill Open Season
    25. 25. True Velocity exercise week natural velocity requested velocity delivered 1 30 32 32 2 28 30 30 3 26 28 28 4 24 26 26 5 22 24 24
    26. 26. Communication Strategy Discussion• When will we have X?• What will it look like?• A better question: What will we have on July 1st?
    27. 27. Thank You Reach out anytime

    ×