product delivery plan - paul cunninghampaulvcunningham.info/assets/work_samples/productdel… ·...

Product Delivery PlanCenterwise v1.5

Table of Contents1. Hot Topics..............................................................................................32. Schedule Risks.......................................................................................33. Events....................................................................................................44. Product Name.........................................................................................45. Product Overview...................................................................................56. Release Schedule...................................................................................67. Product Feature Issues...........................................................................88. Benchmarks...........................................................................................99. 3rd party compatibility.........................................................................1010. Year 2000 Readiness............................................................................1112. Packaging (BOM)..................................................................................1313. Production/Manufacturing/Inventory....................................................1514. Documentation.....................................................................................1615. Localization..........................................................................................1716. Artwork.................................................................................................1817. License Agreement...............................................................................1918. License Management and License Keys...............................................2019. SKU #s, UPC, Pricing............................................................................2120. Service & Support Issues......................................................................2221. QA Issues..............................................................................................2422. Tech Support Issues.............................................................................2523. Training................................................................................................2524. Third-party and logo certifications.......................................................2625. Royalties, Third-party Software and Redistributables..........................2726. Patents, Trademarks, Copyrights.........................................................2827. Beta Programs......................................................................................2928. Product Release Notice (PRN)..............................................................3229. Marketing Launch.................................................................................33

Centricity Company Confidential June 6, 2000 of 37

Product Delivery PlanThe purpose of this document is to document the decisions and actions required to release this product.

Related DocumentsRelease 1 Marketing Requirements DocumentRelease 1 Functional SpecificationsRelease 1 Product Requirement Addendum Draft (added 2/14/00)Websock Functional Design Specifications Draft (added 2/14/00)

PDP Document Owner:Rick Combest, PMgmt

Distribution List:Paul Cunningham, PMgmtSuketu Pandya, EngrJosh Gray, EngrBBM (B. Bharathi Mohan), EngrRamesh Krishnan, EngrMichael Newton, EngrJim Clemmons, QA

Scott Vaughan, MktgLaura Aspenwall, DocsDarryl Joannides, OpsDavid Hults, Customer Services

Cc:Lynn Nye, PresDavid Ries, EngrRob Ryan, QAJason Henneman, QALisa Kinnaman, Mktg


1. Hot Topics

Review of scheduleGold date now 13 JULY.

Status of current build (16)

Review spec features v. Build 16

2. Schedule Risks

Top items that may impact our product delivery date.

Item/EventImpact(Hi/Med/Low)

Likelihood(Hi/Med/Low)

Action Contingency

Scalability Testing Med Med

[Josh/Jim] to set schedule w/Bob Brown/MPSC

65Agents now running in QA

We have topped out at 65 and no plans in place to test further.

QA plans to have 104 before the release

1. Fix2. Limit # of users3. Change CP hierarchy

model

Benchmark Testing Hi Med Create plan[Jim]

1. Fix2. Accept

Compatibility List Hi Med 1. Identify additional resources

Artwork for product Med Low

Quality Gold Candidate

Hi Med Monitor and prioritize bugs

Review defects (complete 7/11)


3. Events

4. Product Name

“Code Name: EurekaVersion number: 1.10

Resolved:The objective is to implement the new name/s prior to RC1 (external beta.)

Marketing has chosen the name Centerwise. This name has a number of advantages, it ‘resonates’ with ‘Centricity’ and implies intelligence. It also has the ability to be used as a company name, should that be necessary. URL centerwise.com has been registered for one year.

Name has been submitted name for trademark registration [Darryl]

Marketing proposes release number to be V1.5

Program areas that need to be changed with new name have been identified [Ramesh]

Marketing has kicked off artwork with Fuse on Wednesday, May 31.

Action Item/s: Finalize component names (BCP, agent, WebSock) [Marketing]

Proposal is: Centerwise Control PointCenterwise AgentCenterwise Administrator

Marketing to provide usage guidelines for name in product (e.g. with/without TM, capitalization, filenames, etc.) [Paul]

Marketing to submit product name to Web search engines. [Lisa, Paul]


5. Product OverviewThis section is intended to communicate the overall functionality /usefulness of the product.Ongoing communication is needed as product positioning and major new features change.

System Requirements

Control Point (server software ) r equirements Windows 98 Second Edition, Windows NT V4.0 SP5 or higher, or Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server Windows NT or Windows 2000 recommended (Supports both Workstation and Server versions of Windows NT and Windows 2000 Pro)

Disk Space: tbdRAM: ~64 MB

Client software requirements Windows 95/98, Windows NT V4.0 SP3 or higher, Windows 2000

Disk Space: tbd

Product Description (draft)Centricity Centerwise™ is a software system that helps enterprises and service providers deliver applications more effectively, more reliably, and with better business outcomes. By providing dynamic bandwidth allocation to users and their applications, Centerwise ensures smoother and more predictable application performance at a lower cost. Priorities can be established for users, groups and for critical business applications, ensuring that application service delivery is maximized. The customizable Virtual Help Desk provides proactive user feedback to reduce unnecessary help desk calls and minimize user frustration. Centerwise easily manages existing network applications, and provides the reliability you need when deploying new business applications. (100 words)

50 word descriptionCentricity Centerwise™ is a software system that ensures more effective delivery of business-critical applications. Dynamic bandwidth allocation based on user and application priorities means better application performance and lower costs. The Virtual Help Desk proactively helps to reduce user frustration. Centerwise provides the reliability needed by both new and existing business applications. (52 words)

(modified to include Virtual Help Desk, 03/29/00. Centerwise added 05/30/00.)

Resolved:Minimum platform for CP is Win98, pending customer acceptance


Action Item:


6. Release Schedule


Resolved:Engineering/QA to add build number to About box; SCR #063 completed 1/27.Proposed WebSock2 schedule has been supplied

PRD complete DoneRelease One PRD Addendum DoneFunctional Design by 14 Feb DoneCode 16 Feb – 15 Mar (4 wks)Unit test 16 Mar – 31 Mar (2 wks)Integration w/BCP 1 Apr – 14 Apr (2 wks)To QA 15 Apr – 29 May (6 wks)

Licensing features will be deferred to Release 2.Schedule revised 21 Mar.Schedule revised 16 May.

Action Items:

Week 19 20 21 22 23 24 25 26 27 28 29 30 311-May 8-May 15-May 22-May 29-May 5-Jun 12-Jun 19-Jun 26-Jun 3-Jul 10-Jul 17-Jul 24-Jul

N + I N+I 15-Jun 13-Jul

B15RC4 RC5 RC6 GOLD

WebSockII

to QA 22-May

exit QA

BCP to QA 22-May

exit QA

Agent to QA 22-May

exit QA

Install to QA 22-May

exit QA


7. Product Feature IssuesThis section is a discussion for product feature issues. There is also a change review board which meets to discuss and approve changes from the published design specs.

Resolved:Installation issues resolved and will be documented [Suketu]

MFC questionsWe will find and ship the latest DLLWe will keep local copy/s of dllWe will not install local copy of DLL if user has more recent version

For client-only installation, we will move MFC dll, optional dlls to disk 2

Graphics/Charting features will be included in initial release and previewed at Networld + Interop Demo

We will add LSP functionality for better winsock 2 support.

QA will burn test/gold CDs from Engineering image.

Bitmap names for popapps need extension change.

Action Items:


8. Benchmarks

Short Description:Baseline performance measurements are needed to ensure that our software maintains a high level of performance from version to version.

Benchmarks may be of two types:Relative to baseline (no Centricity software installed.)

Marketing suggests that aggregate system performance be within 1-2% of baseline performance

Relative to previous version.

Resolved:Benchmarks defined in PRD Addendum 1

Ganymede may be a good benchmark package. We have some experience with their products, and they are a respected name.

Action Item/s:Specify required analysis reporting [Rick]

Complete initial testing by RC6. Jim to distribute results to Marketing[Jim]

Benchmarking to become part of system testing. [Jim]


9. 3rd party compatibilityShort Description:Compatibility must be demonstrated and documented for a wide variety of software and hardware applications.

Applications

The prioritized list can be found below:

Here's the early minimal list of show-stopper candidates (i.e., if we don't control these, we don't ship):

* Internet Explorer 4.0, 5.0 and 5.5 (both HTTP and FTP)* Netscape Communicator 4.04 and 4.73 (both HTTP and FTP)* NetMeeting 3.01* MS Outlook 98/2000* HTTP protocol as evidenced by Internet Explorer 5.0* FTP protocol as evidenced by Internet Explorer 5.0 FTP* NNTP news protocol as evidenced by Outlook Express newsreader* SMTP mail protocol* POP3 mail protocol

Lotus Notes SQL – ODBC over TCP/IP Netscape 5.0

Medium-priority candidates that could get bumped to show-stoppers:* AOL Instant Messenger* NetMeeting 3.0* Real Audio/Video* NetShow* SAP R/3* Siebel* Scopus* Citrix WinFrame* Microsoft Terminal Server* Yahoo Instant Messenger* PeopleSoft* Microsoft Instant Messenger* DNS protocol* SSH protocol* IRC chat protocol * Telnet protocol (aka TN3270)* Netscape 6


Lower-priority control:* Atomtime* Stock Ticker* PC Anywhere* Gopher* Ping* PointCast* Finger* Kali* LapLink FTP* Cute FTP* MS Office FTP* Laplink* Napster

Distribution Systems Microsoft SMS (Systems Management Server)Novell ZENworks

Resolved:Pctest is our vendor of choice. www.pctest.comThey will perform one pass, about 1-May (~RC4)RC5 will be the PCTest version

PCTest will test all Tier 1 & 2, that they have on hand.

The longer list of apps can be found at the following location: \\PRIMARY\Engineering\SoftwareQA\Application.doc

Action Item/s:

Top tier application regression testing to be part of acceptance testing. [Jim]

10. Year 2000 Readiness

Defined:"Year 2000 compliance means that neither performance nor functionality of the products or services we sell, our internal business processes, or our external relationships is materially affected by dates prior to, during and after the year 2000.

In particular:

Rule 1.No value for current date will cause any interruption in operation.


http://www.pctest.com/

Rule 2.Date-based functionality must behave consistently for dates prior to, during and after Year 2000.

Rule 3.In all interfaces and data storage, the century in any date must be specified either explicitly or by unambiguous algorithms or inferencing rules.

Rule 4.Year 2000 must be recognized as a leap year.”

Resolved:Engineering has adopted this readiness standard.QA to test and certify product for compliance.

Action Item/s:


11. Product Contents

CD will contains the followingProduct SoftwareGetting Started GuideAdmin GuideAcrobat Reader V4.0 PackageReadme file

CD Volume Name: (tbd)CD Label: (tbd)

Action item/s:Prod Mgmt to document top level directory structure here [Rick]

12. Packaging (BOM)


Resolved:Can CD-R be used for first release?

Quality issues must be addressedVisual – silver CD is preferred to green

Is silk-screen label required or is ink jet label sufficient? Silkscreen label is required

(FUTURE ) Join UCC prior to packaging finalization.$500, takes 5 days.Apply two weeks prior to final package design. [Paul]

Issues: Join UCC to get UPC company prefix : http://www.uc-council.org/

Each item in BOM must have a part number


http://www.uc-council.org/

Action item/sComplete BOM and submit to Darryl – Draft complete [Rick]Setup part numbering scheme [Lisa, Rick]


13. Production/Manufacturing/Inventory

Short Description:This section addresses product production.

Estimated production quantities through Dec 31 2000

PRODUCT ELEMENTS Part Number Quantity

PRODUCT CDR (BLANK) 231000-001 500EMPTY TRAY 781000-001 1000GETTING STARTED GUIDE/LICENSE AGREEMENT (8 page booklet) 231001-001 500TRAY LINER 231002-001 500PRODUCT CD - REPLICATED VERSION 1.1 NA 100*Assembled Product 781001-001 100

*100 Replicated with Centerwise™ 1.1 at product launch: Aug 21, 200050 for distribution - 50 for employees

Resolved:Prototype/Pre production samples are planned for N+I show(update – N+I is technology preview only)Units will be needed for employee samplesLisa has taken responsibility for ordering and acquisition of components

Action Items:


14. Documentation

Getting Started Guide (GSG) Administrator’s Guide (AG) Online Help

Initial release requires screen level context

Each screen (dialog box) should provide a help button. Administrator applications only (WebSock, BCP) Client/Agent will be defined separately

Each button should call a unique tag and/or .html file (we can assume the presence of a browser.)

.html Help files will be provided by Marketing/Documentation Text will be based on text created for Administrator’s guide

ReadMe.html Marketing/Documentation will work with QA/Engineering to create. QA to provide source input for docs.

Item Formats Who StatusGetting Started Guide

Hard copy, PDF Marketing Final Draft

Admin Guide PDF only Outline started 1/27/00

Online Help Context sensitive HTML

Begin 3/1/00

Beta ReadMe HTML QA/Marketing

RC1 created

CP Help FilesReadMe HTML “

Resolved:\\Primary\Users\Common\CurrentUserDocs\New Docs to be delivered at each RC date. Change bars or Diff file desired

Action Item/s:

Review Control Point help files [Laura]


15. Localization

This product will be delivered in English only. Product should be reviewed carefully to eliminate UK English references, (e.g. “behaviour”)

Localization strategy – tbd(Use separate resource files for strings)

Resolved:No action at this time


16. Artwork

Software relatedSplash screens

Client startup, size approx. 350x250 pixels. 256 color compatible.

AboutBox logo

Installation BillboardsOne billboard/background may be needed.

IconsCD-ROMExecutable programs

Packaging related

PackagingCD Label

Other

[Windows Wallpaper]

Resolved:Fuse has been engaged to create look/identity for Centerwise.They will also create product packaging.

We will create splash screens and logos in-house as required.

Action Item/s:

17. Final Agent splash screen to Eng. By Thursday. [Lisa]


License AgreementInclude Click-to-Agree License agreement as follows (Draft):

Resolved:Proposal is to warranty media only.

Action Item/s:Marketing to have legal review of agreements.

In process. [Mark]

Need by RC6Final Agreement reviewed by Paul, to be included in Thursday build[Paul]


18. License Management and License Keys

Short Description:

Two license keys will be required to install the software:

Key type 1: Enables server functionalityKey type 2: Enables a given number of concurrent client users

Multiple type 2 keys may be used. Each should be visible along with the number of users enabled by each key.

Key type 3: EvaluationA third key type can be used to enable the server and the maximum number of clients (e.g. 100) for 30 days.

Complete definition of the keys and behaviors will be documented separately.

Issues:Key generation mechanismWeb-based registration“SoftwareKey” product is a candidate

Resolved:This release will not include licensing features.Paul to create licensing proposal for next release.

Action Items:


19. SKU #s, UPC, Pricing

Action Items:


20. Service & Support IssuesHere is my first cut. I am interested in any feedback you have regarding support and maintenance for Centerwise. This covers just the first phase and should carry us through the end of the year. We will revisit our Support and Maintenance product offerings as we ramp our customer base.

Centerwise Support and Maintenance One level of service offered Service will be available during business hours from 8am Eastern time to 5pm Pacific time Acknowledgment of customer problem will be issued within four hours of initial receipt (follows

business hours detailed above) Point releases are included as no-charge updates Full version releases may require an upgrade fee Support and Maintenance will be contracted on a three year basis with automatic renewal at

each anniversary and yearly payments Annual Support and Maintenance fee will be 20% of the customer's Centerwise purchase total

Action Items Required Develop detailed plan on how we implement and cover [David H] Develop Support and Maintenance agreement [Rick and Mark B] Develop Product Brochure for Sales and Web Site [Wade G]

Also, I would like to convene a standing meeting as a forum for monitoring and managing our connection to customers. The meeting will deal with service and support issues as well as pre-sales challenges. This will be an open meeting chaired by Product Management where anyone in Support or Sales can raise issues. Meetings will be scheduled on a weekly basis but will not be held when there are no open issues. Different members from Engineering, Marketing, Sales or Support will be required to attend when that person's presence is necessary to resolve a particular issue. The goal is to build and maintain a loyal base of customers. Items to be covered in the meeting:

Review all open customer generated problem reports. Review issues raised by customers through sales Review sales opportunities which can benefit from extra Engineering or Marketing (revenue

propositions) (Describe product service issues here)

Service PricingComprehensive support and maintenance will be available for purchase and strongly recommended for all direct purchases.

Price will be set at 15% of the software list price.

All seats must be covered by support. Initial purchases will be for 12 month duration or longer. Subsequent purchases may be prorated in order to synchronize support period with prior purchases.

Service LevelsResponse times to product bugs will be based on the severity of the bug.

Priority One (P1):Product is substantially inoperative or is affecting the ability of the customer to conduct normal business.


Priority Two (P2):Work around is possible but inconvenient.

Priority Three (P3):Opportunity for improvement

Registration PolicyIncentives for registration or required registration?

Upgrade Policy Service packs are expected to be released approximately every six months. New versions are expected approximately once per year. Interim patches will be delivered on an as needed basis.

Electronic delivery of Service Packs (.rtpatch from PocketSoft, or Microsoft Installer?)ResolvedNo registration incentives at this time

Action Item/s:

Services group to define service levels and response times.[David]

Escalation process to be defined [Dave]

Define Support strategy – develop a Support Product Plan. [Rick]


rickc, 01/03/-1,

This will involve a team of people including myself, Paul, Scott, David, Mark and Suketu. Support will be treated as a product of its own right. We will develop an initial strategy involving multiple phases. We will lay out a plan to get us operating in the first phase.

21. QA Issues

Compatibility with third party applications, documentation Y2K European character sets, keyboards, OS, Euro € Release checklist signoff

Issues:Source code controlBug tracking issuesIntegration with Engineering systems, Customer/Tech Support systems

Action Item/s:

QA to develop test plans and proposed reports. [Jim]Will circulate for review (Engr, Mktg, Cust Supp)BenchmarksY2kInstallation

Product Management to develop release checklist.Circulate draf. [Rick]

Final checklist to include version numbers. [Rick]


22. Tech Support IssuesNeed to define (Define any issues here)

Action Item/s:Define delivery mechanisms (800#, Web, email) [tbd]Define policies [tbd]

Plan for turn over from Engineering. [Josh]

23. TrainingOutline

Day 1 Hands on training (Need to get use of David H's demo setup) [Rick and David H]

Install and configure a simple single machine system (Each person will do this at a workstation). Exercise basic operations:

User setup Group setup Application and service priorities CP charting

Install and configure a sample remote office (this will be done as a team) [Rick and David H] Study requirements Install CP and Administrator Install Agents Establish Policy Monitor performance

Q &A - Wrap up and answer questionsDay 2

Overview [Ernie]Define target customer and sales strategy.

Sales Challenges [Paul, Scott and Rick]Ernie will solicit the sales team for challenges they have faced in selling Centerwise. Paul, Scott and I will develop approaches the sales team can use to overcome the challenges.

Practice Sessions [Rick, Scott, Paul]We play customer.

Web site Tour [Lisa(s)] How to place an order [Darryl] Vision, Next Release and Future [Rick, Paul, Suketu]

Suketu can present his vision. I'll give a description of the next point release(s). Paul or I can give something on the next major release.

Wrap up [Lynn, Scott, Suketu, Ernie] Send them off on fire!!

(Define any issues here)


Third-party and logo certifications

“Designed for Microsoft Windows”

Windows 2000 Certification Customer Benefitshttp://msdn.microsoft.com/certification/appspec.asp

All applications that meet the desktop Application Specifications for Windows 2000: Provide a robust, self-repairing installation that helps minimize conflicts among

shared components (“DLL Hell”) to enable better co-existence of applications. Facilitate easier software deployment and management for organizations. Correctly maintain user preferences and computer settings to ensure a good

“roaming user” experience, support for multiple users per machine, and regeneration of application settings in machine replacement scenarios.

Run in a tightly controlled network environment, to enable network administrators to secure and control corporate desktops.

Provide a consistent user experience and supports accessibility standards to reduce support and training costs.

Provide a smooth transition of the application for users that upgrade from Windows 95 or later operating systems.

Support OnNow power management for a better mobile computing experience.

Your customers will get the greatest benefits when running your application on Windows 2000 operating systems. The same application can also run on down-level operating systems (e.g., Windows NT 4.0, Windows 98, and Windows 95). Many of these benefits will also accrue to customers running your application on down-level operating systems.

Applications that comply with the server specification offer the following benefits: Support for a globally available infrastructure for easier access for the user and

easier management for the administrator. Secure access to resources and security for client-server interactions. Reduced service downtime caused by system failures or planned server maintenance

and upgrades, by exploiting Cluster services (for applications that comply with Windows 2000 Advanced Server requirements).

Windows 2000 Compatibility listing on the Web site.

“Designed for Windows BackOffice”Logo program. Server applications

“Citrix” CompatibleSelf-certification. Need to define requirement.

Resolved:We will be certified on Windows 2000 Professional. This is expected prior to product release

Action Items:Submit Windows 2000 Professional Application for certification [Josh]

24. Royalties, Third-party Software and Redistributables

Short Description:


http://msdn.microsoft.com/certification/appspec.asp

It is desired that no unit royalties are associated with this product.

No royalties are currently associated with this product Ensure that right/s to distribute is documented and on file.

Redistribute: Microsoft MFC 4.2 (specify exact version)

We are using version is 6.00.8267.0 (was 8168)Win 98 SE is 6.00.8447.0

Symantec Visual Café librariesNo explicit permission required.

Adobe Acrobat Reader V4.0Permission is on file.

InstallShieldPermission is on file.

Charting software, program libraries, database drivers, etc.

Resolved:Engineering will ensure latest version of MFC is delivered. [Suketu]We are okay on Sun licensing (per Mick)

Action Items:


25. Patents, Trademarks, Copyrights

Technology name searchsAny product name or component name must be researched for availability and potentially conflicting uses.

Identify patentable technologiesEvery effort should be made to identify patentable technologies and algorithms.

Copyright, Patent Pending and Trademark notices must be displayedsplash screensabout boxlicense agreement screens

Resolved:Engineering and Legal are working all known patent issues and there are no roadblocks at this time.

Draft of patent received and will be filing very soon.

Action Item/s: Marketing to coordinate with Legal team.

Submit product and service names approx. 7 Feb [Lisa]

Submit code for copyright at release [Josh, Darryl]


26. Beta ProgramsShort Description:The general purposes of our Beta programs is two-fold:1. First and foremost is validation of our code (test candidates (TCs) and

release candidates (RC))We have two primary objectives for the RC:

a. Verify the product for no regressions since the prior releaseb. Verify the new functionality introduced in the product

2. Secondly, obtain testimonials in advance of the release that can be used for marketing and generating additional product demand

Deliverables related to Beta programIdentify Beta Sites (Type 1 and Type 2)Signed NDASigned participation agreementGetting Started Guide/Reviewer’s Guide

Letter to beta sitesThanksProduct featuresSupport policyFeedback (web site url)Contacts


Beta Site candidates

Contact

Type (PR, Functional)

, be specific

Location When Notes

CompuCom Dan, Paul Primarily functional test Dallas

March 7Refresh Jun 26

Extremely cooperative. Test environment per our specs. Customer really needs subnet capability for test to proceed.

FirstVPN Dan Vendor, PR Dallas In process

VPN consultants. Customer really needs subnet capability for test to proceed.

Everest Broadband Doug

Broadband Now

(May 16)John Galgay, VP Engineering-Ready for beta in the lab. they realize not ready for service provider management today (discussed we have an enterprise ready product andtechnology we want to develop a solution for broadband offerings).

UUNET Doug In process Internal network

USi Doug

(May 16)Doug to meet with Matt next week (week of May 22)-Suketu and Doug to meet with Matt, Bill Webb (in charge of product lab) and Spearos S. (Chief Architect of Architect and Design Lab) after week of June 6 to prepare for beta test, set expectations, etc.

ADP Dealer services

Demo on 8/2?


Broadband OfficeNBBJ ? Paul Reference,

functional TBD1000 users distributed across the country

Dell Computers Internal NetworkAllstate PossibleState Farm possibleBank of America Dan/Hugh Have Software

PSI Doug/Hugh Sent software

Resolved:Identify unresolved critical product features.

Build 7 = RC1Known limitations include not working with

IE4, Real Audio, Yahoo pager, AOL instant messaging, WS FTP applets.Netscape does not handle DNS names properly, only ip numbers. Known issues with NetMeeting.

Build 7 does work with IE5, MS Outlook, WSFTP, PCAnywhere V9.0

Build 11 planned RC2May include preview version of WebsockII

Action Items:Add beta info to Web site [Lisa/paul]

FeedbackSelf-nomination


27. Product Release Notice (PRN)

This document will provide ‘external’ information for Sales, Marketing, and Channel partners. Includes brief product description, SKU #s, pricing, system requirements, support policies, FAQ, and other information.

Prior to distribution, PRN will require sign off from the following:Director, Product ManagementVP MarketingVP EngineeringVP SalesManager, QAManager, Customer SupportManager, Operations/ProductionOthers as appropriate(cc: Legal)

Channel Pricing will have controlled distribution.


28. Marketing Launch

See \\primary\users\common\ProdMgmt\PDP\product_launch_plan.xls for full details.

Key message document and positioning statement

50- & 100-word descriptions

Web site updatesText content

Product DescriptionWhat’s newFAQ

On-line Demo (walkthrough)Time out EvalWhite PapersOn-line product registration

DatasheetPrintedWeb: PDF

PowerPoint presentation (press, sales & technical)

Partner activitiesPRTradeshow

Press & AnalystsPress ReferencesAnalyst briefingsPress ReleaseReviewer’s GuidePress TourRude Q&A

-end-
