Presentation on theme: "650.315.7394 1 Sample Roadmap: Introduction This is a “sales” roadmap, which is designed to show customers that your."— Presentation transcript:
Sample Roadmap: Introduction This is a “sales” roadmap, which is designed to show customers that your company has a plan, and that the plan makes sense We’re assuming two product lines: Desktop teleportation software suitable for tele- transporting 1 or 2 people Mainframe teleportation software for entire corporate departments, e.g. for the annual Sales meeting Normally, there are lots of development projects which do NOT fit nicely into a customer story. Grouping your projects into customer-friendly stories is half the work For each product and release, look for a “release theme” or other story that knits the R&D items together Show the requirements which match up against the features and improvements that you have scheduled Last slide has an internal engineering roadmap for contrast
Two Products, Two Target Markets Desktop Tele-Transporter ® Low cost, low power, low bandwidth Ease of use FCC Class 1A license readily available Rated for up to 2 persons/hour Enterprise Tele-Transporter ® Rated for up to 105 persons/hour More efficient for frequent use Operator needs FCC Class 4B license (2 year cert) 5 Mw electricity, 45 Gbps network, 7 TB storage
Requirements by Product Line DesktopEnterprise 1. Error Recovery 2. High availability 3. Voice activated 4. Kerberos (encrypt stream) 5. Multithreading (group transport) 6. Role-based permissions 7. Prepaid, third party billing 8. Volume reduction (liposuction) 9. Caller ID 10. Transport Insurance Corporate and personal requirements leading to divergent product sets.
Product Line Evolution Q3-03 Desktop Enterprise Remote-ESP Desk v3.1: Error recovery Voice activation Simpler UI Q4-03Q1-04Q2-04Q3-04Planning Desk v3.3: Caller ID Secure Channels Ent v3.2: Error recovery Multithreading High Avail Ent v3.4: Role-based Prepaid, Insurance Kerberos Software-only solution Theme: improved performance and UI Theme: improved security and billing
Internal Development Schedule Internal project map is not for customers Usually has many steps, milestones Schedule assumptions are often aggressive Don’t confuse internal project roadmaps with “customer-friendly” external roadmaps