Product X Release Y: Readiness Gate V1

Product X Release Y:Readiness Gate V1 Josephine Soap Freda Bloggs Hugh Jarse

Agenda Refresh on Delivery Framework Release Plan Trials Plan Development Status Test Status Services & Training Sales & Marketing Recommendation and Decisions Approvals

Overview Role Phase 1 Concept Phase 2 Definition & Planning Phase 3 Development Phase 4 Readiness Phase 5 Release MRD (Market Requirements Document) Sales Training Sales Planning and Account Targeting Business Case Go-To-Market Strategy(inc Channel Strategy) Sales Collateral (Updated) Go-To-Market Plan Sales & Marketing Sales Validation(with customers) Go-To-Market Execution Release Requirements Prescriptive Architecturesand Activity Profiles Updated Roadmap Final Product Description Requirements Baselined Draft Product Description PRD (Product Requirements Document) UpdatedPlatform Defn Product Management Benchmarks Platform Defn Secure Field Trial Customer Performance Reqs Field Trial Plan Design Complete Technology Evaluation Design Specification Functional Specification Re-work Software Unit Test Plan Architecture Analysis Developer Performance Guidelines Product Architecture Document Development Implementation and Unit Test Feature Complete Integration Test Perf designanalysis PerformanceDesign Changes Release Notes Integration Complete Iterative performance adjustments, tuning and testing Documentation Plan Product Documentation Development Update Documentation Documentation Test Execution TC Certification Test Strategy and Planning Test Plan and Test Cycle Design GA Test Tuning & Benchmarking CR Test Preparation Tuning/sizingguidelines Design Documentation Review Maintenance Maintainability Review Iterative performance adjustments, tuning and testing Maintenance Acceptance Criteria Support Operational Impact Statement Support Training Field Trial Support Add S&M Requirements to PRD Supportability Review Install & Deploy + Partner support Alpha Trial Install and Deployment Plan Add Services Requirements Services Training Custom Benchmarking Servicesinc. Training Training Materiel Development Training Execution Training Assessment Product Delivery Team Dissolved Product Delivery Team Leader and Project Mgmt Project Plan Baselined Product Delivery Team Formed Integrated Project Plan Post Release Review Concept Complete (RPG Review) Definition & Planning Complete (RPG Review) Optional Phase Review Development Complete (RPG Review) Readiness Complete (RPG Review) Release Complete (RPG Review) Phase Review TC = Test Complete CR = Controlled Release GA = General Availability Project Task Feature Status Key On the Radar Concept Committed Development Committed Deliverable Optional Optional

Milestone Reviews – what is presented

Readiness 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 atCode Complete stage • Review Services & Training Plan • Review Marketing plan (pricing/packaging,collateral plan) • Review Sales Plan

Delivery Process: Checklist a done will do n Key Role Phase 1 Concept Phase 2 Definition & Planning Phase 3 Development Phase 4 Readiness Phase 5 Release n Will do later or delay MRD (Market Requirements Document) Sales Training Sales Planning and Account Targeting Business Case Go-To-Market Strategy(inc Channel Strategy) Sales Collateral (Updated) Go-To-Market Plan Sales & Marketing Sales Validation(with customers) Go-To-Market Execution u Past due Release Requirements Prescriptive Architecturesand Activity Profiles Updated Roadmap Final Product Description Requirements Baselined Draft Product Description r PRD (Product Requirements Document) Will not do UpdatedPlatform Defn Product Management Benchmarks Platform Defn Secure Field Trial Customer Performance Reqs Field Trial Plan Design Complete Technology Evaluation Design Specification Functional Specification Re-work Software Unit Test Plan Architecture Analysis Developer Performance Guidelines Product Architecture Document Development Implementation and Unit Test Feature Complete Integration Test Perf designanalysis PerformanceDesign Changes Release Notes Integration Complete Iterative performance adjustments, tuning and testing Documentation Plan Product Documentation Development Update Documentation Documentation Test Execution TC Certification Test Strategy and Planning Test Plan and Test Cycle Design GA Test Tuning & Benchmarking CR Test Preparation Tuning/sizingguidelines Design Documentation Review Maintainability Review Maintenance Iterative performance adjustments, tuning and testing Maintenance Acceptance Criteria Support Operational Impact Statement Support Training Field Trial Support Add S&M Requirements to PRD Supportability Review Install & Deploy + Partner support Alpha Trial Install and Deployment Plan Add Services Requirements Services Training Custom Benchmarking Servicesinc. Training Training Materiel Development Training Execution Training Assessment Product Delivery Team Dissolved Product Delivery Team Leader and Project Mgmt Product Delivery Team Formed Project Plan Baselined Integrated Project Plan Post Release Review Concept Complete (RPG Review) Definition & Planning Complete (RPG Review) Optional Phase Review Development Complete (RPG Review) Readiness Complete (RPG Review) Release Complete (RPG Review) Phase Review TC = Test Complete CR = Controlled Release GA = General Availability Project Task Feature Status Key On the Radar Concept Committed Development Committed Deliverable Optional Optional ? a r a a a a a a a u r a n a a a a r a a a a a a a a a a a r r

Inputs and Plans

Porting of fixes Porting of fixes Release Plan Begin Localisation Release Criteria met Release Criteria met 5.0Service Pack 1 Ship Localised release 5.0 CodeComplete Work on bug backlog continues Dev Dev 5.0 5.1 Test (~ 4 weeks) Test 5.0 Patch Release Patch Release Patch Release Patch Release Patch Release Patch Release  Handover to Maintenance Maint Maint Maint Maint Maint Maint Test Test Test Test Test Test Handover to Maint (Maintenance Criteria apply) End Aug 5.0 SP1 April? Alpha End OctLocalised May 18 5.0

Release 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

Field Trial Plan Release dates, resource allocation, milestones, duration etc August5.0 SP1 Release FinalReview May 185.0 Release Weekly reviews 2 weeks 1 month 2 weeks 1 - 2 months Upgrade Planning Evaluation Planning Environment Set-up Evaluation Plan

Target Trial Customers Ruled out

Development 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 Progress

Summary 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

Test Preparation Status

Development 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 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

Training 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

Services • 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.

Pricing 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 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 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 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 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

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 High/High precludes “Go” decision

Approvals

Questions?

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

Feature Status Definitions " 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. "

Feature Creep Roadmap 2008 Feature Status Development Committed Concept Committed Radar

Product X Release Y: Readiness Gate V1