(Project Plan for\ <REFERENCE>(PROJECT_NAME) <line><line> DIGITAL CONFIDENTIAL) <REVISION_INFO>(X0.2) <AUTHOR>(N. G. Neer) <DATE> <ABSTRACT>(Abstract) This is the Project Plan for the development of <REFERENCE>(PROJECT_NAME). This capability is current planned as a P1 item for the UNKNOWN release. This project plan is in: <p> STAR::DOCD$:[EVMS.PROJECT_DOCUMENTS]sample.PS and .TXT <ENDABSTRACT> <comment> <HEAD2>(Review Team) <p> <SIGNATURES> <byline>(Important person 1\Group Manager) <byline>(IMportant person 2\Project Leader) <byline>(Important person n\UNKNOWN Project Leader) <endcomment> <ENDTITLE_PAGE> <COPYRIGHT_PAGE> <COPYRIGHT_DATE>(1995) <ENDCOPYRIGHT_PAGE> <CONTENTS_FILE> <PREFACE>(-4) <P> This Project Plan describes how to build, test, integrate, and deliver the Software Component <REFERENCE>(PROJECT_NAME) for OpenVMS AXP (and/or) OpenVMS VAX. <SUBHEAD1>(Associated Documents) <LIST>(NUMBERED) <LE>Investigation Report: <p> STAR::DOCD$:[EVMS.PROJECT_DOCUMENTS]IR-sample.PS <LE>Design Specification: <p> STAR::DOCD$:[EVMS.PROJECT_DOCUMENTS]DS-sample.PS <ENDLIST> <SUBHEAD1>(Change History) <p> <TABLE> <TABLE_ATTRIBUTES>(\MULTIPAGE) <TABLE_SETUP>(3\10\7) <TABLE_HEADS>(Date\Issue #\Description/Summary of Changes) <comment>Use as many <TABLE_ROW> tags as required, using the samples shown as a guide. If you have a long list, use the tags <TABLE_ROW_BREAK>(FIRST) and <TABLE_ROW_BREAK>(LAST) to allow the table to break across pages. <endcomment> <TABLE_ROW>(April 1\0.1\Review version) <COMMENT> ***** BE SURE TO UPDATE DATE_LAST_CHANGED ******<ENDCOMMENT> <DEFINE_SYMBOL>(DATE_LAST_CHANGED\April 1) <ENDTABLE> <p> <ENDPREFACE> <ENDFRONT_MATTER> <RUNNING_TITLE>(Digital Equipment Corporation--Project Plan\Digital Confidential) <HEAD1>(Project Description) <P> <comment> Describe the project, stating what it is, and why the work should be done. Identify any unusual or problematical areas. Specify whether the work is for both VAX and Alpha, or for only one platform. <endcomment> <p> <HEAD2>(Goals) <comment> Give a list of the specific goals of the project <endcomment> <p> <HEAD2>(Non-Goals) <comment> List any specific non-goals for the project <endcomment> <p> <HEAD2>(Staffing) <comment> Show all team members involved in this project, the percentage of time dedicated to the project, and how long they expect to be involved. <endcomment> <table>(Project Staffing) <table_setup>(4\15\15\10) <table_heads>(Contributor\Function\Percentage\Time) <table_row>(Person 1\Developer\100%\6 months) <table_row>(Person 2\Project Leader\50%\8 months) <table_row>(Person 3\Test Writer\40%\1 month) <ENDTABLE> <P> <HEAD1>(Tasks and Estimates) <comment> Describe each task, person responsible, and the length of time to complete it. <endcomment> <reference>(TASKS) contains the project tasks and time estimations for implementing <reference>(PROJECT_NAME). <table>(Project Tasks and Time Estimates\TASKS) <table_setup>(3\35\10) <table_heads>(Task\Engineer(s)\Time Estimate) <table_row>(Finish project\Person 1\1 day) <ENDTABLE> <head1>(Integration Criteria) <comment> List the contents of each project baselevel to be integrated. (Include coding milestones and regression tests.) Describe what criteria is being used to determine readiness for integration. Be sure to include any special configurations or requirements that may be needed at the time your project integrates. <endcomment> <P> This section lists the integration steps for checking in changes for the Sample project. <table>(Integration Steps\ISTEPS) <table_setup>(3\5\35) <table_heads>(Step #\Description\Date Planned) <table_row>(1\Finish project\Oct. 31, 1995) <endtable> <p> The following criteria will be used at each integration step to determine readiness to integrate: <p> <HEAD1>(Defect Containment) <comment> Describe the work being done in the project for defect containment. This would include reqression tests, code review and/or inspection, special testing within QTV or elsewhere, etc. Work planned with groups other thant the project team should indicate the person in the other group who is the contact, and give an overview of the plans. <endcomment> <HEAD2>(Pre-integration testing ) <comment> Describe how you will be testing prior to integrating your code. If the QTV group is involved, provide the contact name. <endcomment> <HEAD2>(Post-integration testing ) <comment> Describe how you will be testing after integrating your code. If the QTV group is involved, provide the contact name. <endcomment> <p> <HEAD2>(Dependencies of this Project on other Projects/Events/Resources ) <comment> Describe any dependencies your project has on outside forces that could affect its success. When possible describe what is being done to track and minimize these depencencies. <endcomment> <P> There are no dependencies of this project on other project/events. <HEAD2>(Dependencies of other Project/Events on this Project) <comment> Describe any other projects that are dependent on your project for their success. When possible describe what is being done to minimize the impact to other projects. <endcomment> <P> There are no other projects dependent on this project. <HEAD2>(Risks) <P> <comment> State any currently known risks and the steps that are being taken to address them. <endcomment> <p> <HEAD2>(Contingencies) <comment> Describe and contingency plans you are considering. For example, if this is a hardware based project, what will happen if the hardware slips. <endcomment> <P> If the hardware slips we are going on vacation. <HEAD1>(Special Field Test Considerations) <comment> Describe the type and number of field test sites required. <endcomment> <p> There are no specific field test requirements for this project above the current requirement for OpenVMS. <HEAD1>(Documentation) <comment> Describe which current manuals will need changes, and what new manuals will need to be written. Identify the documentation contact for this project. <endcomment> <HEAD1>(Security) <comment> Describe any known security impact this project will have. If you are unsure how to assess this, see Bill Davenport. <endcomment> <HEAD1>(Internationalization) <comment> Describe and known impact this project will have on internationalization issues. If you are unsure how to assess this, see C. J. Coppersmith. <endcomment> <HEAD1>(Performance) <comment> Describe any potential performance issues that may be created by this project, and how you are measuring and handling them. If you are unsure how to assess this, see Sue Lindenberg. <endcomment> <HEAD1>(Issues) <comment> Provide a list of outstanding issues. As they are resolved describe the resolution in the resolved issues section when you update the project plan. New issues would be added to the outstanding issues section. <endcomment> <HEAD2>(Outstanding Issues) <HEAD2>(Resolved Issues) <P> None at this time. <head1>(Project Milestones) <comment> This section describes your schedule <endcomment> <table>(Milestones) <table_attributes>(keep) <table_setup>(3\35\10) <table_heads>(Milestone\Date\Actual) <table_row>(Finish project \Oct. 31, 1995\) <endtable> <head1>(Changed Modules) <comment> To the best of your ability, list those modules and/or components that your project will be changing. This should be updated as the project moves along. <endcomment> <list>(unnumbered) <le>bigmodule.b32 <endlist>

$ DOCUMENT/CONTENTS PP-sample.SDML REPORT PS This is the project plan template for the Gryphon release of OpenVMS. The template describes the information that the release team needs to do the best job possible integrating your project with V7.1. You are not _required_ to use this template; rather, Kathryn Begley designed this template in response to requests that many project leaders have made for a project plan template. This template was reviewed by several persons, among them Clair Grant, who provided these comments -- I think his words are well taken: A little history. If you haven't already, you should look at DOCD$:[EVMS.PROJECT_DOCUMENTS]LIFE_OF_A_PROJECT.PS to see what our thoughts were on what should be in a project plan. Also, an earlier version of this document had a third quote on the front page, "A template is no substitute for thinking." (PROJECT_NAME\Sample Project) (Project Plan for\ <REFERENCE>(PROJECT_NAME) <line><line> DIGITAL CONFIDENTIAL) <REVISION_INFO>(X0.2) <AUTHOR>(N. G. Neer) <DATE> <ABSTRACT>(Abstract) This is the Project Plan for the development of <REFERENCE>(PROJECT_NAME). This capability is current planned as a P1 item for the UNKNOWN release. This project plan is in: <p> STAR::DOCD$:[EVMS.PROJECT_DOCUMENTS]sample.PS and .TXT <ENDABSTRACT> <comment> <HEAD2>(Review Team) <p> <SIGNATURES> <byline>(Important person 1\Group Manager) <byline>(IMportant person 2\Project Leader) <byline>(Important person n\UNKNOWN Project Leader) <endcomment> <ENDTITLE_PAGE> <COPYRIGHT_PAGE> <COPYRIGHT_DATE>(1995) <ENDCOPYRIGHT_PAGE> <CONTENTS_FILE> <PREFACE>(-4) <P> This Project Plan describes how to build, test, integrate, and deliver the Software Component <REFERENCE>(PROJECT_NAME) for OpenVMS AXP (and/or) OpenVMS VAX. <SUBHEAD1>(Associated Documents) <LIST>(NUMBERED) <LE>Investigation Report: <p> STAR::DOCD$:[EVMS.PROJECT_DOCUMENTS]IR-sample.PS <LE>Design Specification: <p> STAR::DOCD$:[EVMS.PROJECT_DOCUMENTS]DS-sample.PS <ENDLIST> <SUBHEAD1>(Change History) <p> <TABLE> <TABLE_ATTRIBUTES>(\MULTIPAGE) <TABLE_SETUP>(3\10\7) <TABLE_HEADS>(Date\Issue #\Description/Summary of Changes) <comment>Use as many <TABLE_ROW> tags as required, using the samples shown as a guide. If you have a long list, use the tags <TABLE_ROW_BREAK>(FIRST) and <TABLE_ROW_BREAK>(LAST) to allow the table to break across pages. <endcomment> <TABLE_ROW>(April 1\0.1\Review version) <COMMENT> ***** BE SURE TO UPDATE DATE_LAST_CHANGED ******<ENDCOMMENT> <DEFINE_SYMBOL>(DATE_LAST_CHANGED\April 1) <ENDTABLE> <p> <ENDPREFACE> <ENDFRONT_MATTER> <RUNNING_TITLE>(Digital Equipment Corporation--Project Plan\Digital Confidential) <HEAD1>(Project Description) <P> <comment> Describe the project, stating what it is, and why the work should be done. Identify any unusual or problematical areas. Specify whether the work is for both VAX and Alpha, or for only one platform. <endcomment> <p> <HEAD2>(Goals) <comment> Give a list of the specific goals of the project <endcomment> <p> <HEAD2>(Non-Goals) <comment> List any specific non-goals for the project <endcomment> <p> <HEAD2>(Staffing) <comment> Show all team members involved in this project, the percentage of time dedicated to the project, and how long they expect to be involved. <endcomment> <table>(Project Staffing) <table_setup>(4\15\15\10) <table_heads>(Contributor\Function\Percentage\Time) <table_row>(Person 1\Developer\100%\6 months) <table_row>(Person 2\Project Leader\50%\8 months) <table_row>(Person 3\Test Writer\40%\1 month) <ENDTABLE> <P> <HEAD1>(Tasks and Estimates) <comment> Describe each task, person responsible, and the length of time to complete it. <endcomment> <reference>(TASKS) contains the project tasks and time estimations for implementing <reference>(PROJECT_NAME). <table>(Project Tasks and Time Estimates\TASKS) <table_setup>(3\35\10) <table_heads>(Task\Engineer(s)\Time Estimate) <table_row>(Finish project\Person 1\1 day) <ENDTABLE> <head1>(Integration Criteria) <comment> List the contents of each project baselevel to be integrated. (Include coding milestones and regression tests.) Describe what criteria is being used to determine readiness for integration. Be sure to include any special configurations or requirements that may be needed at the time your project integrates. <endcomment> <P> This section lists the integration steps for checking in changes for the Sample project. <table>(Integration Steps\ISTEPS) <table_setup>(3\5\35) <table_heads>(Step #\Description\Date Planned) <table_row>(1\Finish project\Oct. 31, 1995) <endtable> <p> The following criteria will be used at each integration step to determine readiness to integrate: <p> <HEAD1>(Defect Containment) <comment> Describe the work being done in the project for defect containment. This would include reqression tests, code review and/or inspection, special testing within QTV or elsewhere, etc. Work planned with groups other thant the project team should indicate the person in the other group who is the contact, and give an overview of the plans. <endcomment> <HEAD2>(Pre-integration testing ) <comment> Describe how you will be testing prior to integrating your code. If the QTV group is involved, provide the contact name. <endcomment> <HEAD2>(Post-integration testing ) <comment> Describe how you will be testing after integrating your code. If the QTV group is involved, provide the contact name. <endcomment> <p> <HEAD2>(Dependencies of this Project on other Projects/Events/Resources ) <comment> Describe any dependencies your project has on outside forces that could affect its success. When possible describe what is being done to track and minimize these depencencies. <endcomment> <P> There are no dependencies of this project on other project/events. <HEAD2>(Dependencies of other Project/Events on this Project) <comment> Describe any other projects that are dependent on your project for their success. When possible describe what is being done to minimize the impact to other projects. <endcomment> <P> There are no other projects dependent on this project. <HEAD2>(Risks) <P> <comment> State any currently known risks and the steps that are being taken to address them. <endcomment> <p> <HEAD2>(Contingencies) <comment> Describe and contingency plans you are considering. For example, if this is a hardware based project, what will happen if the hardware slips. <endcomment> <P> If the hardware slips we are going on vacation. <HEAD1>(Special Field Test Considerations) <comment> Describe the type and number of field test sites required. <endcomment> <p> There are no specific field test requirements for this project above the current requirement for OpenVMS. <HEAD1>(Documentation) <comment> Describe which current manuals will need changes, and what new manuals will need to be written. Identify the documentation contact for this project. <endcomment> <HEAD1>(Security) <comment> Describe any known security impact this project will have. If you are unsure how to assess this, see Bill Davenport. <endcomment> <HEAD1>(Internationalization) <comment> Describe and known impact this project will have on internationalization issues. If you are unsure how to assess this, see C. J. Coppersmith. <endcomment> <HEAD1>(Performance) <comment> Describe any potential performance issues that may be created by this project, and how you are measuring and handling them. If you are unsure how to assess this, see Sue Lindenberg. <endcomment> <HEAD1>(Issues) <comment> Provide a list of outstanding issues. As they are resolved describe the resolution in the resolved issues section when you update the project plan. New issues would be added to the outstanding issues section. <endcomment> <HEAD2>(Outstanding Issues) <HEAD2>(Resolved Issues) <P> None at this time. <head1>(Project Milestones) <comment> This section describes your schedule <endcomment> <table>(Milestones) <table_attributes>(keep) <table_setup>(3\35\10) <table_heads>(Milestone\Date\Actual) <table_row>(Finish project \Oct. 31, 1995\) <endtable> <head1>(Changed Modules) <comment> To the best of your ability, list those modules and/or components that your project will be changing. This should be updated as the project moves along. <endcomment> <list>(unnumbered) <le>bigmodule.b32 <endlist>