1. Answer the Call: Help Product Owners Define and Prioritize Requirements So many decisions, more time than we thought

2. Kent J. McDonald Business Systems Coach, Knowledge Bridge Partners Founding Partner, Accelinnova So many decisions, more time than we thought

3. Overview  Problems  Value Models Today  Why It Doesn’t Work  Considerations  Purpose  New Models  Example

4. The Problem(s)  “The Business” Expects Us to Do “The Right Things”  Methodologies Tell Us How to Do Things Right How Do We Do This? Who Decides? And When?

5. Features and Functions Never Used 45% Rarely Used 19% Sometimes 16% Often 13% Always 7% Always or Often Used: 20% Never or Rarely Used: 64% Standish Group Study, reported by CEO Jim Johnson, XP2002

6. Value Models How Do You Determine Costs? How Do You Determine Benefits?

7. Costs  Costs Associated with the Team  Hardware Costs  Software Licensing Costs  Vendor Service Costs  Impact to Operations (Extra Staff)

8. Benefits  Increased Revenue  Cost Reductions  Opportunity Costs Avoided  Fee and Penalty Avoidance  Support of Other Initiatives  Reputation  Improved Customer Satisfaction

9. Value Models This Is Hard….

10. Measuring Business Value  Many Different Approaches  Cash Flow  Net Present Value  Internal Rate of Return  Return on Investment  These Can All Be Gamed  Uncertainty Hard to Factor  Other Factors Impact Value

11. Considerations Impact Value

12. Considerations Things That Could Impact Value: Risks  Risks  Assumptions  Constraints

13. Risks  Technical Difficulties  Changes in Market Conditions  Team Makeup and Skill Set  Domain Knowledge

14. Assumptions  Availability of Team Members  Market Demand for Product  Team Velocity  Understanding of Domain Knowledge

15. Constraints  Market Window  External Events  Compliance Dates  Budget Limit  Team Members  Technical Architecture  “Non Functional” Requirements

16. Collaboration Process  Agree to Purpose of Exercise  Brain Write  Stick Items on a Wall  Group Like Items Together  Provide Headlines for Groupings  Vote for Priority

17. Considerations Impact Value That Didn’t Help Much… How Do You Justify a Project That Does Not Provide Positive Business Value?

18. It’s a “Strategic Project”

19. Value Model

20. Project Purpose Optimist’s View: What Job Is the Project Trying to Get Done? Pessimist’s View: What Problem Is the Project Trying to Solve? The Key Is Common Understanding.

21. Purpose Tools to Help Discover Purpose:  Purpose-Based Alignment Model  The 5 Questions  Elevator Statement  Innovation Game

22. Strategic Development MissionVisionValues Strategic Intent ~ Strategy ~ Purpose Long-Range Goals Annual Objectives Action Plans (what, who, when) Individual Business Objectives Tactical Strategic SCO / 5Q

23. Strategic Development MissionVisionValues Strategic Intent ~ Strategy ~ Purpose Long-Range Goals Annual Objectives Action Plans (what, who, when) Individual Business Objectives Tactical Strategic SCO / 5Q Start Here

24. Strategic Intent Cost Leadership Best Customer Solution Competitive Position Strategic Scope CostDifferentiation Broad Narrow Product Leadership Where is Your Organization ?

25. Defining Strategy Answer These Questions: 1.Whom do we serve and what do they want and need most? 2.What services do we provide to help them? 3.How do we know we’re doing a good job? 4.What is the best way to provide these services? 5.How should we organize to deliver these services? Strategic Decision Filters Identifies Strategic Decision Filters

26. Purpose-Based Alignment Market Differentiating High Low Mission Critical Low High Differentiating ParityWho Cares? Partner Purpose Does Not Equal Priority

27. Purpose Statement Stating the Purpose: Your Elevator Statement For Products and Services:  Who Is It For?  What Do They Need?  Key Benefit Is?  Why Is It Different Than the Competition?

28. Purpose Statement Your Elevator Statement For Business Problems:  What’s the Problem?  Who Does It Affect?  What’s the Impact?  What’s a Successful Solution?

29. Purpose as a Product Box Product Box An Innovation Game by Luke Hohmann  Build Imaginary Packaging for Product  Customers Identify the Problems They Want Solved  Identifies Expected Benefits http://www.jonathanboutelle.com/mt/archives/2005/11/offline_gamelik.html

30. Example: Health Insurance Health Insurance Example: Create a 24x7 resource people could call to get health care questions answered and get direction to sources for care.

31. Example: Health Insurance Intent and Filters Strategic Intent: Best Customer Solution Decision Filter: Does this initiative help to improve health care value for our stakeholders?

32. Example: Health Insurance Purpose Alignment Market Differentiating High Low Mission Critical Low High Healthcare analytics Member focus Claims Processing Enrollment Customer Service Disability Insurance Pharmacy Dental

33. Example: Health Insurance Purpose Statements What’s the Problem? Healthcare industry is difficult to navigate Who Does It Affect? Members What’s the Impact? Confused about appropriate place to receive care, resulting in needless expenses What’s a Successful Solution? Provides members a single, trusted point of contact to get health and wellness and urgent care questions answered

34. Example: Health Insurance Purpose  Provide members a single point of entry to heath insurer’s health and wellness resources.  Answer member’s urgent care questions

35. Example: Health Insurance Costs  Software Development Costs  Vendor Development Costs  Ongoing Operational Costs

36. Example: Health Insurance Benefits  Consolidated Member Point of Contact  Cost Avoidance  Gather Clinical Information

37. Example: Health Insurance Considerations  Vendor Size  Integration with Vendor Systems  Date Available Commitments to Customers  Dependency on Other Project to Supply Data

38. Example: Health Insurance Is Business Value Defined?  Costs >> Benefits  Increased Information About Members  Customer Satisfaction  More Appropriate Care Delivery  Better Informed Members

39. Example  Do We Know What the Right Stuff Is?  Do We Know What to Build First?  Who Decides?

40. So Why Do We Care About Business Value?

41. It’s All About Decisions

42. Value Model?

43. Value Model!

44. What Do We Do?

45. Is Analysis a Lost Art?  Do I Understand the Problem?  Do I Understand the Guidelines For a Solution?  Have I Consistently Described the Solution?  Can I Verify the Solution?

46. Doing the Right Stuff  Tie Project Purpose to Strategy  Factor in Considerations  Utilize Cost/Benefit Information

47. Tie Purpose to Strategy What Is the Project Purpose? Does the Purpose Align with Decision Filters?  Yes – Continue! Stop!  No – Stop!  “What Decision Filters?” – Go Back and Define Some.

48. Factor In Considerations  A Business Driven Deadline?  Impact on Other Projects?  Impacted by Other Projects?  Availability of Key People?  Impact of Regulations?

49. Utilize Cost/Benefit Analysis  Adjust for Considerations  Use Consistent Analysis Between Projects  Understand Uncertainty in Estimates

50. Selecting The “Right Requirements” Right  Look at the Right Level Analysis  Put the Analysis Back In Business Analysis  Do the Right Stuff Just Meets  What Just Meets Purpose?

51. Requirements Levels Why Do This Project? What Do Users Want? What Do We Build? The Software Requirements Memory Jogger by Ellen Gottesdiener This Is the Right Level

52. Minimum Necessary Set  Minimum Features to Create Value  Minimum Features to Replace Existing System  Base on Project Purpose and Considerations

53. When Do We Do It?

54. Prioritizing Features  Determine Relative Value  Priority = Order  Revisions to Order Based on Technical Considerations

55. Relative Value of Feature  Relative Benefit Relative Cost  Benefit Measured in Benefit Points  Cost Measured in Story Points  Resolve Outliers

56. “Value” in the Extreme  Team Discusses Feature  Each Member Indicates Numerical Estimate  Discuss Outliers  Outliers Indicate Assumptions, Considerations

57. Change Feature Order Based on Considerations  Move Up Features That Provide Information  Move Down Features That Depend on Others  Group Features Together That Have Synergy

58. When Do We Decide?

59. Real Options

60. Deciding Is Not a Once in a Lifetime Event  Knowledge Improves  Business Conditions Change  Project Conditions Change  Do You Know Why You Are Deciding Early?

61. Decide Who Should Decide  Who Makes The Decision?  Who Makes Sure It Is Enacted?  Understand Before Making Decisions  Decision Leader  NOT  NOT For Purposes Of Placing Blame

62. “Roles” = Who Decides?  Many Roles for “Business”  Stakeholders  Customers  Product Owners  Users  Need Input From Multiple People  Need To Know Who Ultimately Decides

63. Some Things to Remember  Value Impacted By Purpose And Considerations  Business Value Is All About Decisions  Decide Wisely  Decide Who Should Decide Wisely

64. Questions?

65. References  Stand Back and Deliver, co-author, published by Addison Wesley, due out late 2008 or early 2009  The Software Requirements Memory Jogger, Ellen Gottesdiener  Innovation Games, Luke Hohmann

66. Contact Kent J McDonald:  www.knowledgebridgepartners.com  www.accelinnova.com  515.229.6929  kent@knowledgebridgepartners.com