Agile Design and Development
Upcoming SlideShare
Loading in...5
×
 

Agile Design and Development

on

  • 299 views

How we design Woople using agile design and develop

How we design Woople using agile design and develop

Statistics

Views

Total Views
299
Views on SlideShare
299
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

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
  • \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 Agile Design and Development Presentation Transcript

  • How we build Woople Using Agile Design & Development Max Cameron, Product Manager, Woople
  • Table of Contents• Presentation goals• July 1st feature estimates• Woople release cycle• Why we estimate• How can we communicate effectively?
  • Presentation Goals
  • 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
  • Pivotal Tracker Reports
  • How did we get here?• Two countries• Stakeholders, Designers, Engineers,• Many tough decisions
  • Planning Hierarchy Product Roadmap 12-16 months Release Plan 6-8 weeks Iteration Plan 2 weeks Day Plan 5 hours
  • Release Cycle
  • Release Cycle RequirementsTesting & Acceptance User Goals Implementation Prioritization Design & Estimation
  • Requirements
  • Requirements• Business focused• Fuzzy• Visionary• Problem statements• Multiple stakeholders
  • Goal Centred Design
  • 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
  • Prioritization• Ownership of decision-making• Collaboration• Pragmatism
  • Design
  • Design ModellingSketches & Diagrams Personas Generation Workflows
  • Implementation 2 week iterations BugsDocumentation Detailed Design Programming Task Breakdown Unit Testing
  • Testing and Acceptance• Defects removed• Workflows optimized based on user feedback
  • Why Estimates?
  • Uncertainty
  • Sailing Across the Ocean ... without a GPS
  • Safety in Commitment• Padded• Wrong
  • What Gives?Price Speed Quality
  • What Gives?Fixed Budget Efficiency is skill Open Season
  • 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
  • Communication Strategy Discussion• When will we have X?• What will it look like?• A better question: What will we have on July 1st?
  • Thank You Reach out anytime