Organising, planning and scheduling software projects. Software management distinctions



Similar documents
Project management. Organizing, planning and scheduling software projects

Project management. Organizing, planning and scheduling software projects. Objectives. Chapter 3. Chapter 3 Project Management. Learning Objective

Organizing, planning and scheduling software projects

Project management. Objectives. Topics covered. Organizing, planning and scheduling software projects DISCUSSION

Project management. Organising, planning and scheduling software projects. Ian Sommerville 2000 Software Engineering, 6th edition.

Project management. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 1

Project management: an SE Perspective

Software Engineering. Project Management. Based on Software Engineering, 7 th Edition by Ian Sommerville

Project Management. Massimo Felici Room 1402, JCMB, KB

Business Idea Development Product production Services. Development Project. Software project management

Software Project Management. Software Engineering SW Project Management Slide 1

How To Manage Project Management

Chap. 4 Project management. Organising, planning and scheduling software projects

Project management. Objectives

4. Software Project Management

LECTURE 5: SOFTWARE PROJECT MANAGEMENT. Software Engineering Mike Wooldridge

Software Project Management

(Refer Slide Time: 01:52)

Project Planning. COSC345 Lecture 3 Slides: Andrew Trotman Dramatic presentation: Richard O Keefe. Software Engineering 2013

Software Engineering. What is a system?

Software Engineering G Session 12 - Main Theme Risk Management in Software Engineering Projects. Dr. Jean-Claude Franchitti

Software Project Management

Software Project Planning. CITS1220 Software Engineering

CHAPTER 24 SOFTWARE PROJECT SCHEDULING. Overview

Project Management Guidelines

Introduction to Software Engineering (2+1 SWS) Winter Term 2009 / 2010 Dr. Michael Eichberg Vertretungsprofessur Software Engineering Department of

6. Software Lifecycle Models. A software lifecycle model is a standardised format for planning organising, and running a new development project.

Guidelines: Project Schedule Project Management Office (PMO)

Project Management Planning

Introduction to Software Engineering. 9. Project Management

Project Management Step Wise. Sunday, 4 November 12

Basic Project Management & Planning

LECTURE 1. SYSTEMS DEVELOPMENT

Project Management. References: Text, Chapter 16 (and 1 thru 3) Most introductory management books. Get organized!

Software Project Models

Contents. Today Project Management. Project Management. Last Time - Software Development Processes. What is Project Management?

THE PROJECT MANAGEMENT KNOWLEDGE AREAS

Génie Logiciel et Gestion de Projets. Project Management

PROJECT SCHEDULING AND TRACKING

Project Management Guidebook

Génie Logiciel et Gestion de Projets. Project Management

Template for IT Project Plan. Template for IT Project Plan. [Project Acronym and Name]

Time Management. Part 2 Work Breakdown Structure (WBS) Review. Richard Boser

Process Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology

OPERATIONAL PROJECT MANAGEMENT (USING MS PROJECT)

SOFTWARE DEVELOPMENT PLAN

Software Process Models. Xin Feng

2.1 The RAD life cycle composes of four stages:

BUSINESS OCR LEVEL 3 CAMBRIDGE TECHNICAL. Cambridge TECHNICALS BUSINESS PROJECT MANAGEMENT CERTIFICATE/DIPLOMA IN K/502/5459 LEVEL 3 UNIT 18

Supporting Workflow Overview. CSC532 Fall06

Input, Output and Tools of all Processes

MIS 424 COURSE OUTLINE

ICT Project Management. Software Project Planning By J. Ogutu

Chapter 7 - Project Scheduling and Tracking

Retained Fire Fighters Union. Introduction to PRINCE2 Project Management

Goals of the Unit. spm adolfo villafiorita - introduction to software project management

Software Engineering UNIT -1 OVERVIEW

Prepared for: Prepared by:

Mastering Microsoft Project 2010

The Plan s Journey From Scope to WBS to Schedule

IV. Software Lifecycles

Change Management Tool kit Project Management Guidelines

How to Write a Software Process Procedures and Policy Manual for YOUR COMPANY

Introduction and Overview

How to use Microsoft Project? Basic Training to Help You during the BYI challenge

A methodology for knowledge based project management (Work in progress)

Software Project Management Plan (SPMP)

Agile Projects 7. Agile Project Management 21

Analysis Design Coding Testing. Figure 3.1: Basic Waterfall Model

Information Technology Project Management (ITPM)

Software Engineering. Software Development Process Models. Lecturer: Giuseppe Santucci

Best Practices Statement Project Management. Best Practices for Managing State Information Technology Projects

Involve-Project Manager

NFSA Project Management Guidelines

PRINCE2:2009 Glossary of Terms (English)

Chapter 9 Computer Scheduling Projects should be scheduled one byte at a time

How To Model Software Development Life Cycle Models

PROJECT MANAGEMENT METHODOLOGY SECTION 3 -- PLANNING PHASE

Unit 1 Learning Objectives

<Company Name> <Project Name> Software Development Plan. Version <1.0>

NE-50413B Mastering Microsoft Project 2010

CSE 435 Software Engineering. Sept 16, 2015

Object-Oriented Analysis. with the Unified Process. John W. Satzinger Southwest Missouri State University. Robert B. Jackson Brigham Young University

Software Engineering. Requirements elicitation - Facts finding. Software Engineering Requirements Elicitation Slide 1

COURSE CODE : 4072 COURSE CATEGORY : A PERIODS / WEEK : 4 PERIODS / SEMESTER : 72 CREDITS : 4

Establishing Great Software Development Process(es) for Your Organization. By Dale Mayes

SYSTEMS ANALYSIS AND DESIGN DO NOT COPY

CMSC 435: Software Engineering Course overview. Topics covered today

2. Analysis, Design and Implementation

Basic Concepts. Project Scheduling and Tracking. Why are Projects Late? Relationship between People and Effort

Service Blueprinting HANDBOOK Maik Seyring Dr. Utz Dornberger MBA Alfredo Suvelza MBA Trevor Byrnes

Microsoft Project 2010

Project management tutorial

ME 4054W: SENIOR DESIGN PROJECTS

Development and Acquisition D&A

ICS 121 Lecture Notes Spring Quarter 96

Short Guides to IDA Quality Assurance Guidelines. Development and Validation Phase. Issue 2.0

Introduction to Software Engineering. Adopted from Software Engineering, by Ian Sommerville

Leaving Certificate Technology. Project Management. Teacher Notes

Design Document Version 0.0

Transcription:

Project management Organising, planning and scheduling software projects Software management distinctions The product is intangible The product is uniquely flexible Software engineering is not recognized as an engineering discipline with the same status as mechanical, electrical engineering, etc. The software development process is not standardised Most software projects are one-off projects (1 回 限 り)

Management activities ( 管 理 者 の 仕 事 ) Proposal writing ( 提 案 書 を 書 く) Project costing ( 費 用 見 積 り) Project planning and scheduling ( 計 画 スケジュール) Project monitoring and reviews ( 監 視 とレビュー) Personnel selection and evaluation ( 要 員 確 保 と 評 価 ) Report writing and presentations ( 報 告 作 成 とプレゼンテーション) Project staffing May not be possible to appoint the ideal people to work on a project Project budget may not allow for the use of highly-paid staff Staff with the appropriate experience may not be available An organisation may wish to develop employee skills on a software project

Types of project plan Plan Quality plan ( 品 質 計 画 ) Validation plan ( 検 証 計 画 ) Configuration management plan ( 構 成 管 理 計 画 ) Maintenance plan ( 保 守 計 画 ) Staff development plan ( 訓 練 計 画 ). Description Describes the quality procedures and standards that will be used in a project. Describes the approach, resources and schedule used for system validation. Describes the configuration management procedures and structures to be used. Predicts the maintenance requirements of the system, maintenance costs and effort required. Describes how the skills and experience of the project team members will be developed. Project planning process Establish the project constraints Make initial assessments of the project parameters Define project milestones and deliverables while project has not been completed or canceled loop Draw up project schedule Initiate activities according to schedule Wait (for a while) Review project progress Revise estimates of project parameters Update the project schedule Re-negotiate project constraints and deliverables if (problems arise) then Initiate technical review and possible revision end if end loop

Project plan structure Introduction Project organisation Risk analysis Hardware and software resource requirements Work breakdown Project schedule Monitoring and reporting mechanisms Activity organization Activities in a project should be organised to produce tangible outputs for management to judge progress Milestones (マイルストーン) are the end-point of a process activity Deliverables ( 配 布 成 果 物 ) are project results delivered to customers The waterfall process allows for the straightforward definition of progress milestones

Milestones and deliverables ACTIVITIES Feasibility study Requirements analysis Prototype development Design study Requirements specification Feasibility study Requirements definition Evaluation report Architectural design Requirements specification MILESTONES Scheduling problems Estimating the difficulty of problems and hence the cost of developing a solution is hard Productivity is not proportional to the number of people working on a task Adding people to a late project makes it later because of communication overheads The unexpected always happens. Always allow contingency in planning

Task durations and dependencies Task Duration Dependencies (days) T1 8 T2 15 T3 15 T1 T4 10 T5 10 T2, T4 T6 5 T1, T2 T7 20 T1 T8 25 T4 T9 15 T3, T6 T10 15 T5, T7 T11 7 T9 T12 10 T11 Activity network 4/7/94 start 8 days T1 15 days T2 14/7/94 15 days M1 T3 5 d ays 25/7/94 T6 M3 20 days T7 4/8/94 M4 15 days T9 25/8/94 M6 7 days T11 10 days 25/7/94 10 days 11/8/94 5/9/94 T4 M2 T5 M7 15 days M8 18/7/94 T10 10 days M5 T12 25 days T8 Finish 19/9/94

Activity timeline 4/7 11/7 18/7 25/7 1/8 8/8 15/8 22/8 29/8 5/9 12/9 19/9 Start T4 T1 T2 M1 T7 T3 M5 T8 M3 M2 T6 T5 T9 M4 M7 T10 T1 1 M6 T12 M8 Finish Staff allocation 4/7 11/7 18/7 25/ 1/8 8/8 15/8 22/8 29/8 5/9 12/9 19/9 Fred T4 T8 T11 T12 Jane T1 T3 T9 Anne T2 T6 T10 Jim T7 Mary T5

Key points Good project management is essential for project success The intangible nature of software causes problems for management Managers have diverse roles but their most significant activities are planning, estimating and scheduling Planning and estimating are iterative processes which continue throughout the course of a project Key points A project milestone is a predictable state where some formal report of progress is presented to management. Activity charts and bar charts are graphical representations of a project schedule