ITI Project Brief - v 2022


It is strongly recommended that this template is developed as a Word document and once approved, transferred to this project page (due to the limitation of the website in regard to editing and for easier sharing, tracking and versioning)  



Document Sign-off

Name Role Date signed off
  Project Sponsor  
  Project Manager  
  Programme Manager  
  other stakeholders  





Guidance (please remove)

This project brief has guidance, prompts and tips for many of the sections.

Please remove/edit these as they are there to help authors in writing the document and for project teams to consider but not suitable for the final version of the brief.



Changes to Scope will be logged on the Issue Log and also recorded on the Project Scope Change page.


Out of Scope

Guidance (please remove)

Any significant work we need to explicitly state we are not doing (that some stakeholders may assume or expect that we will).


Objectives and Deliverables and Success Criteria

Guidance (please remove)

Summarise - What we are aiming to do and deliver, by when.

What are we aiming to ultimately deliver that will be key to the measure of the success of this project - but potentially any significant other things along the way (that may outlive the project).

What are our objectives and what deliverables are part of them.

Driven by the Deliverables and Objectives. Do we have objective measures that we can point to to say the project has been a success (typically we said we would deliver X and we have).

  Description of the Objective  
  Description of the Deliverables needed to achieve the objective  
Objective 1   Success Criteria
   Deliverable D1.1    

   Deliverable D1.2

   Deliverable D1.3    
Objective 2    
   Deliverable D2.1    
   Deliverable D2.2    
Objective 3    

   Deliverable D3.1

   Deliverable D3.2    
Objective 4    
   Deliverable D4.1    
Objective 5    
   Deliverable D5.1    
   Deliverable D5.2    

This table can be used through Business and Technical Analysis, Design, Build, and Testing/UAT as a Traceability Matrix to ensure the project brief project objectives and deliverables are followed through.



Guidance (please remove)

State the known requirements that drive the project.

Who has set this requirement (who owns the requirement).

Ideally we set these as MoSCoW:

MUST - we would see the project as failing totally or partially if these are not achieved

SHOULD - we have a high expectation that these will be doable with planned work and budget - but if necessary these can be descoped

COULD - if all goes very well, these might be possible

WON'T - we want to be explicit about certain things that people might expect us to deliver but we want to be clear we won't deliver

Which deliverables will fully or partially satisfy the requirement?


Requirement User / Owner MoSCoW Associated Objective/Deliverable (Ox/Dx.x)



Benefits management and realisation will be available on the ITI Sharepoint space.

Guidance (please remove)

The benefits that the deliverables will enable or act as a catalyst in making happen. These benefits may be immediate or may be realised after the project has closed.



Guidance (please remove)

Project will have these governance roles by default. Change as appropriate.

Portfolio Governance  

Role Name Division / Group / Team / College / School and Title
Project Sponsor    
Programme Owner    
Programme Manager    
Portfolio Owner    
Portfolio Manager    
Service Owner / Service Operations Manager    


Project Board


Guidance (please remove)

If the project has a project board for governance then list its composition here:


Role Name Division / Group / Team / College / School and Title
Senior User (may be the Executive)    
Senior Supplier    
Other board members    



Guidance (please remove)

For medium and large projects, state any tolerances for budget/timeline/scope beyond which point the Project Manager must request approval of the change from the Sponsor and / or the Board. For all projects, check if there is a tolerance on budget/timeline/quality for escalating to programme/portfolio manager.



Resources Skills and Cost


Guidance (please remove)

For small projects and project teams, state the estimated effort - build and test, project management.

For medium and large projects, an estimate can be added to the Estimation Log and revised as project progresses.

Also estimate costs of hardware, software, licenses, travel, other.


Priority and Funding

Guidance (please remove)

Check the Forward Look and Annual Plan on ITI Sharepoint to see the project's priority within programme and portfolio (and reflect this also on the project info section of the website). Confirm that we have funding for this project.



Project Team

Guidance (please remove)

The project team : who manages the team, lead and other technical people, business analysts, lead and other representatives, people in other areas of the University who will be involved in analysis, testing, acceptance and service handover.


Role Name Division / Group / Team / College / School and Title
Project Manager    
Technical Lead and other technicians    
Business Analyst    
Business Lead(s)    
Procurement Advisor    
Service Contact    
User(s) - who will help in analysis, testing and sign-offs    


Quality of Project and Deliverables / Key Project Milestones

Guidance (please remove)

The milestones are a key tool in ensuring that the project process itself is followed as set out by ITI, and that the product deliverables are to the required Quality.

Edit this template to list the key Milestones and who signs off on these milestones. Add milestones for Security, Accessibility,  UX, as required.

For medium and large projects, a project plan - MS Project, Gantt, or other - can be added to the Plan Log and revised as project progresses. The approach can be stated here.

You can also mention the approach the project is taking to set, measure and confirm the quality of the deliverables


Milestone Sign-Off means Date of Milestone Who signs-off (Accountability)

Start of Project

Project can begin, is in line with Programme and Portfolio priority, has resource

Add initial planning dates for milestones

Sponsor, Programme Manager

End of Planning

Project Brief, Plan, Estimated Budget, Risks, Communication Plan - all approved. Project has resource approved by section head for the estimated effort. Project has funding for effort for other costs.


Sponsor, PM, Programme Manager, Section Head(s)

End of Analysis quality and completeness of analysis   business analyst / business lead / senior user / PM
End of Design quality and completeness of design   technical lead / senior supplier/ business lead / senior user/ PM
End of UI Design quality of UI - to show we have designed an interface that is usable, accessible, promotes equality and diversity   technical lead / senior supplier/ business lead / senior user
End of Build quality and completeness of build   technical lead / senior supplier/ PM
Acceptance overall quality of deliverable, UAT has been passed, Intergation testing successful, all components technically checked  - fit for delivery to live service  

technical lead / senior supplier /business lead / senior user /business analyst /PM


Security QA deliverable satisifies security   Section Head
Branding QA for new, upgraded services, sign-off that branding guidelines for ISG, University, school/college has been followed by the project team  

PM / and as appropriate ...

UoE C&M, college C&M and (pending) ISG Branding Team

Design UI QA to show we have built an interface that is usable, accessible, promotes equality and diversity   Sponsor and Service Owner
EqIA For new services or services undergoing substantial change, there must be an Equality Impact Assessment completed, validated by equality office and deposited on eqia website   PM / Service Owner / Equality Officer
GDPR / PIA Check if your project needs to undergo a Privacy Impact Assessment   PM / Service Owner / CISO
GoCAB Set the appropriate date for informing GoCAB of the release/change to service   PM


Change to Service can proceed


Sponsor, PM

service owner/ service operations manager (helpline)

Handover to Support support can take over running of the Service   service owner/ service operations manager (helpline)


Project can close


Sponsor, PM



Guidance (please remove)

What are the key underlying assumptions for the project that underpin the planning? For example, that the requirements we have outlined are complete, that all our stakeholders have been identified, that the software we are using is ready and configured, that we have a ready to use TEST environment.



Guidance (please remove)

Are there constraints on this project? For example, specialist skills are needed, having to deliver in certain windows through the academic year, we need to share a TEST environment with other developers?



Guidance (please remove)

The project manager will ensure that the project team will review the risk log at every team meeting, and project owners update their risks at least once a month or more as appropriate to the project.



Guidance (please remove)

The project manager will ensure all changes to cost/timeline/scope must be recorded in the issue log, and reflected in miletones log, budget and estimations, and the project Scope Change log.


Previous Lessons Learned

Guidance (please remove)

Does the ITI Lessons Learned (see ITI Projects Sharepoint) indicate any issues or risks from previous projects? Is any other previous experience pertinent?



Guidance (please remove)

Are there other projects or work that this project is dependent on to start or possibly interact with at a later stage - or vice-versa that depend on this project.

Are we depending on certain events to take place?

Are we dependent on suppliers, or product releases?





Guidance (please remove)

For projects with an array of external stakeholders, a Communication Plan can be created and made available on the ITI Sharepoint space if preferred.

Also confirm that :

Project Sponsor and Project Manager meeting schedule has been agreed with Sponsor.

Project Team meetings schedule has been arranged (these may be combined with Sponsor meetings).


Check the ITI Annual Planning Engagement with Stakeholders on ITI Sharepoint to see the level of engagement our partners expect for your project

Check the ITI Forward Look to see if your project wil be using the Major Governance Toolkit.



Run / Grow / Transform

Guidance (please remove)

Which activity does the project contribute to? The project could be one or more of R/G/T


Alignment to Strategy 2030 



Teaching and Learning


Social and Civic Responsibility




Project Sponsor – Project Responsibilities

The sign-off milestones are associated with specific responsibilities of the Sponsor role .

Guidance (please remove)

This sets out the Sponsor responsibilities on this project - please review and amend as appropriate for this project and agree with Sponsor

Start of project – Explicitly Included in the Initiation Milestones Sign-Off

  1. Negotiates and confirms funding for the project
  2. Ensures the project is in line with organisational strategy and priorities
  3. Chairs the project board, appoints its members and ensures they are effective
  4. Advises the project manager of protocols, political risks, issues and sensitivities
  5. Makes the project visible within the organisation  

End of Planning – Explicitly Included in the Planning Milestone Sign-Off

  1. Works with the project manager to develop the Project Brief
  2. Ensures a realistic project plan is produced
  3. Sets tolerance levels for escalation to themselves and to the project board
  4. Ensures that project team have representation and engagement from users and suppliers
  5. Helps identify Stakeholders
  6. Approves Communication Plan
  7. Agrees on frequency of meetings with Project Manager
  8. Agrees of frequency of meetings with Project Team
  9. Agrees on milestones and who signs-off


Execution – ongoing

  1. Provides strategic direction and guidance to the project manager as directed by the Board
  2. Approves changes to plans, priorities, deliverables, schedule
  3. Encourages stakeholder involvement and maintains their ongoing commitment
  4. Chief risk taker
  5. Makes go/no-go decisions
  6. Communicates change in organisational structure, priorities, business benefits or funding
  7. Helps the project manager in conflict resolution
  8. Helps resolve inter project boundary issues
  9. Gains agreement among stakeholders when differences of opinion occur
  10. Assists the project by exerting organisational authority and the ability to influence  

Delivery – Explicitly Included in the Delivery Sign-Off

  1. Ensures that Service is ready for change


Closure - Explicitly Included in the Closure Milestone Sign-Off


  1. Helps with publicity for the change delivered
  2. Ensure that benefits will be managed, measured and realised post-project
  3. Evaluates the project’s success upon completion

Project Info

Research Services Network Security Review
ITI - Research Services (RSS)
Management Office
Project Manager
Chris Walker
Project Sponsor
David Fergusson
Current Stage
Project Classification
Start Date
Planning Date
Delivery Date
Close Date
Overall Priority