All activities needed
to build a Project Brief are listed as links with “traffic lights” in front.
For example,
selecting” “Define project”, takes the Project Manager to a module where
Objectives, Scope, Constraints, Stakeholder & Interfaces (“tab menu’ed”)
are defined.
Throughout the
application, the user (Project Manager) can access guiding questions to help
understand the intention of the topic and to help phrase questions to
stakeholders
When the Project
Manager has worked on the steps needed to prepare a project brief, the
application can generate a project brief based on the information.
Note: The intention is
not for all process steps to turn green before generating a Project Brief. The
intention is to make sure all these areas are reflected on and considered
before proceeding.
The project Briefs can
be exported in Draft version for Review (Word/PDF) and one can track Approved
versions
The approval to start
a project is aligned with the approval of the Project Brief. When the Project
Brief is registered as approved, the home screen of the application will change
and show the process steps needed for Initiating a Project where the end result
is to generate a Project Initiation Document (PID).
Note: It is not the
intention that Project Owners (Executives) or other Project Board members should
approve briefs or PIDs in ProjectLink. It is sufficient for the project manager
to get the approvals confirmed in meetings or e-mails. Then the project manager
registers the approval in ProjectLink. We do this to create transparency to
where we are in the project.
