On this day in P1atter History...

   "It will provide reliable, stable, responsive ERL and WebSPIRS with common functionality across all supported platforms."
05/16/97

Message to all staff from JennyW and JohnL

We are announcing on behalf of the MTM an exciting new project called ERL 97. As List Zero development is near completion, ERL 97 is now the immediate priority for development. The starting point for the project is the Consolidated Technology Priorities List (CTPL), prepared by marketing and business managers, which defined technology needs to support our 1997 revenue forecasts.

Mission
ERL 97 is a complete product release. It will provide reliable, stable, responsive ERL and WebSPIRS with common functionality across all supported platforms. We will include other specific functions called for in the CTPL consistent with the urgency of our overriding goal - late summer release to the market.

Who's doing it?
A cross-functional team, delegated by the MTM, will manage the creation and launch of the product. They are

Jenny is in charge of the product and will decide trade-offs between urgency and functionality. She will liaise with all parts of the business with a stake in ERL 97. And she'll report progress to the company.

Denis will make day-to-day technical decisions (that don't affect functionality) to keep the project on track and maintain technical integrity of the product.

Paul will manage the ERL 97 project schedule and ensure that we follow disciplined development and testing processes.

The software development will occur in CCPs working in the context set by this team.

Progress so far
The project is underway. For each CTPL requirement we are writing a specification with enough detail that everyone can see what is required; can make judgements about adjusting requirements; can decide whether to include items; can produce trustworthy schedules; and can tell when the job is done. Here's who's leading on each of the requirements:

* Note that JustinR is leading the Si1verLinker project relating to full content; and ChristineL and NeilC are responsible for Buildware. Jenny is responsible for establishing relationships with them to determine how best to represent them in the context of ERL 97.

** For ERL 97 we have decided that what is needed is a clear strategy statement and Jenny will write this.

Most of the specs will be ready by next week and we'll review them at the MTM. As each is completed and agreed, they'll become the inputs to a series of CCPs (whose deliverables constitute the meat of ERL 97).

Planning and Reporting
Our previous development planning and reporting efforts have not been effective.

For this product release we will follow a guiding principle. We will only allow individual CCP deliverables and dates into the ERL 97 overall plan when they have (a) an agreed detailed spec and (b) an agreed schedule. We'll expect the CCP to demonstrate sufficient clarity about it's task and timescale, that it can genuinely commit - that is, treat the schedule as a contract with the company.

Paul will produce and maintain plans and schedules which we will use to manage the projects and as the basis for progress reporting. Jenny will report progress to the company through Inside Si1verP1atter.

[Back to 'On This Day'] [Back to Secretp1atter] [the 'other' P1atter]

1