Projmgmt-1/22 DePaul University Project Management I - Realistic Scheduling Instructor: David A. Lash.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

TIME MANAGEMENT 641 Topic 03 Activity Sequencing.
Work Breakdown Structures
Software Quality Assurance Plan
Advanced Project Management - CPH
Managing Project Scheduling. What is Project Scheduling? The process of: – defining project activities – determining their sequence – estimating their.
Introduction to Project Management Chapter 6 Managing Project Scheduling Information Systems Project Management: A Process and Team Approach, 1e Fuller/Valacich/George.
Work Breakdown Structure.
Degree and Graduation Seminar Scope Management
Project Time Management
Importance of Project Schedules
Projmgmt-1/17 DePaul University Project Management I - Work Breakdown Structure Instructor: David A. Lash.
Projmgmt-1/33 DePaul University Project Management I - Risk Management Instructor: David A. Lash.
Projmgmt-1/14 DePaul University Project Management I - Realistic Scheduling Instructor: David A. Lash.
Project Time Management
Project Time Management
Chapter 5: Project Scope Management
Engineering Design Development. Turner College and Career High School.
1 CSc Senior Project Software Testing. 2 Preface “The amount of required study of testing techniques is trivial – a few hours over the course of.
HIT241 - TIME MANAGEMENT Introduction
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Project Management An overview. What is a Project A temporary job to accomplish a specific task A temporary job to accomplish a specific task Attributes.
Software Project Management Task Sequencing Activity Sequencing Concepts PERT charts Critical Path Analysis.
S/W Project Management
Typical Software Documents with an emphasis on writing proposals.
Software Testing Lifecycle Practice
5.1 Principles of Project Management. So what is Project Management? Definition: Is the process of planning, organizing, and managing tasks and resources.
Chapter 6: Project Time Management
~ pertemuan 6 ~ Oleh: Ir. Abdul Hayat, MTI 03-Apr-2009 [Abdul Hayat, Project Time Management, Semester Genap 2008/2009] 1 PROJECT TIME MANAGEMENT.
Quick Recap. Work Breakdown Structure (WBS): Set of activities to do (“use cases”) Formats of WBS Risk associated WBS Approaches for WBS Dependency Graph:
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project Planning.
Successful IT Projects slides © 2007 Darren Dalcher & Lindsey Brodie Successful IT Projects By Darren Dalcher & Lindsey Brodie
Welcome to Session 4 – Project Management Process Overview (continued) Instructor:Phyllis Sweeney Instructor: Phyllis Sweeney Project Management Certificate.
Information Technology Project Management, Seventh Edition Note: See the text itself for full citations.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
IT Project Management, Third Edition Chapter 6 1 Chapter 3: Project Time Management.
Lecture 7. Review of Lecture 6 Project Scheduling: The process of defining project activities, determining their sequence, estimating their duration Scheduling.
1 Determining Feasibility and Managing Analysis and Design Activities.
Managing Project Resources. Project Resources Human Resources Project stakeholders: – Customers – Project team members – Support staff Systems analyst.
Copyright 2008 Introduction to Project Management, Second Edition 2  Many people have heard the following sayings: ◦ If you fail to plan, you plan to.
Lecture 6. Review of Lecture 5 Company strategic planning: mission and objective statements and competitive strategy. Planning Methods: Top-down, Bottom-up.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
1IT Project Management, Third Edition Chapter 6 Chapter 6: Project Time Management.
Collecting requirements – Different methods Defining scope – Estimates for all resources Creating the WBS – Different approaches Verifying scope – Formal.
Project Management All projects need to be “managed” –Cost (people-effort, tools, education, etc.) –schedule –deliverables and “associated” characteristics.
PRJ566 Project Planning & Management Work Breakdown Structure.
Copyright 2006 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Project Management Operations Management - 5 th Edition Chapter.
Project Management Theory. Planning a Project Identify the problems and inefficiency of system. – Design brief Design brief: A statement that contains.
Copyright 2003 Lynn Frock & Company. All Rights Reserved. 1 Five Ways to Build a Microsoft Project Schedule Lynn Frock, PMP Phone
Richard Fisher 1 The University of Texas at Dallas Project Management Richard Fisher The University of Texas at Dallas.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Project Management Inspections and Reviews 1 February.
Project Time Management
McGraw-Hill/Irwin Copyright © 2011 The McGraw-Hill Companies, All Rights Reserved Chapter 10 Projects.
 Project Time Management includes the processes required to accomplish timely completion of the project  Part of Triple Constraints  Managers often.
Creating the Work Breakdown Structure. INFO 638Lecture #22 WBS The goal of the project should be accomplished when all tasks in the WBS are completed.
Scheduling and Budgeting Engineers Without Frontiers CEE 402.
SOFTWARE PROJECT MANAGEMENT
Project Time Management Based on PMBOK 5 th Edition Abdelrahman Sheta, PMP,ITIL 1PMP - Project Time Managementfacebook.com/Sheta.Page.
Project Management Planning and Scheduling. “Failing to plan is planning to fail” by J. Hinze, Construction Planning and Scheduling Planning: “what” is.
© 2008 Prentice Hall6-1 Introduction to Project Management Chapter 6 Managing Project Scheduling Information Systems Project Management: A Process and.
Project Management MGT 30725
Chapter 3 Managing the Information Systems Project
CHAPTER 6 PROJECT TIME MANAGEMENT
Project Time Management
Importance of Project Schedules
Software Testing Lifecycle Practice
CHAPTER 6 PROJECT TIME MANAGEMENT
Chapter 3 Managing the Information Systems Project
Presentation transcript:

Projmgmt-1/22 DePaul University Project Management I - Realistic Scheduling Instructor: David A. Lash

Projmgmt-2/22 Some Aspects Of Scheduling u A realistic schedule: – Has detailed knowledge of work to be done – Has tasks sequenced in correct order. – Accounts for external constraints beyond team control – Can be accomplished on time with resources available – Accounts for project’s objects (e.g., milestones)

Projmgmt-3/22

Projmgmt-4/22 Identify Task Relationships u WBS identified the major tasks u Need to develop how the tasks are related u Need to develop the “proper” sequence – For example, u cannot paint a fence until the fence is built!! u Cannot build the fence until the material are obtained!

Projmgmt-5/22 Home Landscape Project 1.0 Design home landscape 2.0 Put in Lawn 2.1 Acquire lawn material 2.2 Install Sprinkler System Identify sprinkler locations dig trenches Install pipe and hardware Cover Sprinkler system 2.3 Plant Grass Remove Debris Prepare soil (e.g., fertilize) plant lawn seed 2.4 Plant Shrubs 3.0 Build Fence 3.1 Acquire Fence material 3.2 Construct the fence Mark fence line Install posts Install fencing and gates Paint/stain fence Sample WBS From Book What is proper ordering for these? Any in parallel?

Projmgmt-6/22 Sequencing Tasks Either Task 1 or 2 can go first (Can be concurrent) Task 5 can't start until 2 Task 3 needs 1 & 2 Task 4 needs 3 (therefore needs 1 & 2 too!)

Projmgmt-7/22 2 Rules When Graphing Task Relationships u Define task relationships ONLY between work packages – Don’t graph the summary tasks, in general it is too high level u Graph to reflect sequence relationship – not the resource constraints – these graphs are intended to show the sequence constraints u Use Network Chart (sometimes call PERT) – (Program Evaluation and Review Technique)

Projmgmt-8/22 Correct Network Diagram Mile- stone (diamond) 2 con- current paths

Projmgmt-9/22 Incorrect Network Diagram u Common problem is removing redundant tasks for same resource u May not have resources to execute 4&5 concurrently but diagram should not reflect that yet. (only task sequence not resource constraints). diamond

Projmgmt-10/22 Setting Up Milestones u Milestones - significant events worth special tracking u Why track milestones? – Make network diagram easier to read – Can show input from an external dependency (E.g., government agency releases report) – Can represent significant events that aren’t tasks (e.g., receive progress payments) Milestones should be drawn as a diamond

Projmgmt-11/22

Projmgmt-12/22 Step 3: Estimating Work Packages u Bottom-up Estimating - estimate time duration of each work task – Include total elapsed time - u e.g., if takes 10 work days to install & 4 days to order, requires 14 days or u if requires 4 hours to make decision but 10 days to get meeting(s) set, then task takes 10 days or 11.

Projmgmt-13/22 Step 3: Estimating Work Packages u Concentrate on cost estimates (since they are usually a major constraint): – Cost estimates can be: u Labor Costs - amount of human effort. (e.g., 3 people 8 hrs/day = 72 hours). There may be skill or salary grades required. Each should be listed. u Equipment Estimates - Identify tools needed (e.g, cranes, software, machines, etc) u Materials Estimates - Any raw materials needed. (May be none) u Fixed-bid Contracts - Can be estimates from sub-contractor built into your project plan. u Will build estimates & identify resource for each task at a time

Projmgmt-14/22 A Task Estimate Summary Table

Projmgmt-15/22 A Task Estimate Summary Table

Projmgmt-16/22 Task Estimates “Fully Define” Resources u Include header descriptors of Task Description, Exit Criteria, Key Requirements, Assumption, Duration, Materials. For example, – Task Description - Count number of salmon during a 40-day salmon-run – Key Requirements - Error rate 5 Cms counted. – Exit Criteria - A report completed that describes the methods and shows results in tabular format – Assumption - The federal agency dictates the length of the study and specifies output format. – Duration - 40-days. – Materials - none – Labor & Equipment Table Type Aver Use Total Salmon Spec 400hrs Field Tech 800hrs Truck 1 all day 40 day

Projmgmt-17/22 Task Estimates “Fully Define” Resources u Task Description - A good non-ambiguous description of the task. Should be clear enough such that 2-3 people who read the description can understand task. u Exit Criteria - A statement of how to determine when the task is done. Providing this detail helps estimators nail down quality levels and review requirements. u Key Requirements - Summarize key requirements that will be required of the task. Define any quality specifications needed. Define some deliverables s of what task will accomplish. u Assumption - Define any resource or task assumptions made in the task. For example, task may assume use of a specialized tool for productivity.

Projmgmt-18/22 Task Estimates “Fully Define” Resources u Duration - Total elapsed time in hours/days to complete task. u Materials - Define special equipment and tools required for the task. u Task and Equipment Table - For each resource type include the type, average use and total time required. Note: it also makes sense to include a description or notes for each. Type Average Total Notes Salmon Special 400 Hrs Need outside consultant help. Beyond our area of expertise. u Other - Include any other items that may help define tasks and increase accuracy & clarity of estimates.

Projmgmt-19/22 Productivity and Task Duration u On some tasks adding people can reduce the task lengths – E.g., adding people removing debris from existing lawn. u On other tasks, adding people can negatively affect task duration – E.g., Adding a systems analyst to a task might decrease the duration by only 80% but increase costs. u When asking individuals to estimate, it is best to give them some criteria for estimation. For example, best case, worst case, and average case. – Consider reviewing their estimates as a matter of standard operation

Projmgmt-20/22 Example Work Package Estimate: Software Upgrade (Page 130) u Task: Upgrade software on 20 workstations u Exit Criteria - End user signs a completion of work form and fills out survey. u Description: Requires about – 2 hours install per machine – 1 hour testing per machine – only 1 person at a time can work on machine u First Estimate: 5 Days & 20 software license – Computer Tech - 1 tech x 8 hrs/ day - 40 hrs – Tester tech - 1 tech x 4 hrs/day - 20 hrs u Second Estimate: 2 Days & 20 softw license – Computer Tech - 2 tech x 10 hrs/ day - 40 hrs – Tester tech - 1 tech x 10 hrs/day - 20 hrs

Projmgmt-21/22 Example Work Package Estimate: System Design Activity (Page 132) u Task: Systems analyst works on 3 different projects including this subsystem design task. – First Estimate: No Materials - 40 Days u Systems analyst hrs/day 100 hrs u Assumption: Each work on 3 projects at once – Second Estimate: No Materials - 30 Days u Systems analyst hrs/day 150 hrs u Assumption: 2 will work concurrently (but both have 2 other projects) – Third Estimate: No Materials - 10 Days u Systems analyst - 8 hrs/day 80 hrs u Assumption: 1 work on this project only (with no other projects during the time)

Projmgmt-22/22