Formulate the project goal. The project goal includes a time limit (ready date), estimated costs and a general description of the project outc
Describe the purpose of the project in concise terms, that is, the long-term effects of the project and its outcome.
The purpose is a description of the general aim and direction of a project and the effect the project outcome will have.
Give a brief orientation on the business opportunity, related to the project outcome.
If applicable, provide information on the market situation for the project outcome. This includes information on, for example:
· The customer and the status of customer agreements (tender, contracts, etc.)
· Profitability calculations for the project outcome
· Technology trends and trends on the supplier market
· Competitive products and the market window
Briefly describe the current situation and the reasons for carrying out the project.
The background description helps putting the project into the right context and gives everyone involved a common view of the project.
· Fault density
In order to elucidate the project scope, state what requirements are made on the project from the organization in terms of competence development, testing of new methods or techniques, etc.
State the effects of these requirements on, for instance, budget, lead-time and competence development needs.
State the specific quality objectives for the project performance expressed in measurable terms, for instance:
· Planning precision
· Precision in lead-time, etc.
In order to avoid future shifts in the level of ambition, state what is specifically included in or excluded from the project in relation to its goal.
· The work breakdown structure for the project.
· Estimation principles
· Principles for activity sequencing
Prepare a time-schedule including the main activities in the project master plan, the tollgate decisions and other important events.
Include the project milestones in the project's time-schedule.
Prepare a project budget. Include release of funds and major payments in the project.
Specify the individuals composing the project steering function (the project sponsor, the project steering group, etc.) and their roles, responsibilities and authority in the project.
Specify the responsibilities and authority of the project manager and the division of authority and responsibilities between the project organization and the organization in which it operates.
Describe the responsibilities and authority needed to support the project manager. Important areas of responsibility are, for example:
· Administration management
· Technical coordination
· Business coordination
· Configuration management
· Quality coordination
Specify the project executing function in terms of individuals, teams and organizations, as well as their roles, responsibilities and authority in the project.
Identify project stakeholders, such as customers, end-users of the project outcome, partners and suppliers, affected parts of the organization and other projects.
Enclose or document here an overview of the project and its environment of stakeholders.
State the customer in the project (if applicable). In some projects, the customer cannot be identified. If this is the case, an individual or an organization representing the potential customer or the organization's customers should be identified.
If applicable, specify what is expected from and agreed with the customer in terms of supplied products, information, contacts, tools, availability, etc. Refer to agreements on routines for handling customer-supplied products.
List suppliers to the project, such as partners, subcontractors and consultants by name and function in the project. A supplier is not necessarily an external company, it can also be another project, partners, consultants or any other party delivering the products or services needed in the project.
State any special arrangements or procedures that will be used in contacts with the subcontractors. Name contacts, if applicable.
Specify the links between the project and other projects or assignments. Ensure that the relevant dependencies in terms of deliveries to or from the project, and usage of the same resources, are visible in the project's time-schedule.
State the principles for reporting and distributing information within the project for the different groups of external and internal stakeholders. Include, for example, how often the reporting will take place, the type of reports or information, the type of media in which it is presented, and the type of meetings that will take place.
In large projects, a separate document describing reporting and communication principles could be prepared and enclosed to the Project Specification.
Prepare a resource plan, specifying the project's need for human resources, as well as for other resources. Prepare resource profiles, if applicable.
Define what competence development is needed to reach the project goal, and specify who is responsible for providing the training.
If a separate quality plan is prepared, refer to it.
Specify the project strategy that will be employed in the project. The strategy should be based on business strategies, experience and results of risk analyses. Include, for example:
· External provisioning or in-house development
· Technology and development strategies, for instance, incremental development
· Use of external suppliers
· Joint ventures
· Methods and tools to be used
State the internal and external audits planned in the project, for example process audits, product audits or project management audits, as well as who is responsible for calling an audit and how it will be reported.
Describe the procedures to be applied in tollgate assessments.
Describe how and when risk assessments will be performed and reported.
Specify all the different reviews that will be performed during the course of the project, the procedures that will be used and how the reviews are being coordinated and reported. Different types of reviews are milestone reviews, contract reviews and joint reviews (for example, purchaser - supplier).
List the different processes or work models used in the project. Refer to the relevant process descriptions and work models.
Describe how the processes applied in the project have been tailored to the needs of the project or if special routines will be applied.
Describe any special agreements that have been made with the customer.
List the different methods, instructions and tools to be used in the project for each process, or indicate if these are included in the process description. List any deviations.
Describe the routines that assure the correctness of the tools and/or test equipment to be used, and how these will be controlled during the course of the project.
In a project, a number of support activities (that is, activities that are not phase-dependant) are performed to ensure quality of both performance and result. For all the relevant activities, procedures or routines should be defined.
State how to deal with security matters, for instance:
· classification of the project information with regard to requirements for integrity, availability and confidentiality, in accordance with the organization's corporate directives on security,
· specific action that must be taken to fulfill security requirements, such as security agreements with suppliers and partners, security check of project team members, security audits of equipment, usage of coded information, etc.
· authorization of information distribution and publishing, that is, who should decide which information will be distributed to whom,
· routines for monitoring security,
· routines for reporting security incidents.
· Configuration identification
· Configuration control
· Configuration status accounting (for example inspection and test status)
· Configuration auditing
Indicate the quality reviews of the project outcome, inspections, tests and evaluation of measurements planned in the project to verify conformity after each phase during the process.
Define the responsibility for each activity.
Describe the procedures to be used for handling products not fulfilling specified requirements.
Describe the procedures to be used for handling new or changed requirements on the project.
Describe the procedures to be used for managing risks and opportunities in the project.
Describe the procedures to be used for tracking and reporting progress in the project. Describe measurements and key values that will be used, as well as how the reporting will be made and presented.
State how subcontractors will be approved and how quality assurance of their work will be carried out.
Refer to the acceptance criteria that have been agreed on.
Describe the procedures for revising documents.
Describe how to ensure that the latest versions of documents are available to the project.
Describe how quality records will be handled in the project.
Present a list of the most important risks and opportunities that have been identified.
Describe how the identified risks and opportunities have been acted on in the project planning.
Describe or enclose contingency plans for risks that are not possible to eliminate or prevent.
State the legal aspects of the project's results, such as patents, copyright, trademarks, registered names and licenses.
Note any restrictions that apply, or areas where special attention to the threat of infringement is justified.
Note areas in which the project is likely to create inventions that should be protected by patents.
Describe procedure for deliveries to the customer, and for customer's acceptance test, acceptance criteria, etc.
Define which receiving units will take over the responsibility for the project outcome, for instance maintenance, implementation, production, sales, operations, warranty handling, product support and customer services.
State the acceptance routines and criteria of the receiving unit when taking over the responsibility for the project outcome.
State the receiving unit for project documentation and computer-stored libraries. State the acceptance routines and criteria.
Indicate how the project organization will be dissolved and how information on competence acquisition in the project will be transferred to the regular organization.
List any documents referred to in the Project Specification.
The Project Specification is an internal document. Customers and other external stakeholders should not be included in the distribution list. They should instead be given access to a separate quality plan.
Holding a PhD degree in Finance, Dr. John Adams is experienced in assisting students who are in dire need...
55 - Completed Orders
Canada, Toronto I have acquired my degree from Campion College at the University of Regina Occuption/Desi...
52 - Completed Orders
Even since I was a student in Italy I had a passion for languages, in fact I love teaching Italian, and I...
102 - Completed Orders
To work with an organization where I can optimally utilize my knowledge and skills for meeting challenges...
109 - Completed Orders
JOB OBJECTIVE Seeking entry level assignments in Marketing & Business Development with an organization...
202 - Completed Orders
Current work profile Project manager- The Researchers Hub (2nd Jan 2016 to presently working) Researc...
20 - Completed Orders
Sales Assistant, Mito Marina Assigned to the Stationery dept – assisted in merchandising, stock taking...
100 - Completed Orders
Personal Profile Dedicated and highly experienced private chauffeur. High energy, hardworking, punctua...
200 - Completed Orders
I'm Lizzy, full time education specialist in English, Essay Writing, Economics and Maths. Having Assi...
109 - Completed Orders