Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Wagile Product Development - Being Agile with Waterfall Clients

409 views

Published on

Slides Jessica Fredican recently used in his discussion w/ mentees of The Product Mentor.

Synopsis: Working with enterprise clients accustomed to waterfall development can be challenging. Taking a "wagile" approach can help your team stay agile while managing client expectations.

The Product Mentor is a program designed to pair Product Mentors and Mentees from around the World, across all industries, from start-up to enterprise, guided by the fundamental goals…Better Decisions. Better Products. Better Product People.

Throughout the program, each mentor leads a conversation in an area of their expertise that is live streamed and available to both mentee and the broader product community.

http://TheProductMentor.com

Published in: Business
  • Be the first to comment

  • Be the first to like this

Wagile Product Development - Being Agile with Waterfall Clients

  1. 1. WAGILE: BEING AGILE WITH WATERFALL CLIENTS Jessica Fredican @jessicafredican
  2. 2. Agenda What is Wagile? How does it work? When to use it?
  3. 3. Waterfall Challenges
  4. 4. Agile Ideals Are Great  Individuals and interactions over processes and tools  Working software over comprehensive documentation  Customer collaboration over contract negotiation  Responding to change over following a plan - Agile Manifesto
  5. 5. Agile doesn’t work for everyone
  6. 6. Wagile Agile Ideals  Focus on delivering value  Frequent customer validation  Ability to respond to change Agile Waterfall Wagile Waterfall Reality  Defined Releases  Defined Test Periods  Planning Periods
  7. 7. Roadmapping in Wagile Establish client and external stakeholder planning periods Groom major feature sets and themes Validate directional roadmap with stakeholders Prioritize and size work
  8. 8. Delivery in Wagile Regular but flexible release schedule Set theme or define a single feature for the release Communicate theme/single feature externally Manage release backlog internally
  9. 9. Product Validation in Wagile Roadmap validation with customers and stakeholders Release theme validation with customers and stakeholders Frequent informal validation with users and stakeholders End-of-Release User Acceptance Testing
  10. 10. Wagile is successful with… Enterprise clients Organizations transitioning from waterfall Updates require new install Users have a low change tolerance
  11. 11. Transitioning Waterfall to Wagile Get stakeholders comfortable with uncertain reality Agile education Ships don’t turn on a dime
  12. 12. Thank you

×