1 / 11

Software Product Strategy Week Three Tony Wasserman Spring 2013

Software Product Strategy Week Three Tony Wasserman Spring 2013. Underlying Issues for Tasks 1 and 2. How far can you go in an initial release? What must be in the initial version of the product to capture customers? What did you intentionally leave out?

sirius
Download Presentation

Software Product Strategy Week Three Tony Wasserman Spring 2013

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Product Strategy Week Three Tony Wasserman Spring 2013

  2. west.cmu.edu Underlying Issues for Tasks 1 and 2 • How far can you go in an initial release? • What must be in the initial version of the product to capture customers? • What did you intentionally leave out? • How do you address the “whole product”?

  3. west.cmu.edu Where Do You Go From Here? • Plan for successive releases • Enhancements – new features • Enhancements – non-functional • Sources of feature enhancements • Your previous planning • Bugs and vulnerabilities • User requests • Competitive matchups

  4. west.cmu.edu How Often to Release an Update? • Different for user-installable vs. SaaS products • Enterprise and government customers favor stability • Consumers and developers prefer more frequent updates • Planned vs. unplanned updates

  5. west.cmu.edu General Approach to Roadmap Planning • Identify major enhancements (1-2 years) • Estimate required effort for each • Create possible themes for future releases • Performance • Enterprise support (e.g., directories, Exchange) • Integration with third party products • Usability • Try to group enhancements into themes

  6. west.cmu.edu Creating the Roadmap • Decide on timing for next releases • Prioritize • What can you fit in? • Leave slack for customer requests and fixes • Don’t forget hidden features, e.g., analytics • Think about market impact

  7. west.cmu.edu How Far Can You Project? • Hard to go beyond two years • World changes • New competitive forces • Customers drive direction

  8. west.cmu.edu How Can We Possibly Do This in a Week?! • Cut to fit!

  9. west.cmu.edu How to Cut…Step 1 • Make a list of requirements that didn’t make the cut for your first release • Make a list of subsequent ideas that didn’t make it into the requirements • Make a list of non-functional rqts. that need attention as user population grows • Tag each as priority A, B, or C Two hours max

  10. west.cmu.edu How to Cut…Step 2 • Make a SWAG estimate for the work needed to implement Priority A tasks • Compare to planned release interval • Less than 50% of time filled? • Yes – add related lower priority tasks • No – separate user-visible features • Repeat as needed • Name each release by key enhancement

  11. Questions? Miramar State Beach Image source: www.flickr.com/photos/tony_wasserman

More Related