Students will be introduced to the Time Management processes and their associated terms, tools and techniques that will be introduced in further courses in this Knowledge Area and that are used throughout the lifecycle of the project.
Students will gain an understanding of the project due diligence which enables the client organisation to decide if they should proceed with a project and, if so, how to do so in a way that enables them to manage the social, economic and environmental risks.
The Project Manager (PM) must document the client, stakeholder groups and individuals. Each stakeholder group or individual will have their own set of project priorities and outcome objectives which must be identified and documented.
The PM must identify how the project intends to deliver on each stakeholder’s priorities and objectives, what influence each stakeholder will have on the project and level of communication is required with each stakeholder.
The PM may not have visibility on all stakeholders at the time of starting out in the project, however must identify those that are impacted by or have influence on the projects outcomes that are known to the project at this early stage.
In this course, you will gain an understanding of the importance of defining what each role is responsible for, on a project team.
Approximately 10 Minutes
Define business requirements is necessary to capture and agree the project’s scope. These requirements are used to define the project deliverables, against which project delivery is measured.
The Client’s requirements will normally be expressed as required attributes or properties of the asset under construction (system, building, etc.) and as a description of the works required by the Client from Organizations: normally expressed as a Statement of Work (SOW). In addition to Client requirements, the project may have other requirements arising for example from Organizations policies, legislation and regulation relevant to the nature of the project.
In this course, you will gain an understanding of the high-level process for defining the project requirements to meet the scope of the project relative to the high level business needs of the organization, and the requirements gathering process and techniques to achieve the desired results.
Approximately 20 Minutes
The Project Manager will verify that the product or service meets the Client requirements, defined as the project scope in the contract and project documentation.
To validate that functionality, as defined in requirement specification, has the intended behavior of the product or service validation typically involves actual testing and which takes place after verifications are completed.
Depending on the nature of the project, deliverables may be accepted progressively throughout the project lifecycle (known as progressive acceptance).
In this course, you will gain an understanding of the key five steps to controlling project scope.
Approximately 20 Minutes
Validate Scope as part of your requirements management is the process of formalizing acceptance of the completed project deliverables. The key benefit of this process is that it brings objectivity to the acceptance process and increases the chance of final product, service, or result acceptance by validating each deliverable.
The requirements management plan is the process which describes how the project requirements are validated. The scope baseline is compared to the actual results of the project at the point of completion to determine if a change, corrective or preventive action is necessary to be implemented in the project.
In this course, you will gain an understanding of the process for developing the Requirements Management Plan and how to define and communicate how the project requirements are to be captured and managed through to delivery.
Approximately 20 Minutes
Kickstart your next project with your own team.