Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Like this? Share it with your network

Share

Making Product Development Agile

on

  • 835 views

Stacey Berlow

Stacey Berlow
President, Project Balance
Product Camp NYC
November 6, 2010

Statistics

Views

Total Views
835
Views on SlideShare
835
Embed Views
0

Actions

Likes
0
Downloads
12
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

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

Making Product Development Agile Presentation Transcript

  • 1. Making Product Development Agile
    Stacey Berlow
    President, Project Balance
    Product Camp NYC
    November 6, 2010
  • 2. All rights reserved. Copyright 2010
    Learning Objectives
    Learn about the core values of the Agile framework
    Understand how the framework helps teams be more customer oriented
    Take one idea away that you an immediately use in your product development efforts
  • 3. Agenda
    Overview of Agile principles – 15 minutes
    Group exercises – 20 minutes
    Group discussion – 10 minutes
    Wrap up – 5 minutes
    All rights reserved. Copyright 2010
  • 4. All rights reserved. Copyright 2010
    Origins of Agile
    1950s: US Department of Defense and NASA
    used iterative and incremental development
    1960s: Evolutionary project management (Evo)
    recommends two-week iterations focusing on delivery of product each iteration
    1986: Takeuchi and Nanoka
    Wrote seminal paper “The New New Product Development Game” Discussed the “rugby approach” of dedicated, self-organizing, cross functional teams
    1990s: Agile methodologies take off
    Scrum, Extreme Programming, Rational Unified Process, Dynamic Systems Development Model
    2001: Agile Manifesto written
  • 5. All rights reserved. Copyright 2009
    http://agilemanifesto.org/
  • 6. All rights reserved. Copyright 2010
    Individuals and interactionsoverprocesses and tools
    Agile approach focuses on empowered, self-managing teams
    You must consider all aspects about the people on your team and how they work together
    Communication and team collaboration are key to creating innovative products
  • 7. Individuals and interactionsoverprocesses and tools
    Examples of cross functional teams:
    Advertisement development:
    • Artist, copy writer, language translator, product owner, operations
    Healthcare software:
    • Physicians/clinicians, program managers, business analysts software developers, testers
  • All rights reserved. Copyright 2010
    Working software (product features) overcomprehensive documentation
    The project progress is measured by the number of working features
    Even with very detailed specs, the design is likely to change as it is built
    Documentation is an absolute requirement. But the primary goal is to produce a product not documents
  • 8. Working software (product features)overcomprehensive documentation
    Examples:
    Advertisement campaign:
    • Prototypes/mock ups
    Healthcare software:
    • Prototypes, completed features
  • All rights reserved. Copyright 2010
    Customer collaborationovercontract negotiation
    The customer become a part of the development process
    Part of the development process is to discover what the customer needs
    Customer feedback is essential at every step of the process
  • 9. Customer collaborationovercontract negotiation
    Examples:
    Advertisement development:
    • PM shows ads to consumers and gets feedback
    • 10. Customer sends in ideas to a website or blog
    • 11. PM participates in every aspect of the planning to understand time, cost and quality constraint.
    Healthcare software:
    • Physicians/clinicians drive features requirements
    • 12. Customer sees and approves mock ups
    • 13. Test and approve software before release
    • 14. They work with team on timing of new releases
  • All rights reserved. Copyright 2010
    Responding to changeoverfollowing a plan
    Many factors can and will change over the course of the project
    Being able to respond to change is essential
    The cyclic nature and iterative development allows the team to respond to change
    Planning is a requirement and must be done continuously throughout the project
  • 15. Responding to changeoverfollowing a plan
    Examples:
    Advertisement campaign:
    • PM finds out that a competitor has just launched a new product and changes the ad copy in one of the iterations
    • 16. During the campaign you set specific iterations/check point at which time you can adjust the copy, distribution. Etc.
    Healthcare software:
    • Physicians/clinicians drive the new feature set
    • 17. Physicians/clinicians drive the order in which the features are developed
  • The Agile framework focuses on activities to provide early customer value
  • 18. All rights reserved. Copyright 2010
    Value-Driven versus Plan-Driven
    Traditional
    Agile
    Features Resources + Schedule
    Set These First
    Value-driven
    Plan-driven
    Agile flips the triangle.
    Resources + ScheduleFeatures
    … Then Calculate
    Reference: The Software Project Manager’s Bridge to Agile
  • 19. All rights reserved. Copyright 2010
    What Makes a Process Agile?
    Product development iterations
    Feedback loop with customers before the product ships
    Looking at the trade-offs between new development and fixing defects
    Adjusting in real time what gets developed and fixed in each iteration
  • 20. All rights reserved. Copyright 2010
    Agile Is Not…
    Informal
    “Hack and pack”, “Cowboy Coding”
    Document free
    A free for all
  • 21. Discussion Questions
  • 22. Agile Resources
    Agile Software Development with Scrum by Ken Schwaber (Prentice Hall, 2002)
    http://www.scrumalliance.org/
    Improving Software Economics White Paper by Walker Royce (IBM Rational, May 2009) ftp://public.dhe.ibm.com/common/ssi/sa/wh/n/raw14148usen/RAW14148USEN.PDF
    Agile Adoption Patterns by AmrElssamadisy (Addison-Wesley, 2009)
    All rights reserved. Copyright 2010
  • 23. Thank You
    Email is Welcome
    sberlow@projectbalance.com