Difference between revisions of "SCC QSP Project Management"

From SCC Wiki
Jump to: navigation, search
m (Sequential Project Model (4.1))
m (Procedure (4.))
 
(6 intermediate revisions by the same user not shown)
Line 19: Line 19:
 
== Procedure (4.) ==
 
== Procedure (4.) ==
  
* If a project plan has not already been created, create one now according to the format given by [[SCC QSF Project Plan (PRP)]]
+
The assigned project manager shall:
** The project plan should specify which project management model strategy will be followed for project management, either the sequential model or the general model. The sequential model is preferred for SCC product development projects.
 
* Add the project to the [[SCC QSR Project List]]
 
* Iteratively refine the project plan
 
* Capture product data deliverables according to the [[SCC QSP Product Lifecycle Management]]
 
* Provide regular reports to the project stakeholders on the status of the project
 
  
=== Phased Model ===
+
* Create a project plan following either the Sequential Model or the General Model, following [[SCC QSF Project Plan (PRP)]].
 +
* Add the project to the [[SCC QSR Project List]].
 +
* Execute the project according to the PRP and the [[SCC QSP Product Lifecycle Management]].
 +
* Capture project execution and metrics (e.g. tasks completed and rate, team member time tracking, minutes of meetings and phase reviews, etc.).
 +
* Provide regular reports to the project stakeholders on the status of the project.
  
The SCC follows a sequential project model, which suits the general product development projects undertaken by the SCC.
+
===  Sequential Model (4.1) ===
  
The sequential project management model is a domain specific model, a recipe book that guides a project through a number of sequential phases, each followed by a review gate. At each review gate the project stakeholders review the project status and deliberate if the risks are acceptable for advancing the project to the next phase, based on completion of deliverables, level of risk, and other relevant factors.
+
SCC projects generally follow a sequential project model, which suits the type of development projects undertaken by the SCC. The sequential model is a domain specific recipe book, guiding a project through a number of stages with a review to confirm completion at the end of each phase. At a review gate, the project stakeholders review the project status and determine if the risks are acceptable for the project to advance to the next phase.
  
=== Project Phases ===
 
  
 
     Idea -> Requirements -> Design -> Test -> Pilot -> Termination
 
     Idea -> Requirements -> Design -> Test -> Pilot -> Termination
Line 48: Line 46:
 
* Termination - when it is determined the product no longer provides benefit to the organization, all processes involved in the product are reviewed and then terminated in a controlled manner.
 
* Termination - when it is determined the product no longer provides benefit to the organization, all processes involved in the product are reviewed and then terminated in a controlled manner.
  
=== General Project Model ===
+
This is an idealistic view, actual projects typically include more complex interactions:
 +
* There may be iteration within a phase, or between phases.
 +
* Some tasks in the following phase may be started before completing all tasks in the current phase.
 +
* Sub-phases may be introduced to mitigate risk.
 +
 
 +
Deviating from the model can be done at the project manager's discretion, so long as the deviation is visible to the project team and stakeholders, and does not significantly affect project risk.
 +
 
 +
For Maestro, a project is defined as a related set of activities, each activity is associated with only one project.
 +
 
 +
=== General Model (4.2) ===
  
 
For projects other than product development projects, a more general project model is required. There are a number of project management standards that have been developed, such as ANSI/PMI 99/001/2008, ISO 10006, PRINCE2, Agile, and others. In this model, project activities tend to be divided among the following five process groups:
 
For projects other than product development projects, a more general project model is required. There are a number of project management standards that have been developed, such as ANSI/PMI 99/001/2008, ISO 10006, PRINCE2, Agile, and others. In this model, project activities tend to be divided among the following five process groups:

Latest revision as of 17:00, 29 October 2018

Reference: ISO 9001:2008 Element 7.1 Planning of product realization

Purpose (1.)

To establish a procedure for consistent and effective management of projects.

A project is a temporary activity for the purpose of achieving a specific objective. Project management is the discipline associated with planning, directing and managing resources for the successful completion of that objective.

Every project is different, but a common critical success factor is the shared understanding of the project by its stakeholders. The SCC has developed a formal, but flexible, project management process which is tailored to each project's unique needs at the onset of the project.

Scope (2.)

This procedure applies to all appropriate projects undertaken by the SCC. As a guideline, an appropriate project is a project with high importance or consequence to the SCC, a project which is expected to consume at least 2 man-weeks of labor, or a project which will require at least 4 calendar weeks to complete.

Responsibility and Authority (3.)

The Director, Quality has responsibility and authority for maintaining this procedure.

Procedure (4.)

The assigned project manager shall:

  • Create a project plan following either the Sequential Model or the General Model, following SCC QSF Project Plan (PRP).
  • Add the project to the SCC QSR Project List.
  • Execute the project according to the PRP and the SCC QSP Product Lifecycle Management.
  • Capture project execution and metrics (e.g. tasks completed and rate, team member time tracking, minutes of meetings and phase reviews, etc.).
  • Provide regular reports to the project stakeholders on the status of the project.

Sequential Model (4.1)

SCC projects generally follow a sequential project model, which suits the type of development projects undertaken by the SCC. The sequential model is a domain specific recipe book, guiding a project through a number of stages with a review to confirm completion at the end of each phase. At a review gate, the project stakeholders review the project status and determine if the risks are acceptable for the project to advance to the next phase.


   Idea -> Requirements -> Design -> Test -> Pilot -> Termination
  • Idea - an idea is presented and found to have sufficient merit for further investigation. A preliminary business justification should be included in the Idea phase.
  • Requirements - the idea is developed into a specification or set of requirements. A development project is created with costs, and the business justification is refined.
  • Design - a design is completed that meets the decided requirements. Prototypes are typically produced and tested by the development project team.
  • Test - prototypes are evaluated against the design requirements (verification testing) and customer expectations (validation testing).
  • Pilot - all processes involved in producing and bringing the product to market are evaluated and tested. Processes may include the raw material supply chain, manufacturing, sales order entry, shipping, etc. The product is considered to be in full production once it has passed the Pilot phase gate.
  • Termination - when it is determined the product no longer provides benefit to the organization, all processes involved in the product are reviewed and then terminated in a controlled manner.

This is an idealistic view, actual projects typically include more complex interactions:

  • There may be iteration within a phase, or between phases.
  • Some tasks in the following phase may be started before completing all tasks in the current phase.
  • Sub-phases may be introduced to mitigate risk.

Deviating from the model can be done at the project manager's discretion, so long as the deviation is visible to the project team and stakeholders, and does not significantly affect project risk.

For Maestro, a project is defined as a related set of activities, each activity is associated with only one project.

General Model (4.2)

For projects other than product development projects, a more general project model is required. There are a number of project management standards that have been developed, such as ANSI/PMI 99/001/2008, ISO 10006, PRINCE2, Agile, and others. In this model, project activities tend to be divided among the following five process groups:

   Initiating -->  Planning --> Executing --> Closing
               ^                     |
               |                     v
              Monitoring and Controlling

This is a conceptual model, and must be adapted to a specific project to be practical.

Related and Support Documentation (5.)

The following documents may be useful in product development projects:

  • Electronic Product Design Checklist TODO - include in Maestro SCC document management.