Professional Documents
Culture Documents
Project QA, Collab Plan
Project QA, Collab Plan
Kolb
Note:
Text displayed in blue italics is included to provide guidance to the author and should be deleted or hidden before publishing the document. This template can be used at it is, or to complete and improve an already existing template.
Distribution:
<Org., Name>
Appendices:
<Appendix 1>
Help: The purpose of the Project QA and Collaboration Plan is to document all activities and collaboration procedures that are required to execute the project successfully within its constraints.
Page 1
Contents
1. Organization .............................................................................................................3
1.1 Project-internal Functions ..................................................................................... 3 1.2 Change Control Board (CCB) ................................................................................ 3
Page 2
1. Organization
1.1 Project-internal Functions
Help: Since the project manager has the overall project responsibility, he /she is also responsible for the project-internal functions. But he/she can delegate the management of these functions to project team members. In this case list the functions and individuals responsible for Example: Function Quality Assurance System Test Lead Validation Lead Configuration Mgmt Change Mgmt etc. Organization: Name Comment
Page 3
Milestones M0
Milestone Criteria Budget Release PRS or SRS reviewed Stakeholders identified Impl. Proposal reviewed Scope and concept described
M1
Start Planning <milestone description, e.g. Life Cycle Objectives LCO defined>
<yyyy-mm-dd> <yyyy-mm-dd>
M2
Start Execution <milestone description, e.g. Life Cycle Architecture LCA defined> Confirm Execution <milestone description, e.g. alpa version> Requirements agreed, project plan reviewed, resources committed Architecture reviewed and stable Coding of new functionality finished, Draft documentation Product system tested, documentation reviewed
<yyyy-mm-dd> <yyyy-mm-dd>
M3
M4
M5
M6
Close Project
A detailed Project Schedule is available in 0. The Project Schedule is monthly updated by the Project Manager.
2.2 Resources
Help: List the required project resources based on estimates for project activities, subcontracts, training, etc. Present the distribution of the resources over the whole project life. Category M0M1 Human Resources (internal) Human Resources (external) Travel (for internal people) Travel (for external people) Equipment and Tools (internal) Equipment and Tools (external) Budget for Period in kUS$ M1M2 M2M3 M3M4 M4M5 M5M6
Page 4
Successful Software Outsourcing and Offshoring, Prof. B. Meyer, Prof. P. Kolb Help: Prepare a resource plan specifying the project's need for human resources, as well as for other resources (equipment, tools, licenses, etc.).
Page 5
Successful Software Outsourcing and Offshoring, Prof. B. Meyer, Prof. P. Kolb Define how and how often sub-projects and sub-contractors report to the project manager Define who participates milestone meetings Define how events will be communicated b) External communication and reporting: Define what information will be provided to which stakeholders Define how and how often information will be provided to which stakeholders often (e.g. project report) Plan regular meetings with external stakeholders (e.g. SteCo meetings) Example: Type of Communication Project Meetings Method / Tool Frequency /Schedule Weekly and on event When available Bi-weekly Information Participants / Responsibles Project Mgr Project Team Sub-contractor Project Mgr(s) Project Team Members Sub-contractors
Recurring Communication Activities Project Internal: Teleconference Project status, problems, risks, changed requirements All project documentation and reports Sub-project status - progress - forecast - risks Project status (progress)
Teleconference
Wrap-up Experiences
Project Mgr Sub-project Mgr Sub-contractor Project Manager, SteCo Project Mgr Project Team Sub-contractor Project Manager Sub-Project Managers Sub-contractors Project Manager, SteCo
Communication Activities Project External: Project Report Excel sheet Monthly Project status - progress - forecast - risks
SteCo Meetings
Monthly
Page 6
4. Quality Assurance
Help: The Quality Assurance Plan (QA Plan) can be either a separate document or included in the project plan. If the QA Plan is a separate document refer to it in this chapter. If not, the subchapters below should be used.
Page 7
Successful Software Outsourcing and Offshoring, Prof. B. Meyer, Prof. P. Kolb Activity <Requirements Specification> <Functional and Design Description> <Sub-system x>> <Alpha Release> <Beta Release> <Release> <Review> <Review> <Subsystem test> <System Test> <onsite test> <acceptance test> Type Ver Ver Ver Ver Val Val Author, Reference Group ID Author, Reference Group ID Sub-contractor x Test lead BetaTest Group Techn. Proj. Mgr. Review procedure [x] Review procedure [x] Techn. Proj. Mgr. Project Manager Test Plan [x], Test Spec [y] End User
5.1.2 Baselines
Help: Define major baselines for this project, their purpose and their relation to the projects milestones. Baseline ID Purpose/Description At Milestone
Page 8
Successful Software Outsourcing and Offshoring, Prof. B. Meyer, Prof. P. Kolb Baseline ID Purpose/Description
At Milestone
Description <None or see section 5.1 (Resource Plan)> <None or see section 5.2 (Training Plan)>
Page 9
7. References
Help: List all other documents this document refers to. <Doc. No.> <Doc. No.> <Doc. No.> <Doc. No.> <Doc. No.> <Doc. No.> <Doc. No.> <Doc. No.> <Doc. No.> Project Plan for <project name> Project Requirements Specification for <project name> Implementation Proposal for <project name> Project Schedule for <project name> Risk Management Plan for <project name> Work Breakdown Structure for <project name> Configuration Management Plan (if it is a separate plan) <Sub-contract #1>
8. Revision
Rev. ind. Page (P) Chapt. (C) --Description original version Date Dept./Init.
Page 10
Page 11