|
|||||||||||||||||
Basic FlowThis model will help you run a less complicated project. (To run large and specialised projects, use The Project Model.) The Basic Model has been developed to describe a minimum of activities common to less complicated projects within Volvo CE. By performing these activities, the model shall assure projects are carried out with adequate quality. In particular, it shall assure that decisions are made, based on adequate work supporting the facts and recommendations made. It shall also give directions to help avoid overworking the task Basic FlowThis model will help you run a less complicated project. (To run large and specialised projects, use The Project Model.) The Basic Model has been developed to describe a minimum of activities common to less complicated projects within Volvo CE. By performing these activities, the model shall assure projects are carried out with adequate quality. In particular, it shall assure that decisions are made, based on adequate work supporting the facts and recommendations made. It shall also give directions to help avoid overworking the task PrestudyThe prestudy is an evaluation of an idea or earlier studies, to gain enough information about different project alternatives, to be able to decide on project start. The prestudy results forms an important part of the background material for the Project Charter and Project Description.
Project Initiation and Start phaseThe project is decided by the sponsor and described in the Project Charter. The detailed planning of the project, resulting in the Project Description is done by the first project team. The work in this phase provides a good basis for the excecution, creates commitment and understanding in the project team, secures competence, communicates the work to be done and a realistic planning.
Project Execution phaseThe purpose of this phase is to execute the activities in the project plan according to time, cost and resources in order to achieve the project goals. The activities to be carried out are defined in the WBS and the Time Schedule. The resources are to be supplied by the Line Managers and other resource providers as per agreements based on the Resource Requirement Matrix.
Project Conclusion phaseAll activities in the project are concluded and the Project Organisation is dissolved. Preparation of the Final Report is done.
Purpose, Goal, Objectives and TargetsHere you will understand the Goal hierarchy and learn in detail how to formulate and set up requirements on good formulated Project Goals. All Projects are oriented and guided by formulated Goal, Objectives and Targets. Clearly defined project goals will have a significant effect on efficiency, motivation and control. As the final result of the project is compared with the described achievements in the Goal and the Objectives the formulations must be clear and easy to understand and measure. We use the term Project Goals as a common term for Purpose, Goal, Objectives and Targets. Goal VerificationGoal verification is done after the project is concluded, to verify the project’s effects on the business compared to expected effects described in the Project Charter, Project Description and Final Report. Milestone - Project Description completedA confirmation that the Project Description is completed and verified to be able to take the DP 2 decision.
Milestone - Prepare for decision to approve project resultsConfirm that project results have been achieved and can be handed over to the line organisation/ customer.
Milestone - Prepare for decision to close the projectFinal Report is complete and all material necessary for the decision by the Project Sponsor/Steering Group to close the project.
DP1 - The decision to prepare a Project DescriptionThis decision starts the work in the project initiation and start phase and commitment for resources is granted.
DP2 - The decision to start project executionAt this point the Project Sponsor/ Steering Group will approve the Project Description and allocate the necessary resources to the project.
DP3 - Decision to approve of project resultsApproval and handover of project results to in the Project Charter/ Project Description defined receiver.
DP4 - Decision to approve the Final ReportThe decision to end the project work and give prerequisites for Goal verification.
Project CharterThe Project Charter must clearly describe the Project Sponsors intention with the project and its financial aspects and how the effect shall be verified. It is a compulsory document signed off by the Project Sponsor.
Project DescriptionThe Project Description is the detailed plan guiding the execution of the project. It provides the basis for communication and commitment of the project to the project team and the stakeholders. It is a compulsory document signed off by the Project Sponsor and the Project Leader. It replaces the Project Charter and is referred to throughout the project life cycle.
Final ReportThe Final Report is the summary of the projects results and achievements up to last DP. It is an input to new projects of similar kind and for changes in the Project Model.
Supporting documents & templatesAll suppoting documents and templates available in the PKS Project model will show as a pop-down menu where each item can be accessed by a click.
Here you will find all related information and documents for the selected situation. Click text for example. Project Related documents:
StrategyProject role in organisation, the top level in the Project hirearchy. With information on topis such as portfolio management, organisational issues, roles and Project concepts.
ProjectThe Project Flow, in the PKS model available in two versions; Basic Flow and Project Flow. The Basic Flow is for small and less complicated Project, and the Project Flow is more detailed in description of how to manage a full scale Project. The Basic Flow is represented here. TargetsThe Project Goals are always coherent with the overall company vision, mission and goals. The hierarchy consists of Purpose, Goal, Objectives and Targets. EffectsWhat where the intentions of the Project, what was the effects that where to be reached. Very often lost during the project lifecycle. Who is responsible for the effects. How to verify, secure and follow up. PhaseAll projects are divided into phases, with a defined content both regarding project activities and activities related to the specific project scope, to ensure a successful completion of the project. The phases can be expanded to stages and activities. When specific work methods exist they can be linked to the phases/ stages in the Project Model. PhaseAll projects are divided into phases, with a defined content both regarding project activities and activities related to the specific project scope, to ensure a successful completion of the project. The phases can be expanded to stages and activities. When specific work methods exist they can be linked to the phases/ stages in the Project Model. PhaseAll projects are divided into phases, with a defined content both regarding project activities and activities related to the specific project scope, to ensure a successful completion of the project. The phases can be expanded to stages and activities. When specific work methods exist they can be linked to the phases/ stages in the Project Model. PhaseAll projects are divided into phases, with a defined content both regarding project activities and activities related to the specific project scope, to ensure a successful completion of the project. The phases can be expanded to stages and activities. When specific work methods exist they can be linked to the phases/ stages in the Project Model. MilestoneThe milestone is a Project internal point of verification. Predefined milestones in the PKS model is set as a verification of decision materiel for the next decsion point is complete and valid. MilestoneThe milestone is a Project internal point of verification. Predefined milestones in the PKS model is set as a verification of decision materiel for the next decsion point is complete and valid. MilestoneThe milestone is a Project internal point of verification. Predefined milestones in the PKS model is set as a verification of decision materiel for the next decsion point is complete and valid. Descision pointThe DP’s should provide management control and build confidence in the expected outcome of the project. The Project Sponsor/Steering Group makes the DP decision. The DP decision is based on a formal review related to specific criteria. A decision-point in the project concludes a phase and opens up the next when criteria is met.
Descision pointThe DP’s should provide management control and build confidence in the expected outcome of the project. The Project Sponsor/Steering Group makes the DP decision. The DP decision is based on a formal review related to specific criteria. A decision-point in the project concludes a phase and opens up the next when criteria is met.
Descision pointThe DP’s should provide management control and build confidence in the expected outcome of the project. The Project Sponsor/Steering Group makes the DP decision. The DP decision is based on a formal review related to specific criteria. A decision-point in the project concludes a phase and opens up the next when criteria is met.
Descision pointThe DP’s should provide management control and build confidence in the expected outcome of the project. The Project Sponsor/Steering Group makes the DP decision. The DP decision is based on a formal review related to specific criteria. A decision-point in the project concludes a phase and opens up the next when criteria is met.
Control documentThe control documents are compulsory to every project and secure the purpose of defining and concluding the project. Each control document is the primary documentation and base for the decisions in defined DP:s. Control documentThe control documents are compulsory to every project and secure the purpose of defining and concluding the project. Each control document is the primary documentation and base for the decisions in defined DP:s. Control documentThe control documents are compulsory to every project and secure the purpose of defining and concluding the project. Each control document is the primary documentation and base for the decisions in defined DP:s. Examples & TemplatesExamples will give examplify how to handle a specific situation in the Project Plow. Templates will give you the structure for a useful document related to specific situations.
|
|||||||||||||||||
|
All documents are available in word format
DescriptionProvides an adapted description for the situation related to:
| ![]() |
Tip & AdviceTips & Advice is a presentation of experiences and feedback from PKS users on the specific situation.
| ![]() |
ChecklistsA Checklist is available for all situations in the Project Flow. The Checklist is a short reference for the experienced PKS-User to remenber what to do. The Checklist can be expanded to the desired level of detail. | ![]() |
TemplatesTemplates for Project Charter, Project Description and Final Report as well as a numberr of supporting templates is available in PKS. All templates are available in Word format for editing and filing. Templates will be added continously, based on user feedback PKS development. | ![]() |
ExampleExamples on how to perform a specific activity e.g. Project Goal Formulation or how to use a template. | ![]() |
Related documentsSupport related to the specific situation in the flow.
| ![]() |