Go to the Students section
Go to the Staff section
Go to the Alumni section
Go to the Study here section
Go to the International section
Go to the About section
Go to the Research section
Go to the Business and Employers section
Go to the Support us section
Setting out what you want to do
A project ‘begins’ when the Sponsor/business gives the Project Manager a 'mandate' to develop the Project Brief. If this is a major project, a Mandate should have already been completed and approved through the integrated planning process.
The Project Manager will meet regularly with the Sponsor to ensure that the project develops in a way that the Sponsor supports. The PM then writes an initial outline of the project background, objectives, scope and exclusions in the form of a Project Brief. This is approved by the Sponsor to check it accurately reflects what they've been asked to do.
The Project Manager begins initial stakeholder identification and talks to user group representatives to help them understand the aims of the project and develop the brief further. They begin to elicit details of what customers and users expect of the product or service being developed.
Requirements gathered now are about what customers expect the product to do or to be like, not technical details or technical approaches to how the requirements are achieved. Those will come later in discussion with technical experts.
If there are a lot of stakeholders the Project Manager may seek their Sponsor’s approval for early engagement of a Senior User to help with requirements gathering. The PM and Senior User will work with the users to prioritise long requirements lists into essentials and desirables. This forms the basis for developing the ‘Acceptance Criteria’ - those qualities that the deliverables must have in order to be deemed ‘fit for purpose’ and, without which, it will be rejected.