Revision Date: 1999-06-06
Source: Andrew Josey, Chair
Action: for review and planning
This is an estimated project timeline. This will be updated after each meeting.
Known risks: We may decide due to delays in .1a/.2b to push draft 2 and beyond back one quarter which would lead to "technical completion" at the end of the first quarter of Year 2001.
This plan allows between 4 and 12 weeks editing cycle for draft production and a 6 week review period for each draft.
Table 1 - Austin Group Specification Draft Schedule
Date | Title of deliverable | Type | Probability | Resources Needed | Assumptions and Dependencies | |
People | Financial | |||||
1 June 1999 | Draft 1 | Draft Standard | 100 | 2 (1 development manager (40%), and one technical editor (40%)) | 10 staff weeks editing + project management .
Signature of MoU between IEEE and The Open Group.
|
|
June 1 - July 14 1999 | Draft 1 Review | Aardvark bug reports | 100 | 1 (1 development manager) | 3 staff days to manage incoming aardvark and prepare for
review meeting.
Assumes working group review the document. The Open Group and IEEE editors to liaise over style changes.
|
|
20-22 July 1999 | Draft 1 Review Meeting | Change Request Report | 100 | 2 (1 development manager, and one technical editor) | 10 staff days plus travel and living costs to attend Review Meeting in Montreal July 20-22
Meeting to be hosted by IEEE PASC, assumes meeting room with external phone line
|
|
October 1999 | Draft 2 | Draft Standard | 80 | 2 (1 development manager (40%), and one technical editor (40%)) | Staff time for production of drafts (6 weeks). Project
management (4 days).
External editing costs.
Incorporates .1a and .2b if complete. If they slip then the schedule for the project slips by one quarter. (it looks highly probable
that these drafts will slip).
|
|
Oct 11 - Nov 22 1999 | Draft 2 Review | Aardvark bug reports | 80 | 1 (1 development manager) | 3 staff days to manage incoming aardvark and prepare for
review meeting.
Assumes working group review the document
|
|
December 1999 | Draft 2 Review Meeting | Change Request Report | 80 | 2 (1 development manager, and one technical editor) | 10 staff days plus travel and living costs to attend Review Meeting
Meeting to be hosted by TBD, assumes meeting room with external phone line
|
|
February 2000 | Draft 3 | Draft Standard | 80 | 2 (1 development manager (40%), and one technical editor (40%)) | Staff time for production of drafts (6 weeks).
Project management (4 days).
External editing costs for merger of external documents (does not include XRAT)
Merges in the following : Networking interfaces from
XNS 5v2 (includes IPv6) , in-flight amendments and c9x changes. Document
style finalised. First IEEE ballot.
First draft of XRAT volume (note this is at risk unless we can
find funding and staff to develop it).
|
|
Feb 1 - Mar 15 2000 | Draft 3 Review | Aardvark bug reports | 80 | 1 (1 development manager) | 3 staff days to manage incoming aardvark and prepare for
review meeting.
Assumes working group review the document
|
|
Mar 27-31 2000 | Draft 3 Review Meeting | Change Request Report | 80 | 2 (1 development manager, and one technical editor) | 10 staff days plus travel and living costs to attend Review Meeting
Meeting to be hosted by TBD, assumes meeting room with external phone line
|
|
May 2000 | Draft 4 | Draft Standard | 80 | 2 (1 development manager (40%), and one technical editor (40%)) | Staff time for production of drafts (6 weeks).
Project Management (4 days).
second IEEE ballot
|
|
May 15 - Jul 3 2000 | Draft 4 Review | Aardvark bug reports | 80 | 1 (1 development manager) | 3 staff days to manage incoming aardvark and prepare for
review meeting.
Assumes working group review the document
|
|
July 10-15 2000 | Draft 4 Review Meeting | Change Request Report | 80 | 2 (1 development manager, and one technical editor) | 10 staff days plus travel and living costs to attend Review Meeting
Meeting to be hosted by TBD, assumes meeting room with external phone line
|
|
September 2000 | Draft 5 | Draft Standard | 80 | 2 (1 development manager (40%), and one technical editor (40%)) | Staff time for production of drafts (6 weeks).
Project management (4 days).
The Open Group Company review draft, and third IEEE ballot
|
|
Sep 4 - Oct 16 2000 | Draft 5 Review | Aardvark bug reports | 80 | 1 (1 development manager) | 3 staff days to manage incoming aardvark and prepare for
review meeting.
Assumes working group review the document
|
|
Oct 23-27 2000 | Draft 5 Review Meeting | Change Request Report | 80 | 2 (1 development manager, and one technical editor) | 10 staff days plus travel and living costs to attend Review Meeting
Meeting to be hosted by TBD, assumes meeting room with external phone line
|
|
November 2000 | Sanity Draft | Draft Standard | 80 | 2 (1 development manager (40%), and one technical editor (40%)) | Staff time for production of drafts (4 weeks).
Project management (4 days)
IEEE Recirculation draft
|
|
Dec 1 - Dec 15 2000 | Sanity Review | Aardvark bug reports | 80 | 1 (1 development manager) | 3 staff days to manage incoming aardvark and prepare for
review meeting.
Assumes working group review the document
|
|
Jan 3 2001 | Sanity Review Teleconference | Change Request Report | 80 | 2 (1 development manager, and one technical editor) | 2 staff days
Teleconference to resolve final issues arising from the Sanity Review
|
|
1Q 2001 | Final Draft | Recirculation Draft Standard | 80 | 2 (1 development manager (40%), and one technical editor (40%)) | Staff time for production of drafts (1 week per draft)
Enter final approval process. If recirculations are needed they iterate at one month intervals.
|
|