1. Erich Gatejen Exec Status 30 May 2002

2. Overall Status Project-X is on schedule. Application-Y on schedule  We are spending a lot of time working on the documentation. Product-F 1.1 (Cycle 2) is 50% done.  We are a little behind.  Fix pack in test. Service Packs (July Release) are ahead of schedule. GOLD Labs and other services all ok.

3. Status of outstanding milestones Project-X Functional Testing is done. Application-Y is about 20% done.  We have to create the documentation.  Unit Testing is done.  Functional Testing started. Working on Cycle II of Project-F. Services Pack for W2K Testing is done.  Strange bug found. #12912. It will take several days to investigate. (MEDIUM Schedule Risk)  Issues may require a new cycle of testing. Solaris packs underway.  All done except Module-J.  Bug numbers are in line with expectations.

4. Project-X Dashboard ComponentWindows due 11 JunSolaris due 11 Jun Platformpassed Portaltesting Tracking and Accountingtestingloading Connectorstesting Management Consoleproblemstesting Conversion subsystemtestingloading Content Managertesting User Managerpassedloading Interface Managertesting Application-YloadingN/A Application-ZtestingN/A {blank}loadingproblemstestingpassed

5. Key Items from Tasking Orders For the week of 27 May  Slack time for Service Packs Load any Cycle II service packs, if they fix critical issues.  Resume Application-T deployment (Bravo-1).  Module-J testing (round 2)  Application-Y integration and handoff (round 1)  Project-F testing (cycle 2) For the week of 3 Jun  Complete Application-T deployment (Bravo-1).  Accept Release Candidates for Project-X  Complete Module-J testing  Project-F testing (cycle 3)  Acceptance Testing for any outstanding Service Packs.

6. Lab Delivery Schedule: 6/4Application-Y and Application-Z (build cycle 5/27) - Handoff to developers for bug regression testing. 6/4SP releases for both, Windows and Solaris. - Delivered early. 6/10Direct Connect lab (Solaris) 6/11SP releases after Final Acceptance (for both, Windows and Solaris) - Handoff for training. 6/17GOLD updates

7. Issues & Risk  The component teams *must* meet build and install criteria for this schedule to work.  I.e. automated installers, migration in less than an hour for standard test data set, et al.  Content Manager currently violates this criteria. We have a workable solution that involves documenting manual steps.  All others appear ok.  Application-X and Application-Y documentation need a lot of work.  We may have to continue this after the RTM and roll the documentation CD later.