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

Slides:



Advertisements
Similar presentations
Project Quality Plans Gillian Sandilands Director of Quality
Advertisements

Targets for the individual and the organisation By Rachel, Claire, Kirsten and Natalie.
Computer Science Department
CS 501: Software Engineering Fall 2000 Lecture 2 The Software Process.
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 المحاضرة الثانية.
CIS-74 Computer Software Quality Assurance Systematic Software Testing Chapter 1: An Overview of the Testing Process.
1 Chapter 7 Lifecycle Planning. 2 Lifecycles - Introduction A lifecycle model is a prescriptive model of what should happen between the first glimmer.
Waterfall Model H.M.Shahzad MS(CS) from COMSATS Institute of Information Technology, Lahore.
Chapter 2 – Software Processes
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
ITIL: Service Transition
Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
SYSC System Analysis and Design
Cadle & Yeates Ch 5 Revised by Ivor Perry Sept Detailed Planning - 1.
The ISO 9002 Quality Assurance Management System
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 2 Software Processes.
Empowering Staff Through Institute Planning (ESTIP) Executive Workshop Institute Name: XXXXXX Presenter: XXXXXX Date: XXXXXX.
CS 501: Software Engineering
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Fundamentals of Information Systems, Second Edition
© The McGraw-Hill Companies, Software Project Management 4th Edition Managing contracts Chapter 10.
THE PRINCIPLES OF QUALITY MANAGEMENT. DEFINING QUALITY Good Appearance? High Price? The Best? Particular Specification? Not necessarily, but always: Fitness.
SOFTWARE QUALITY ASSURANCE Asst. Prof. Dr. Selim BAYRAKLI Maltepe University Faculty of Engineering SE 410.
Introduction to Computer Technology
Welcome ISO9001:2000 Foundation Workshop.
Software project management
Introduction to ISO New and modified requirements.
© The McGraw-Hill Companies, An Introduction Chapter 1 Software Project Management 4 th Edition Robert Hughes and Mike Cotterell.
Module CC3002 Post Implementation Issues Lecture for Week 1 AY 2013 Spring.
1 IT Project – Project Lifecycle, methodologies, tools, resources and other issues.
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Software Engineering Management Lecture 1 The Software Process.
Rapid Application Development. What is RAD……..?  Rapid Application Development (RAD) is a software development process.  first developed during the.
1 Activities covered by project management Feasibility study Is project technically feasible and worthwhile from a business point of view? Planning Only.
Lecture 1 :- Introduction Project Lifecycle Project Stakeholders Lecturer: Kawther Abas Monday: 3/4/1435 (8-11) 447CS – Management of Programming Projects.
 Project management is the organization and management of resources (i.e. people, information, tools and machines, materials, time, capital and energy)
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
An introduction to Project Management Ainsley Smith
Introduction to Project Management.  Explain what a project is?  Describe project management.  Understand project management framework.  Discuss the.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Topic 5 Initiating a project
Software Engineering Lecture # 1.
CC20O7N Software Engineering 1 CC2007N Software Engineering 1 Part 1 Introduction to Software Engineering.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
44222: Information Systems Development
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
Contract management 1. Acquiring software from external supplier This could be: a bespoke system - created specially for the customer off-the-shelf -
Introduction to Software Project Management Lecture1.
Presenter: Igna Visser Date: Wednesday, 18 March 2015
Information Systems Development
ITIL: Service Transition
Software Engineering Management
Workplace Projects.
SALES COORDINATOR Sydney
CS 389 – Software Engineering
Understand the principles of change management
Enterprise Content Management Owners Representative Contract Approval
Chapter 4 Systems Planning and Selection
Information Systems Development
Chapter 2 – Software Processes
Guidance notes for Project Manager
Introduction to Projects
CS310 Software Engineering Lecturer Dr.Doaa Sami
Presentation transcript:

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

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

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

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.

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.

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

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

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

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.

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.

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.

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

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)

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

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

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.

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.

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.

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.

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.

Thanks for your attention!