Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Copyright Feature Creep 2008 Product X Release Y: Development Commit V1 Josephine Soap Freda Bloggs Hugh Jarse."— Presentation transcript:

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

2 Copyright Feature Creep 2008 Agenda Refresh on Delivery Framework Business Rationale Technical Strategy Delivery Plan Recommendation and Decisions 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 Delivery Process: Checklist  done will do  Past due  Will not do Key Will do later or delay           

6 Copyright Feature Creep 2008 Agenda Refresh on Delivery Framework Business Rationale Technical Strategy Delivery Plan Recommendation and Decisions Approvals

7 Copyright Feature Creep 2008 Reminder of Concept Commit Scope Summary of CC agreed scope

8 Copyright Feature Creep 2008 Elevator Pitch For who are dissatisfied with, is a that provides. Unlike a, we have assembled. Example - Palm PilotPalm Pilot For travelling executives who are dissatisfied with Franklin Planners, the Palm Pilot is a personal digital assistant that provides rapid access to phone numbers and appointments. Unlike the Sharp Wizard, the Pilot can easily synchronize your data with your PC and fits in your shirt pocket.

9 Copyright Feature Creep 2008 Business Case Latest update on opportunity, forecasts, customer interest

10 Copyright Feature Creep 2008 Agenda Refresh on Delivery Framework Business Rationale Technical Strategy Delivery Plan Recommendation and Decisions Approvals

11 Copyright Feature Creep 2008 Technical Strategy The next few charts should set out the technical strategy, including options still under consideration. It should cover such things as: High level design Choice of components/suppliers/partners Development and test methodology Results of any feasibility studies, prototyping, evaluation & benchmarking Key design decisions and rationale

12 Copyright Feature Creep 2008 Agenda Refresh on Delivery Framework Business Rationale Technical Strategy Delivery Plan Recommendation and Decisions Approvals

13 Copyright Feature Creep 2008 Resourcing Plan The next few charts should describe: Planning Assumptions: Resource availability/contention Resource requirements for delivery: People Skills Hardware Software Other Schedule Plan If multiple delivery options exist e.g. different timing/phasing The charts that follow may offer useful approaches on how best to communicate the Delivery Plan

14 Copyright Feature Creep 2008 Resourcing

15 Copyright Feature Creep 2008 Planning and Resourcing Shortfall Load Test:2 QE:1 S/W:2 Tech Pubs:1 CE:3 (+maternity cover Dec-Mar) EA Jan 31 CR Feb 28 GA Apr 30 Patch releases QE HO4 Dec 10 STIC TestingQE HO3 Nov 30 HO2 Nov 5 HO1 Oct 15 QE DevelopmentSpec/Design Requiredto bring CE back up to full strength and prevent field issues spilling over into mainline and de- railing delivery

16 Copyright Feature Creep 2008 Resource Profile

17 Copyright Feature Creep 2008 Resourcing Feb MarAprMay Jun Jul Assumptions 1.3 month final regression cycle 2.2 incremental heads in Core 3.Very little overflow of work from maintenance 4.Bug backlog reduction ~ 200 issues Delivery Date (2007) Approx 900 man weeks in scope 600 man weeks (Dev) effort available for end Q1 delivery Full delivery not possible until July ’07 or later: Not viable.  A phased approach Earned value

18 Copyright Feature Creep 2008 Delivery Options: 3 Paths Jan 2007 Q May ‘ Jun ‘07 3 Base Planning Assumptions 1) Office 2007 Lab capability required by Jan ’07 2) Smart Client re-factoring can’t delivery before Q3 3) RFEs can be split into Q2 and Q3 deliveries 5.0 Off ’07 SharePoint Client 4.4 Server Apr ‘07

19 Copyright Feature Creep 2008 Delivery Plan: 3 Phasing Options Q May ‘ Jun ‘07 Base Planning Assumptions 1) Smart Client re-factoring can’t delivery before Q3 2) RFEs can be split into Q2 and Q3 deliveries 5.1 Apr ‘07

20 Copyright Feature Creep 2008 Option A – Blah Blah Blah Multi keyword select Licence reporting Not Searching Feature Complete End Jan ‘08 Controlled Release End April ‘08 Generally Available July ‘08

21 Copyright Feature Creep 2008 Option B – Blah Blah Blah Multi keyword select Licence reporting Not Searching Feature Complete End March ‘08 Controlled Release End June ‘08 Generally Available Sept ‘08

22 Copyright Feature Creep 2008 Options OptionCostDelivery Date Year 1 Revenue Year 2 Revenue 3 Year ROI

23 Copyright Feature Creep 2008 Agenda Refresh on Delivery Framework Business Rationale Technical Strategy Delivery Plan Recommendation and Decisions Approvals

24 Copyright Feature Creep 2008 Recommendation Proceed with Option A Cost £xx Feature Complete End Jan ‘09 Controlled Release End April ‘09 Generally Available July ‘09 Begin design with DSP chip included and remove if possible before final build, or in a subsequent version. Readiness on Date Cost to achieve Readiness: £XXX

25 Copyright Feature Creep 2008 Major Risks and Planned Response AreaNature of RiskProbabilityImpactPlanned Response (Owner) TechnicalClock recovery may hit unforeseen technical problems LowMedium Complete design asap Fully resource team (skills and numbers) Schedule/ Resource Inability to hire right skills quickly to enable MPEG encoding work to proceed at optimum speed MedHigh Advertise soon CommercialInability to negotiate customer X to manageable set of features MedHigh Begin discussions soon MarketKorean market throws up new “MUST” features. MediumHigh Stay awake MarketOur doohickey is seen as an incomplete offering LowMedium None MarketTime to market for major features (e.g. Reaction of existing customers to date for availability of 4 port card) HighMedium Test with field Keep them close – involve in design. Sign up to adopt early. High/High precludes “Go” decision

26 Copyright Feature Creep 2008 Agenda Refresh on Delivery Framework Business Rationale Technical Strategy Delivery Plan Recommendation and Decisions Approvals

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

28 Copyright Feature Creep 2008 Questions?

29 Copyright Feature Creep 2008Disclaimer Due to the forward-looking nature of this Roadmap, Feature Creep includes information about products that are in the planning stage of development or that represent custom features or product enhancements. Functionality cited in this document that is not publicly available is discussed within the context of the strategic evolution of the proposed products. This document is for informational purposes only. The information in this document is provisional and is subject to change without notice. Nothing in this document should be considered as a commitment by Feature Creep in relation to future functionality, release dates, product roadmaps or any other matter. Feature Creep MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

30 Copyright Feature Creep 2008 Feature Status Definitions “Radar”“Concept Committed” “Development Committed” The feature has been identified as a potential future feature Deliverables created: – TBD (feature description) The feature has been prioritized by the management team and it has been decided that we will spend additional resources to determine if it is technically feasible and fits within the product strategy – More information required to determine the actual release Probability of the feature going to market – Medium-Low Probability of the feature going to market in the targeted release – Low The feature has completed a business case and most product and market requirements have been defined Deliverables created: – Business Case Or – Drafts of PRD and MRD The management team has approved resources to complete the product and market requirements, functional specifications, development and implementation plan, and perform any technical feasibility studies – The management team has updated the “target release” More information required to determine the actual release Probability of the feature going to market – Medium-High Probability of the feature going to market in the targeted release – Medium The feature has been approved to be developed Deliverables created: – Business Plan – PRD and MRD – Development and Implementation Plans – Functional Specification A management team has approved resources to complete the development of the feature – The management team has placed the feature in a “locked” release We are spending resource to ensure the feature is included in the “locked” release Probability of the feature going to market – High Probability of the feature going to market in the “locked” release – High " Due to the forward-looking nature of this Roadmap, Feature Creep includes information about products that are in the planning stage of development or that represent custom features or product enhancements. Functionality cited in this document that is not publicly available is discussed within the context of the strategic evolution of the proposed products. This document is for informational purposes only. The information in this document is provisional and is subject to change without notice. Nothing in this document should be considered as a commitment by Feature Creep in relation to future functionality, release dates, product roadmaps or any other matter. Feature Creep MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. "

31 Copyright Feature Creep 2008 TimelineJuly 2008Q4 2008Q Release GerbilHamsterShrew Theme Replication & Distribution Smart clients Physical Records Management Management Office 12 support Advanced Physical Records Management Manage-in-place APIs Core Features  Feature 1 Feature 2 Feature 3 Feature 4 Feature 5  Feature 1  Feature 2  Feature 3  Feature 4 Feature 1 Feature 2 Feature 3 Optional Features Feature 1 Feature 2 Feature 3 Feature 4 Feature 5  Feature 1  Feature 2  Feature 3  Feature 4  Feature 5 Feature 1 Feature 2 Feature 3 Platforms OS/DB Windows 2000, XP Office 2003.Net 1.1 Windows 2000, XP Office 2003.Net 1.1 Windows 2000, XP Office 2007.Net 2.0 Radar Concept Committed Development CommittedFeature Status Feature Creep Roadmap 2008


Download ppt "Copyright Feature Creep 2008 Product X Release Y: Development Commit V1 Josephine Soap Freda Bloggs Hugh Jarse."

Similar presentations


Ads by Google