👉 low to medium level of complexity
👉 current expertise required
👉 estimated workload > 25 days/man (M/D)
👉 high level of complexity
👉 rare expertise required
This categorisation implies:
- the registration of the project/micro-project request by the IT Project Management Office (PMO) to the Institutional IT Project Portfolio. Following this registration, the PMO communicates by email the project identifier (project_id) which formalizes the project request;
- presentation of the project request to the IT Project Framing Committee by the future Project Leader or by the Sponsor;
- the registration by the future Project Leader or by the Sponsor of the Project Mandate which allows to confirm (or not) the categorization proposed by the IT Demand Mgmt Committee;
- regarding the projects:
- regarding the micro-projects:
- the drafting of the specifications which will allow to define more precisely the workload, the required expertise, the budget, the planning & the risks;
- Prioritization by the entity in charge of the implementation (e.g. IT Department, Faculty...);
- In both cases:
It is important to differentiate between the notion of a project/micro-project request and the notion of a project/micro-project.
A project/micro-project request only becomes a project/micro-project once the Project Management Office (PMO) has given the green light. The PMO's task is to ensure that there are no conflicts in terms of team capacity planning or that these conflicts are resolved through prioritization.