1. Copyright Feature Creep 2008 Product X Release Y: Release Gate V1 Josephine Soap Freda Bloggs Hugh Jarse

2. Copyright Feature Creep 2008 Agenda Refresh on Feature Creep Delivery Framework Product Management status Product Quality Marketing Status Support & Maintenance Status Services Status Sales Status Recommendation Approvals

3. Copyright Feature Creep 2008Overview

4. Milestone Reviews – what is presented Phase 1: Concept Phase 2: Definition and Planning Phase 3: Development Phase 4: Readiness Phase 5: Release Product Concept Fit with strategy and roadmap Marketing Requirements Target market and size Value proposition to customer Product Requirements Business case Project schedule Resources required Project costs Gap between product requirements and actual product Updated business case Updated project schedule and costs Test results Field trial feedback Launch plan Updated business case Updated project schedule and costs Initial bookings and revenue Review of development effort Retirement plan

5. Copyright Feature Creep 2008 Release Review Objectives Verify that:  Product is at sufficient level of quality for trial customers  Software release media/mechanisms are prepared  Trial customers have been secured and plans in place  Pricing/packaging defined and communicated  Marketing/Sales materials are in place  Customer/Partner engagement plan is in place  Support organisation is ready  Services organisation is ready  Sales organisation is ready

6. Copyright Feature Creep 2008 Delivery Process: Checklist  done will do  Past due  Will not do Key Will do later or delay              

7. Copyright Feature Creep 2008 Agenda Refresh on Feature Creep Delivery Framework Product Management status Product Quality Marketing Status Support & Maintenance Status Services Status Sales Status Recommendation Approvals

8. Copyright Feature Creep 2008 Product Management Status Summary of release content Gaps or variance from Development Committed plan Issues, risks, opportunities

9. Copyright Feature Creep 2008 Trial Customers CustomerRegionFocusStart DateProbability Customer ANAMVoice input5/6/2008100% Customer BEMEAIntegration with SharePoint7/6/2008100% Customer CEMEAClean Energy from ear wax13/7/200860% Customer DAPACFaster than light traveltbd100%

10. Copyright Feature Creep 2008 Trial Plans – Customer A Business Problem: what will they do with the release? Environment: where/how will it be deployed? Trial size : how many users or systems? Users:what kind of users? Future: If successful, what deployment will follow the trial? Issues: What concerns, limitations, knowledge or resource gaps threaten a successful trial? Resource Plan:What resources are required and are they in place?

11. Copyright Feature Creep 2008 Agenda Refresh on Feature Creep Delivery Framework Product Management status Product Quality Marketing Status Support & Maintenance Status Services Status Sales Status Recommendation Approvals

12. Copyright Feature Creep 2008 Product Quality Summary e.g. duration of testing, number of test cases added, executed, new things tried, lessons, observations etc

13. Copyright Feature Creep 2008 Severity Definitions Severity A (Issue Priority = 1 Critical)  A problem which will prevent the accomplishment of an essential capability and NO known work-around:  Show-stopper, production down  Critical functionality does not work  Data loss  Causes irreversible (or reversible but with a lot of effort) database damage  Repeated, service-affecting core dumps  Security violations  Unbounded memory growth  Severe degradation (> 50%) in throughput performance below that specified in the PRD Severity B (Issue Priority = 2 High)  A problem will adversely affect the accomplishment of an operational capability and HAS known work-around:  Critical functionality of the product does not work but known work-around solution is available  Non-Critical functional issue that a customer is LIKELY to come across but known work- around solution is available Severity C (Issue Priority = 3 Medium)  A problem will result in user/operator inconvenience or annoyance, but does not affect a required operational or mission-essential capability:  Customer is NOT likely to come across this with known work-around  Non-Critical functionality issue with known work-around Severity D (Issue Priority = 4 Low)  Very minor problem resulting in negligible inconvenience or annoyance

14. Copyright Feature Creep 2008 Exit Criteria set at Development Commit 100% new feature test case coverage and pass rate 100% regression test case coverage Zero severity A’s and B’s across entire product 90% of severity C defects raised against new features are closed 80% of severity D defects raised against new features are closed No incidents in a status of Further Evidence Required No incidents in a status of Awaiting Test Evidence that defect cumulative count is levelling off

15. Copyright Feature Creep 2008 Test Case Coverage 100% new feature test case coverage and pass rate 100% regression test case coverage

16. Copyright Feature Creep 2008 Test Case Coverage 100% new feature test case coverage and pass rate 100% regression test case coverage

17. Copyright Feature Creep 2008 Incidents Zero severity A’s and B’s across entire product SeverityOpen Defects A0 B2

18. Copyright Feature Creep 2008 Incidents IncidentDescriptionSeverityJustification 93866Office – when saving a new version clicking cancel on version comment dialog loses all changes to document. B – infrequent loss or corruption of user- added data. Defect pre-exists X.Y Limitation of Vista. 94237Lookups – large number of lookups causes client API and memory errors. B – frequent failure of important component of the system, no acceptable workaround. Defect pre-exists X.Y Significant change to product, deemed too risky. Uncommon scenario. Zero severity A’s and B’s across entire product

19. Copyright Feature Creep 2008 Incidents Zero severity A’s and B’s across entire product SeverityOpen Defects A0 B8

20. Copyright Feature Creep 2008 Incidents 90% of severity C defects raised against new features are closed 80% of severity D defects raised against new features are closed SeverityNew Feature Open Defects Expected Fix Count Actual Fix Count % Achieved C96787082585 D77261054370 All Priority 1, 2 and 3 defects (as assigned by the Defect Council) have been cleared Greater number of pre-existing incidents closed than expected

21. Copyright Feature Creep 2008 Incidents FER or RAT No incidents in a status of Further Evidence Required No incidents in a status of Awaiting Test

22. Copyright Feature Creep 2008 Defect Cumulative Count Evidence that defect cumulative count is levelling off

23. Copyright Feature Creep 2008 Other Areas Installations, Upgrades and Backward Compatibility. Successful execution of Test Cycle on a New Installation. Successful execution of Upgrade Testing for a defined set of supported releases. Successful execution of Backward Compatibility Testing for a defined set of supported releases. Product Performance Successful execution of Performance Type Testing. No Degradation in performance that can not be attributed to the introduction of new functionality. Stress Testing.

24. Copyright Feature Creep 2008 Areas of Concern Identify any areas where quality is suspect and/or further testing is required

25. Copyright Feature Creep 2008 Summary General Statement – Test Manager The X.Y Test Cycle has been completed and the product is deemed fit for release to customers. The X.Y Test Cycle has achieved a higher level of testing than has been attained in previous releases, and by consequence is assumed to be of higher quality. All defects which have been Suspended or De-scoped from the release have been with the agreement of the defect council members and are deemed lower risk.

26. Copyright Feature Creep 2008 Agenda Refresh on Feature Creep Delivery Framework Product Management status Product Quality Marketing Status Support & Maintenance Status Services Status Sales Status Recommendation Approvals

27. Copyright Feature Creep 2008 Marketing Status  Update on pricing/packaging changes  Inventory of materiels and availability  Update on sales collateral  Sales, customer and partner engagement/training plans  Anything else relevant e.g. Web site updates, press releases etc

28. Copyright Feature Creep 2008 Agenda Refresh on Feature Creep Delivery Framework Product Management status Product Quality Marketing Status Support & Maintenance Status Services Status Sales Status Recommendation Approvals

29. Copyright Feature Creep 2008 Support & Maintenance Status  Release mechanisms e.g. CDs, download etc?  Readiness of support teams?  Readiness of Maintenance teams?  Timing of first service pack?

30. Copyright Feature Creep 2008 Agenda Refresh on Feature Creep Delivery Framework Product Management status Product Quality Marketing Status Support & Maintenance Status Services Status Sales Status Recommendation Approvals

31. Copyright Feature Creep 2008 Services Status  Readiness of Professional Services?  Readiness of training team (inc Training materiels)?

32. Copyright Feature Creep 2008 Agenda Refresh on Feature Creep Delivery Framework Product Management status Product Quality Marketing Status Support & Maintenance Status Services Status Sales Status Recommendation Approvals

33. Copyright Feature Creep 2008 Sales Status  Update from each region on X.Y sales forecasts – what opportunities, dependencies etc. exist

34. Copyright Feature Creep 2008 Agenda Refresh on MDF Product Management status Product Quality Marketing Status Support & Maintenance Status Services Status Sales Status Recommendation Approvals

35. Copyright Feature Creep 2008 Recommendation Make release as planned Allocate X resources to support trial at Customer B Release on Date Cost to achieve Release: £XXX

36. Copyright Feature Creep 2008 Major Risks and Planned Response AreaNature of RiskProbabilityImpactPlanned Response (Owner) TechnicalInstall process is lengthy and complex on Vista LowMedium Assign additional resources to Vista trials Schedule/ Resource 4 customer trials in parallel is demanding and may overwhelm support and product management Med Prepare 2 of Services team to provide additional support CommercialCustomer Y expected feature Z to be free but we’re treating as upsell HighMed Be prepared to discount, or trade additional licenses to keep them happy. High/High precludes “Go” decision

37. Copyright Feature Creep 2008 Agenda Refresh on Feature Creep Delivery Framework Product Management status Product Quality Marketing Status Support & Maintenance Status Services Status Sales Status Recommendation Approvals

38. Copyright Feature Creep 2008 Approvals DeptApproval: Go/No Go EMEA NAM CALA APAC CEO CTO Finance Marketing Support Maintenance & Test Research Development Product Management

39. Copyright Feature Creep 2008 Questions?