copyright feature creep 2008 product x release y: readiness gate v1 josephine soap freda bloggs hugh...

Copyright Feature Creep 2008Copyright Feature Creep 2008

Product X Release Y:Product X Release Y:Readiness Gate V1Readiness Gate V1

Josephine SoapFreda BloggsHugh Jarse

Copyright Feature Creep 2008

Agenda

Refresh on Delivery Framework

Release Plan

Trials Plan

Development Status

Test Status

Services & Training

Sales & Marketing

Recommendation and Decisions

Approvals


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


Platform Defn

UpdatedPlatform Defn


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


Readiness Gate ObjectivesReadiness Gate Objectives Ensure entire business is aligned around release and will be ready to

fully exploit the opportunity to market, sell, deploy, and support

• Did each function deliver those things specified in the Development phase on time and to quality?

• Does each function have a plan and resource to deliver those things specified in the Readiness phase on time and to quality?

• Where a function is dependent on something from someone else, is there a commitment to deliver it?

• Are there any significant known risks for which we need mitigation?• Are we all in synch on dates and approach?• Review Release Plan• Review status of product development and test at Code Complete

stage• Review Services & Training Plan• Review Marketing plan (pricing/packaging,collateral plan)• Review Sales Plan


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



Platform Defn

UpdatedPlatform Defn

Delivery Process: Checklist done will do Past due Will not doKey Will do later or delay

?


Inputs and PlansInputs and PlansReadiness Gate Inputs

Type Item Owner Draft Reviewed Approved

Field Trial Customers/Plan Paul Moorhead Under Way N N

Test Plan and Test Cycle Design Jim Jones Complete Y Y

Sales Planning & Account Targeting ? Not started N N

Product Documentation Gary Smith Under Way N N

Code Feature Complete Gary Smith Under Way N N

Release Criteria Joanne Thud Under Way N N

Draft Product Description Nuala Lilly Under Way N NReadiness Phase Tasks and Deliverables

Type Item Owner Draft Reviewed Approved

Pricing/Packaging John Ball Under Way Y N

Sales Collateral Olivia Branden Under Way N N

Sales Planning/Account Targeting Hugh Jarse Not started N N

Sales Training Hugh Jarse Not started N N

Product Documentation update Gary Smith Under Way N N

Product Description Simon Oil Under Way N N

Maintenance & Support Training Ian Wind Under Way N N

Services Training Tom Sane Under Way N N

Training Materiel Development Tom Sane Under Way N N

Release Notes Gary Smith Not started N N


Agenda


Release Plan

Trials Plan

Development Status

Test Status

Services & Training

Sales & Marketing


Approvals


Release PlanRelease Plan

Handover to Maintenance

DevDev

Test

5.0

Maint

Test Test Test

Patch Release

Patch Release

Patch Release

CodeComplete

5.0

Porting of fixes

Maint Maint

5.0Service Pack 1

Maint

Test Test Test

Patch Release

Patch Release

Patch Release

Maint Maint

Test (~ 4 weeks) 5.15.0

Porting of fixes

Work on bug backlog continues

Handover to Maint (Maintenance Criteria apply)

Release Criteria met

Release Criteria met

Begin Localisation

Ship Localised release

May 185.0

End Aug5.0 SP1

End OctLocalised

April?Alpha


Release MechanismsRelease Mechanisms

Description of release process, especially any changes from previous process e.g.:

•For 5.0 and thereafter we move to a software distribution model based on electronic downloads, with CDs shipped only as a customer/Partner requested exceptional approach. Customers and SI Partners will be informed of releases by email and we will be able to track their downloads via their unique log-in IDs when accessing the download system.• CR release – email announcement will be made only to Customers A and B• GA release – email announcement to all customers on current support contracts

Bill Culbertson

I thought we were doing away with the term Controlled Release because so few custiomer were taking it anyhow.


Agenda


Release Plan

Trials Plan

Development Status

Test Status

Services & Training

Sales & Marketing


Approvals


Field Trial PlanField Trial Plan

PlanningPlanning Environment Set-upEnvironment Set-up

Evaluation PlanEvaluation Plan

EvaluationEvaluation

May 185.0 Release

1 month2 weeks 1 - 2 months

Weekly reviews

August5.0 SP1 Release

FinalReview

Upgrade PlanningUpgrade Planning

2 weeks

Release dates, resource allocation, milestones, duration etc


Target Trial CustomersTarget Trial CustomersCustomer Target Area Status

Toyota Gear knobs Approached – no commitment as yet

BMW Warehousing Committed – trial to start Sept 5.

Renault Car mats Considering proposal – need support from Tony and confirmation of level of support

Lotus Steering Wheels Tentative discussions – no commitment as yet.

Customer Reason

Ford Not upgrading until year end at earliest

Mazda 4.4 deployment too problematic to propose upgrade

Honda Not approached re 5.0 trial as yet.

Ruled out


Agenda


Release Plan

Trials Plan

Development Status

Test Status

Services & Training

Sales & Marketing


Approvals


Development StatusDevelopment Status Code Complete target date for new enhancements was

16th February This was met in most areas, exceptions are:

2 man weeks on SharePoint 2007 integration 2 man weeks on new sideburn attachment 3-4 man weeks on Installers

Total effort on enhancements, excluding bug fixing during Testing phase, is 373 man weeks

1 week of integration testing followed by 12 weeks of system testing (we are now in week 1)

On target for release on 18th May


Development ProgressDevelopment Progress


Summary of MilestonesSummary of Milestones 16th February – target date for Code Complete on

enhancements 27th February – start of System Testing 16th March – first product documentation available for

internal review 5th April – all product documentation available for

internal review 11th May – all product documentation definitive 18th May – release


Agenda


Release Plan

Trials Plan

Development Status

Test Status

Services & Training

Sales & Marketing


Approvals


Test Preparation StatusTest Preparation Status

Milestone

Status

Specifications Reviews Complete Master Test Plan and Strategy Definitive Test Environment Readiness Complete Test Schedule Complete New Feature Test Cases Complete Regression Pack Identification Complete


Development Hand-offDevelopment Hand-off 5.0 Feature Specifications Definitive Feature Complete Feb 16th 2007 Incomplete

2 of 18 enhancements did not meet feature complete deadline RFE 18 Chalk to cheese converter RFE 78 Oil and water mixer

Additional Gap Areas of Significance Installers (Manual Workarounds available) New icons in desktop client still not available

Unit and Integration Test Period by Development to be ongoing until Integration testing has been achieved for all features.


Test StatusTest Status Test Execution commenced Feb 19th 2007. 12 week Test Cycle planned 5.0 New Feature Test Case

2691 New Feature Test Cases generated 2/3 required to be executed across a range of Client side platforms, namely Office 03,

07 with XP and Vista.

Planned Test Case Coverage 12 week cycle should result in execution of 9000 test cases

(New Feature and Regression). Can only be achieved through

delivery of revised Dev to Test Handover Materialisation of higher quality features to test


Agenda


Release Plan

Trials Plan

Development Status

Test Status

Services & Training

Sales & Marketing


Approvals


Training MaterialTraining Material Assessment / read-up of new features

Assessment to be completed for how they will effect SA and RM course only target for completion : 31st March.

Preparation of slideware Slideware to be produced for SA and RM course only in first instance Initial pass complete : 28th April

Preparation of training environment to allow exercises to begin Will be on Beta software, depends on beta release from test / dev. Expected from mid April.

Will liaise with Test Preparation of exercises

Depends on alpha training environment availability – target end April/early May Preparation of final training environment

Only possible once final delivery of 5.0 release Date of completion :+ 2 weeks after 5.0

Verification of training deliverables i.e. make sure that the exercises / slideware produced using beta versions matches the actual

versions Date of completion – delivery + 2 weeks

We are expecting some rework, given past experience


ServicesServices European team to be training guinea pigs, July 5 Product Management briefing webinar on July 9 2 of maintenance team on loan to Services to cover initial customer

upgrade surge Etc.

Microsoft Word Document


Agenda


Release Plan

Trials Plan

Development Status

Test Status

Services & Training

Sales & Marketing


Approvals


Pricing and PackagingPricing and Packaging Now available in silver with certificate of

authenticity Price book updated and reviewed with sales New discounting structure – Sales can

discount up to 50% during last week of quarter provided they agree to drive Fiat Pandas


Printed CollateralPrinted Collateral 5.0 Release Summary – draft Mon 12th March Updated “Feature Creep solves all known problems”

Whitepaper – to be updated by 12th March New Product Fact Sheet (representing our new product and

positioning) – draft 26th Match New Technical Fact Sheet (with new architecture diagrams) Product Announcement – 1 week before Product ships Other current collateral will be revised as a result of the 5.0

Release, however the pieces listed above are essential to have for the release of the product


Sales ToolsSales Tools New Product Presentation – draft 2nd March Updated Corporate Presentation – draft 12th

March Updated Technical Presentation – draft 2nd April Updated Battlecard – 16th April Others: New Product Demo, Updated Screen

Demo


Website UpdatesWebsite Updates Homepage 4.4 webpage Products section

Product homepage Product Key Benefits page Organizational Value page

Services Section Training course overviews

Support Section Lifecycle Policy page Retirement Policy page

Website updates will be completed by the Product Release date.


Customer CommunicationsCustomer Communications

Product Announcement – sent to Feature Creep News subscribers

Field to arrange and send invites for Customer and Partner Live Meetings

Release Notice email – pushed out to Salesforce.com contacts


Agenda


Release Plan

Trials Plan

Development Status

Test Status

Services & Training

Sales & Marketing


Approvals


Recommendation• Proceed with Readiness Phase

•Cost £xx

•Controlled Release End April ‘09

•Generally Available July ‘09

• Ensure trial customers signed up by 15th May – needs Exec assistance

• Cost to achieve Release: £XXX


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


Agenda


Release Plan

Trials Plan

Development Status

Test Status

Services & Training

Sales & Marketing


Approvals


ApprovalsDept Approval: Go/No Go

EMEA

NAM

CALA

APAC

CEO

CTO

Finance

Marketing

Support Maintenance & Test

Research

Development

Product Management


Questions?


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.


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. "


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



Radar Concept Committed Development CommittedFeature Status

Feature Creep Roadmap 2008Feature Creep Roadmap 2008

copyright feature creep 2008 product x release y: readiness gate v1 josephine soap freda bloggs hugh...

Documents

release plan handover

copyright feature creep

release product concept

weeks release dates

product x release y

development phase

overview slide

alpha slide