copyright feature creep 2008 product x release y: development commit v1 josephine soap freda bloggs...
TRANSCRIPT
Copyright Feature Creep 2008Copyright Feature Creep 2008
Product X Release Y:Product X Release Y:Development Commit V1Development Commit V1
Josephine SoapFreda BloggsHugh Jarse
Copyright Feature Creep 2008
Agenda
Refresh on Delivery Framework
Business Rationale
Technical Strategy
Delivery Plan
Recommendation and Decisions
Approvals
Copyright Feature Creep 2008
OverviewOverviewPhase 1Concept
Product Delivery Team Formed Post Release
Review
Release Requirements
Integration Test
Phase 2Definition & Planning
Phase 3Development
Phase 4Readiness
Phase 5Release
Integration Complete
DesignComplete
Development
Test
Maintenance
Integrated Project Plan
Secure Field Trial Customer
Product Architecture Document Implementation and Unit Test
ArchitectureAnalysis
Optional Phase Review
Draft Product DescriptionProduct
Management
Project Plan Baselined
Test Plan and Test Cycle Design
Field Trial Plan
Test Strategy and Planning
Final Product Description
Product Delivery Team Leader and Project Mgmt
Design Specification
DevelopmentCommitted
Concept Committed
On the Radar
Documentation
Concept Complete(RPG Review)
Definition & PlanningComplete(RPG Review)
DevelopmentComplete(RPG Review)
ReadinessComplete(RPG Review)
Re-work Software
Update Documentation
Feature Complete
Add S&M Requirements to PRD
Field Trial
Requirements Baselined
Product Documentation Development
Training Assessment Training ExecutionTraining Materiel Development
Test Execution
Phase Review
Feature Status
Functional Specification
Install and Deployment Plan
Supportability Review
ReleaseComplete(RPG Review)
TC
Product Delivery Team Dissolved
GACR
TechnologyEvaluation
Documentation Plan
Design Documentation Review
Maintenance Acceptance Criteria
Project Task
Deliverable
Optional Optional
TC = Test CompleteCR = Controlled ReleaseGA = General AvailabilityKey
Servicesinc. Training
Install & Deploy + Partner support
Maintainability Review
PRD (Product RequirementsDocument)
Role
Support Operational Impact Statement
Support
Unit Test Plan
Updated Roadmap
Release Notes
Support Training
Alpha TrialServices Training
Certification
Test Preparation
Sales &Marketing
Business Case
Sales Validation(with customers)
Go-To-MarketStrategy(inc Channel Strategy)
(Updated) Go-To-Market Plan
Go-To-Market Execution
Sales Planning and Account TargetingMRD (Market Requirements Document) Sales Collateral
Sales Training
Add Services Requirements
Performance Reqs
Benchmarks
Prescriptive Architecturesand Activity Profiles
Developer Performance Guidelines
PerformanceDesign Changes
Perf designanalysis
Tuning & Benchmarking
Tuning/sizingguidelines
Custom Benchmarking
Iterative performance adjustments, tuning and testing
Iterative performance adjustments, tuning and testing
Platform Defn
UpdatedPlatform Defn
Copyright Feature Creep 2008
Milestone Reviews – what is presentedMilestone 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
Copyright Feature Creep 2008
Phase 1Concept
Product Delivery Team Formed
Post ReleaseReview
Release Requirements
Integration Test
Phase 2Definition & Planning
Phase 3Development
Phase 4Readiness
Phase 5Release
Integration Complete
DesignComplete
Development
Test
Maintenance
Integrated Project Plan
Secure Field Trial Customer
Product Architecture Document Implementation and Unit Test
ArchitectureAnalysis
Optional Phase Review
Draft Product DescriptionProduct
Management
Project Plan Baselined
Test Plan and Test Cycle Design
Field Trial Plan
Test Strategy and Planning
Final Product Description
Product Delivery Team Leader and Project Mgmt
Design Specification
DevelopmentCommitted
Concept Committed
On the Radar
Documentation
Concept Complete(RPG Review)
Definition & PlanningComplete(RPG Review)
DevelopmentComplete(RPG Review)
ReadinessComplete(RPG Review)
Re-work Software
Update Documentation
Feature Complete
Add S&M Requirements to PRD
Field Trial
Requirements Baselined
Product Documentation Development
Training Assessment Training ExecutionTraining Materiel Development
Test Execution
Phase Review
Feature Status
Functional Specification
Install and Deployment Plan
Supportability Review
ReleaseComplete(RPG Review)
TC
Product Delivery Team Dissolved
GACR
TechnologyEvaluation
Documentation Plan
Design Documentation Review
Maintenance Acceptance Criteria
Project Task
Deliverable
Optional Optional
TC = Test CompleteCR = Controlled ReleaseGA = General Availability
Key
Servicesinc. Training
Install & Deploy + Partner support
Maintainability Review
PRD (Product RequirementsDocument)
Role
Support Operational Impact Statement
Support
Unit Test Plan
Updated Roadmap
Release Notes
Support Training
Alpha TrialServices Training
Certification
Test Preparation
Sales &Marketing
Business Case
Sales Validation(with customers)
Go-To-MarketStrategy(inc Channel Strategy)
(Updated) Go-To-Market Plan
Go-To-Market Execution
Sales Planning and Account TargetingMRD (Market Requirements Document) Sales Collateral
Sales Training
Add Services Requirements
Performance Reqs
Benchmarks
Prescriptive Architecturesand Activity Profiles
Developer Performance Guidelines
PerformanceDesign Changes
Perf designanalysis
Tuning & BenchmarkingTuning/sizingguidelines
Custom Benchmarking
Iterative performance adjustments, tuning and testing
Iterative performance adjustments, tuning and testing
Platform Defn
UpdatedPlatform Defn
Delivery Process: Checklist done will do Past due Will not doKey Will do later or delay
Copyright Feature Creep 2008
Agenda
Refresh on Delivery Framework
Business Rationale
Technical Strategy
Delivery Plan
Recommendation and Decisions
Approvals
Copyright Feature Creep 2008
Elevator PitchElevator Pitch
For <target customers> who are dissatisfied with <current alternative>,<our product> is a <new product category> that provides <key problem solving opportunity>. Unlike a <competitive substitute>, we have assembled <key whole product features>.
Example - Palm 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.
Copyright Feature Creep 2008
Business CaseBusiness Case Latest update on opportunity, forecasts,
customer interest
Copyright Feature Creep 2008
Agenda
Refresh on Delivery Framework
Business Rationale
Technical Strategy
Delivery Plan
Recommendation and Decisions
Approvals
Copyright Feature Creep 2008
Technical StrategyTechnical 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
Copyright Feature Creep 2008
Agenda
Refresh on Delivery Framework
Business Rationale
Technical Strategy
Delivery Plan
Recommendation and Decisions
Approvals
Copyright Feature Creep 2008
Resourcing PlanResourcing PlanThe next few charts should describe:• Planning Assumptions:• Resource availability/contention• Resource requirements for delivery:
•People•Skills•Hardware•Software•Other
• Schedule PlanIf 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
Copyright Feature Creep 2008
Resourcing
Delivery Resourcing
Sprint
MBI/LATIMS MPG
CE Nextel i930 SupportCE AIX Release
CE Telus IP Auth
Other CE
M3T
Provisioning
ESF MAG 6.4+
0
20
40
60
80
100
120
140
160
180
Oct Nov Dec Jan Feb Mar Apr May
Peo
ple
MAG 6.4+ESFProvisioningM3TOther CECE China UnicomCE Telus IP AuthCE AIX ReleaseCE Nextel i930 SupportCE Cingular GD+MPGIMSMBI/LATEMS for TMOD2 DASprint
+10
Copyright Feature Creep 2008
Sprint Resource Plan
Tech Pubs
EMS SW
MAG SW
MAG QE
Test Automation
PMArchitects
EMS QE
MAG Load Test
0
20
40
60
80
100
120
Oct Nov Dec Jan Feb Mar Apr May
He
ad
s
Planning and ResourcingShortfall
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 Testing
QE
HO3 Nov 30
HO2 Nov 5
HO1 Oct 15
QEQE
Development
Spec/Design
Requiredto bring CE back up to full strength and
prevent field issues spilling over into mainline and de-railing delivery
Copyright Feature Creep 2008
Resource ProfileSoftware Development Resource Profile
19.00
20.00
21.00
22.00
23.00
24.00
25.00
26.00
Jul-06 Aug-06 Sep-06 Oct-06 Nov-06 Dec-06 Jan-07 Feb-07 Mar-07 Apr-07 May-07 Jun-07
Month
Hea
ds
75.00
80.00
85.00
90.00
95.00
100.00
105.00
Man
Wee
ks p
er M
on
th
Copyright Feature Creep 2008
Feature content
Smart Client Re-factor Phase 1
RFEs (~50)
Centera Integration
Office 2007
eMail Phase 1
PRM basic
L10NBug backlog
0
100
200
300
400
500
600
700
800
900
1000
1
Eff
ort
(m
an
wee
ks)
Bug backlog
L10N
PRM basic
eMail Phase 1
Office 2007
Centera Integration
RFEs (~50)
Smart Client Re-factor Phase 1
Resourcing
Feb Mar Apr May Jun Jul
Assumptions1. 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
Earned value
Copyright Feature Creep 2008
Delivery Options: 3 PathsDelivery Options: 3 PathsJan 2007
Q3 2007
5.2
1
2
5.1 May ‘072
3
5.1 Jun ‘073
Base Planning Assumptions1) Office 2007 Lab capability required by Jan ’072) Smart Client re-factoring can’t delivery before Q33) RFEs can be split into Q2 and Q3 deliveries
5.0Off ’07 SharePoint Client4.4 Server
1
5.1 Apr ‘07
Copyright Feature Creep 2008
Delivery Plan: 3 Phasing OptionsQ3 2007
5.2
1
25.1 May ‘07
35.1 Jun ‘07
Base Planning Assumptions1) Smart Client re-factoring can’t delivery before Q32) RFEs can be split into Q2 and Q3 deliveries
5.1 Apr ‘07
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
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
Copyright Feature Creep 2008
Options
Option Cost Delivery Date
Year 1 Revenue
Year 2 Revenue
Year 2 Revenue
3 Year ROI
Copyright Feature Creep 2008
Agenda
Refresh on Delivery Framework
Business Rationale
Technical Strategy
Delivery Plan
Recommendation and Decisions
Approvals
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
Copyright Feature Creep 2008
Major Risks and Planned Response
Area Nature of Risk Probability Impact Planned Response (Owner)
Technical Clock recovery may hit unforeseen technical problems
Low Medium Complete design asapFully resource team (skills and numbers)
Schedule/ Resource
Inability to hire right skills quickly to enable MPEG encoding work to proceed at optimum speed
Med High Advertise soon
Commercial Inability to negotiate customer X to manageable set of features
Med High Begin discussions soon
Market Korean market throws up new “MUST” features.
Medium High Stay awake
Market Our doohickey is seen as an incomplete offering
Low Medium None
Market Time to market for major features (e.g. Reaction of existing customers to date for availability of 4 port card)
High Medium Test with fieldKeep them close – involve in design.Sign up to adopt early.
High/High precludes “Go” decision
Copyright Feature Creep 2008
Agenda
Refresh on Delivery Framework
Business Rationale
Technical Strategy
Delivery Plan
Recommendation and Decisions
Approvals
Copyright Feature Creep 2008
ApprovalsDept Approval: Go/No Go
EMEA
NAM
CALA
APAC
CEO
CTO
Finance
Marketing
Support Maintenance & Test
Research
Development
Product Management
Copyright Feature Creep 2008
DisclaimerDisclaimerDue 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.
Copyright Feature Creep 2008
Feature Status DefinitionsFeature 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. "
Copyright Feature Creep 2008
Timeline July 2008 Q4 2008 Q2 2009
Release Gerbil Hamster ShrewTheme • Replication & Distribution
• Smart clients• Physical Records Management• eMail 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
OptionalFeatures
• 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
PlatformsOS/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 2008Feature Creep Roadmap 2008