1. The Organisational Framework

2. Introduction to organisation structures  Functional organisation

3. Introduction to organisation structures  Pure project organisations

4. Introduction to organisation structures  Matrix organisations

5. Project roles and responsibilities  Generic project organisation and roles

6. Project roles and responsibilities  Sponsor : The person who is accountable to the business for the investment represented by the project and for the achievement of the project’s business objectives.  User : The person who will make use of the facilities of the system in their everyday work and is therefore the person most directly affected by the project.

7. Project roles and responsibilities  Project manager : The person who is appointed by the sponsor and is responsible for the management of the project on a day-to-day basis and for the achievement of the project objectives.  Risk manager : The person who will control the process of identifying, classifying and quantifying the risks.

8. Project roles and responsibilities  Quality manager : The person who will write the quality plan, develop the quality control procedures, check that these procedures are being followed and provide guidance to team members on quality-related issues.  Chief analyst : This is a senior and experienced business or systems analyst who will, under the direction of the project manager, lead the analysis work.

9. Project roles and responsibilities  Chief designer : The chief designer works under the direction of the project manager to control the work of the design team, and probably that of the programmers as well.  Database administrator : The database administrator will develop and enforce standards for the use of the database product, the naming and placement of data items and so on.

10. Project roles and responsibilities  Configuration librarian : The person who is responsible for operating the configuration control procedures.  Team leader : The team leader is typically in charge of a small group of, for example, programmers. They plan and direct work on a day-to-day basis and either review or organise reviews of the team members’ work.  Project office : A project office provides administrative support to the project manager.

11. Organising the roles  The steering committee : It is set up to control the development of a particular project – or perhaps a group of related projects – and has representation from the various interested parties.  The user group : Where there are several users for a planned system, it is sometimes useful to create a forum where they can come together and discuss their disparate requirements.

12. Organising the roles  The risk management committee : The function of this group would be to review the current status of risks, assign owners to the risks and check that the identified avoidance or mitigation actions are being carried out.

13. Programme and portfolio management

14. PRINCE2 organisation structure  PRINCE is an acronym for Projects in Controlled Environment.  PRINCE2 offers a number of features that are of benefit in the management of IS projects: - A defined management structure - A system of plans - A set of control procedures - A focus on product-based – that is deliverables-based – planning.

15. PRINCE2 organisation structure

16. Thank you for your participation