Overview of Software Project Management cont Review – Class 6 Scheduling Tasks Project Management Activities CEN 4010 Class 8 – 09/22.

Slides:



Advertisements
Similar presentations
Project Management Techniques and tools Move mouse over arrow to enter presentation End Show.
Advertisements

Work Breakdown Structures
Project Management Process. Managing the Information Systems Project Focus of project management To ensure that information system projects meet customer.
Chapter 3 Managing the Information Systems Project
Managing the Information System Project
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
© 2005 by Prentice Hall Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Chapter 3 Managing the Information Systems Project
© 2008 by Prentice Hall 3-1 ITCS311 Systems Analysis and Design Dr. Taher Homeed Feb 2010 Department of Computer Science College of IT University of Bahrain.
CS3500 Software Engineering Project Management (1) In 1986 one well-known software engineer (Tom DeMarco) made the simple but important observation: “You.
CS3773 Software Engineering Lecture 8 Software Planning and Estimation.
Pair of Wires Box 1Box 2 A Communication Example "Two missile electrical boxes manufactured by different contractors were joined together by a pair of.
SWE Introduction to Software Engineering
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Project.
Project Management and Communication Represented by: Latifa Jaber Al-Ghafran.
Chapter 3 Managing the Information Systems Project
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 COMP201 Project Management.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 3, Project Organization and Communication.
Lean Six Sigma: Process Improvement Tools and Techniques Donna C. Summers © 2011 Pearson Higher Education, Upper Saddle River, NJ All Rights Reserved.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
Project planning. Software project management Informal definition of management – The art of getting work done through other people Software project management.
Project Management and Scheduling
CEN Fourth Lecture Introduction to Software Engineering (CEN-4010) Instructor: Masoud Sadjadi Project Organization.
Software Engineering Principles Chapter 3 From Software Engineering by I. Sommerville, Slide 1 project managementorganizing planning scheduling Learning.
Chapter 3 Project Management
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
Chapter 3 : Managing the Information Systems Project.
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
© 2005 by Prentice Hall 3-1 Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition.
 Probably the most time-consuming project management activity.  Continuous activity - Plans must be regularly revised.  Various different types of.
Managing the Design Process Project must  Accomplish the goals - scope  Be done within resources - spending  Be done on time - scheduling.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Concerned with activities involved in ensuring that software is delivered: on.
BSBPMG402A Apply Time Management Techniques 1 Apply Time Management Techniques Week 6 Project Time Processes – Part 2 C ertificate IV in Project Management.
Lecture 3 Scheduling CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
Software Project Management Lecture # 7. Outline Project Scheduling.
Lecture4 : Project planning Lecturer: Kawther Abas 447CS – Management of Programming Projects.
1 Chapter 5 Project management. 2 Project management : Is Organizing, planning and scheduling software projects.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Software Project Management
Lecture 3 Managing the Development Project SFDV Principles of Information Systems.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects.
Geog 469 GIS Workshop Project Management.
Project Management Yonsei University 2 nd Semester, 2012 Sanghyun Park.
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Software Engineering November 7, 2001 Project.
CS 425/625 Software Engineering Project Management
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Lecture 61 Project planning tool Lecture 62 Objectives Understand the reasons why projects sometimes fail Describe the different scheduling tools, including.
Chapter 3 Managing the Information Systems Project
The Goal: To Climb Above The Competition Copyright 2005: I Lead Projects, L.L.C. Course Description Project Process Workplates Project Process Workplates.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
Overview of Software Project Management Review – Class 5 UML diagrams cont Overview of Software Project Management - Communication CEN 4010 Class 6 – 09/15.
MADALINA CROITORU Software Engineering week 6 Madalina Croitoru IUT Montpellier.
BSBPMG503A Manage Project Time Manage Project Time Project Time Processes Part 2 Diploma of Project Management Qualification Code BSB51507 Unit Code.
Chapter 3 Project Management Parts of this presentation is extracted from Ian Sommerville’s slides located at
HNDIT23082 Lecture 10:Software Project Management
Chapter 3 Managing the Information Systems Project
Chapter 3, Project Organization and Communication
Management should be based on effective and thorough planning
Software Project Management
Business System Development
Chapter 2: Project Management
Software Project Management
Tools for Visualization
Information system analysis and design
Presentation transcript:

Overview of Software Project Management cont Review – Class 6 Scheduling Tasks Project Management Activities CEN 4010 Class 8 – 09/22

CEN 4010 Class /222 Overview of S/W Project Management Software engineering is a collaborative effort. Involves domain experts, analysts, designers, programmers, managers, etc.. Communication is essential! Definitions:  Communication mode - a type of information exchange that has defined objectives and scope.  Communication mechanism - a tool or procedure that can be used to transmit and receive information and support a communication mode.

CEN 4010 Class /223 Overview of S/W Project Manag. cont Modes of communication: Scheduled – Problem defn., client reviews, project reviews, inspection/walkthroughs, status review, brainstorming, releases, postmortem. Event-driven – Request for clarification, request for change, issue resolution. Go through Tables 3.1 and 3.2

CEN 4010 Class /224 Overview of S/W Project Manag. cont Mechanisms of communication: Synchronous – Hallway conversations, questionnaires and structured reviews, meetings, same-time, and different-place groupware. Asynchronous – , newsgroups, WWW, and Lotus Notes.

CEN 4010 Class /225 Overview of S/W Project Manag. cont Meetings: Primary facilitator – responsible for –organizing the meeting and guiding its execution. –writing the agenda describing the objective and the scope of the meeting. Minute taker – responsible for recording the meeting i.e. information for the diary. Time keeper – responsible for keeping track of time and notifying the facilitator if a discussion consumes more time than is allocated. A vote might be required to continue discussion or move on to the next point.

CEN 4010 Class /226 Tasks Recall, a task is an atomic unit of work that can be managed and that consumes resources. A task includes a description, a duration, and is assigned to a role. Tasks are related by dependencies. Tasks dependencies are relationships between individual tasks and time. Task constraints can be used to make sure a project is on schedule. See Table 3-4 and Figure 3-21 and 3-23

CEN 4010 Class /227 Schedule A task model contains the tasks, their dependencies, their constraints, and their planned duration. A schedule is the mapping of tasks onto time; Each task is assigned planned start and end times. Common notations:  Bar chart - Gantt charts  Activity network – PERT chart.

CEN 4010 Class /228 Schedule – Notation Gantt chart: is a bar chart where the horizontal axis represents time and the vertical axis the different tasks to be done. tasks are represented as bars whose length correspond to the planned duration of the task. PERT Chart: is an acyclic graph of tasks that represents a schedule. The minimum time required to finish the project can be estimated by considering the longest path (in days) in the activity graph (the critical path)

CEN 4010 Class /229 Schedule – Notation cont PERT Chart cont: tasks on the critical path are the most important. That is, a delay in any of these tasks will result in a delay in the overall project. Properties of Gantt and PERT charts: useful tools for planning a project and tracking its execution. models are only as good as the estimations they represent. accurate estimation usually comes with experience. can represent tasks to be done in parallel.

CEN 4010 Class /2210 Developing a Schedule 1.Identify tasks to be completed i.e. work breakdown 2.Estimate duration for each task in days. 3.State any dependencies between tasks. 4.Create a table with the above information. 5.Use information in table to create a Gantt or PERT chart.

CEN 4010 Class /2211 Developing a Schedule - Example TaskDuration (days)Dependencies T14 T26T1 T310 T412T2, T3 (M1) T58T3 T66T4, T5 (M2) T – represents a task M – represents a milestone

CEN 4010 Class /2212 Developing a Schedule – Example cont Task NameDurationSeptemberOctober Start T14 T26 M1 T310 T412 M2 T58 T66 Finish Gantt Chart

CEN 4010 Class /2213 Developing a Schedule – Example cont PERT Chart T1 Start 14d 09/18 09/21 T2 26d 09/2209/27 T3 310d 09/1809/27 M1 09/27 T4 412d 09/2210/09 T5 58d 09/2810/09 T6 66d 10/1010/15 Finish 10/15 M2 10/09 Critical path in green.Are there any other critical paths?

CEN 4010 Class /2214 Project Management Activities Proposal writing Project planning and scheduling Project costing Project monitoring and reviews Personnel selection and evaluation Report writing and presentations (Sommerville 2001)

CEN 4010 Class /2215 Project Plan Introduction – Briefly describes the project, and sets out the constraints. Project organization – how people on the team are organized i.e., roles. Risk analysis – describes possible risks e.g. h/w unavailability, requirements change, technology change etc. Hardware and software requirements – describes the h/w and s/w required to carry out the development.

CEN 4010 Class /2216 Project Plan cont Work breakdown – identification of milestones and deliverables. Project schedule – describes dependencies between activities, estimation of time required to reach each milestone and deliverable. In your report (Deliverable 1) there should be a section named “Project Plan” consisting of at least – introduction, project organization, h/w and s/w requirements, work breakdown and project schedule.