Organisation

Work/Task Breakdown

These stages will be undertaken:

• Planning: Create a project brief, Identify stakeholders, Identify project risks, estimate required resources, and define scope of the document.
• Development: 
  • Meet with Project Managers and ask 4 questions

• What do they see as their role in a procurement?
• What do they see as procurement office role?
• What do they see as business partner role?
• What do they see as other roles, e.g. other IS teams who evaluate? 
  • Write up the findings of the meetings, see if there is a consensus of opinion and produce a draft guidance document
  • Set up meetings with other IS teams
  • Update document, if needed, on basis of feedback
  • Share findings with procurement office and see if they agree
  • Update document, if needed, on basis of feedback
  • Decide where to publish document
  • Publish final document and communicate to stakeholders

• Delivery: Deliver a document, which clearly outlines the software procurement process and the allocation of responsibilities within the process.
• Closure: Reflect and report upon the success criteria stated in the brief and whether it has been fulfilled or not.

Resources, Skills and Costs

• Project Manager
• Project Managers with knowledge and experience of UoE Procurements
• Project Sponsor
• Procurement Office
• Existing wiki pages for procurement

Project Governance

• Regular catch-ups with project sponsor

Project Stakeholders

Project Estimations

csg014_estimate.xls

Attachment	Size
csg014_estimate.xls	52 KB