1. The Profile Of a Project G. Murat Taşbaşı SWE 523

2. Introduction We will examine a generic process model for a project that can be modified for a specific one. We will examine a generic process model for a project that can be modified for a specific one. Process model of a project is the stages that a project is involved during development. Process model of a project is the stages that a project is involved during development. 2 types of project: 2 types of project: ‘In House’ project: In house IT department ‘In House’ project: In house IT department Project with an external supplier Project with an external supplier

3. Introduction We focus on the projects with external suppliers. We focus on the projects with external suppliers. These kind of projects are carried out in one of the two ways: These kind of projects are carried out in one of the two ways: Fixed Price Fixed Price Time – and – materials Time – and – materials

4. Introduction Projects with external supplier are carried out in one of two ways: Projects with external supplier are carried out in one of two ways: Fixed Price Fixed Price Time and Materials Time and Materials Both has advanttages and disadvantages from the point of the customer and supplier. Both has advanttages and disadvantages from the point of the customer and supplier.

5. Introduction Fixed Price Method: The cost is agreed at the beginning. Fixed Price Method: The cost is agreed at the beginning. Time and Materials: Supplier is paid on the basis of his efford. Time and Materials: Supplier is paid on the basis of his efford.

6. Introduction What are the advantages and disadvantages of both method? Fixed Price Time and Materials

7. The Process Model All the project are different, but there are still some common elements All the project are different, but there are still some common elements We will develop a process model: We will develop a process model: A generic framework that is adaptable to many different projects

8. Pre- Project Work Project Start Up Development Stage Completion Stage Post - Project Work Operational Stage

9. The Process Model Not all elements of the model is appropriate for all projects, but it is still a good idea to use it as a cheklist, to be sure of that: Not all elements of the model is appropriate for all projects, but it is still a good idea to use it as a cheklist, to be sure of that: Nothing important is missed! Nothing important is missed! This process model is adaptive to any system development lifecycles such as waterfall or sprial or any other. This process model is adaptive to any system development lifecycles such as waterfall or sprial or any other.

10. Stage 1 of 6: Pre Project Work Customer prepares a specification of requirements. Customer prepares a specification of requirements. Make invitations to suppliers. Make invitations to suppliers. Suppliers respond, one of them is accepted. Suppliers respond, one of them is accepted. Negotiations start. Negotiations start.

11. Stage 2 of 6: Project Start Up Stage likely to involve 2 project managers: Stage likely to involve 2 project managers: Customer Project Manager: Responsible for whole project, to be successed. Likely to be called as ‘Project Director’ Customer Project Manager: Responsible for whole project, to be successed. Likely to be called as ‘Project Director’ Supplier Project Manager: Responsible for technical issues and deliveries mostly. Supplier Project Manager: Responsible for technical issues and deliveries mostly.

12. Stage 2 of 6: Project Start Up Outlines of this stage: Outlines of this stage: Product Initiation Document (PID) Product Initiation Document (PID) Project Plan Project Plan Quality Plan Quality Plan Risk Management Plan Risk Management Plan Project Organisation Project Organisation Project Administration Project Administration Resource Management Resource Management

13. Stage 2 of 6: Project Start Up Product Initiation Document (PID): Product Initiation Document (PID): Main decisions of the project: Objectives (Business and Project obj.) Objectives (Business and Project obj.) Scope (DOs And DON’Ts) Scope (DOs And DON’Ts) Constraints (Time, Cost, Resources) Constraints (Time, Cost, Resources) Authority(Administration) Authority(Administration) Resources(People, money, hardware, software) Resources(People, money, hardware, software)

14. Stage 3 of 6: Development Stage Most of the supplier’s work is carried out: Most of the supplier’s work is carried out: Mostly technical development. Mostly technical development. Development Stages: Development Stages: Requirements Definition Requirements Definition Design Design Implementation Implementation Integration & Testing Integration & Testing

15. Stage 3 of 6: Development Stage Deliveries of the Development Stage: Deliveries of the Development Stage: Requirements Specification Requirements Specification Technical Specifications Technical Specifications

16. Stage 4 of 6: Completion Stage Completion stage starts when the system is completed by the supplier and ready for system testing. Completion stage starts when the system is completed by the supplier and ready for system testing. Completed system is delivered to customer. Completed system is delivered to customer. Customer examines the system and checks if it satisfies the requirements. Customer examines the system and checks if it satisfies the requirements.

17. Stage 4 of 6: Completion Stage If planned, traning customer staff takes place in this stage. If planned, traning customer staff takes place in this stage. Acceptance testing is also done by the customer in this stage. Acceptance testing is also done by the customer in this stage. Delivery of the stage is a report called ‘Project Evaluation Report’, prepared by the Project Director, for the steering committee to benefit from his experience. Delivery of the stage is a report called ‘Project Evaluation Report’, prepared by the Project Director, for the steering committee to benefit from his experience.

18. Stage 5 of 6: Operational Stage The operational stage begins when the system is ‘on air’. The operational stage begins when the system is ‘on air’. Maintenance and enhancment is managed. Maintenance and enhancment is managed. Perhaps some changes in the business requirements are handled in this stage. Perhaps some changes in the business requirements are handled in this stage.

19. Stage 6 of 6: Post – Project Review Usually after about 6 months, a project review is done for addressing following issues: Usually after about 6 months, a project review is done for addressing following issues: Technical methods and standarts used, how effective they were etc. Technical methods and standarts used, how effective they were etc. How effective were the methods to address the project risks. How effective were the methods to address the project risks. Customer / supplier relationship issues. Customer / supplier relationship issues. Stakeholder management issues. Stakeholder management issues. Performence of the project and staff. Performence of the project and staff.

20. Stage 6 of 6: Post – Project Review The aim of the post project review IS NOT ‘hunt for the quilty’ BUT to capture the experience gained from the project.

21. Thanks for your attention!