IS 556 Project Management David A Lash 630

IS 556 Project Management David A. Lash 630. 979. 5940 [email protected]. depaul. edu Week 4 – Readings: On Time Within Budget Ch. 11 Case: Timberjack Parts IS 556 Fall 2003 David Lash 1

Objectives z Project Plan z Work Breakdown Structure z Pert Chart z Gannt Chart z Dealing with Human Resources CS 556 - Winter David Lash 2

Project Plan z. One of the first Formal documents produced z. Includes: y. How project will proceed y. What resources are needed y. How risk will be used and managed z. Ensures planning of project activities, sequences and ywhat equipment and staff is needed and when? y. What activities and who will do them? y. What contingency plans z. Contents depends on project size/complexity 3 CS 556 - Winter David Lash

Project Plan - Page 243 CS 556 - Winter David Lash 4

Scheduled Activities and Milestones z. Project schedule is list of activities, when started and end. y. First step WBS - Break down activities into work tasks y. Breakdown all tasks into x. Start with listing the activities x. Break down to task level y. Will want to eventually define: x. Activity ID and Activity name x. Description x. Start & End date x. Dependencies - what other task this on depends on. x. Assignment - who is doing this item 5 CS 556 - Winter David Lash

3 Steps to WBS Development First got to figure out all tasks needed 1. Begin at The Top 2. Name all tasks needed to produce deliverables 3. Organizing the WBS (there are multiple ways to organize WBS. ) CS 556 - Winter David Lash 6

Step 1 - Begin at The Top z. List the major deliverables or high-level tasks from the scope z. Might also include intermediate deliverables (if major and not an end-product) Landscape Project Design Lawn Grass CS 556 - Winter David Lash Fence Shrubs 7

Step 2. Name all tasks needed to produce deliverables z For example put in grass might include ybuy dirt & seed yspread dirt yspread seed ywater for 2 weeks z. Don’t worry about order of activities yet. z. Need people closer to project tasks to help. z. Can be difficult in new situations y. E. g. , if never before executed a process or new technology use y. May need to call team together to develop strategies for WBS development (high level) 8 CS 556 - Winter David Lash

Step 3 - Organizing the WBS There are multiple ways to organize WBS. Some things to consider yorganize in a way closer to development process yorganize in a way easier to manage yorganize in way meaningful to sponsors. CS 556 - Winter David Lash 9

On to Sequencing Tasks • Once have a WBS need to figure out sequence of 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!) 10 CS 556 - Winter David Lash

Using a Network Diagram z. Network diagram y A logical representation of tasks that define the sequence of work x. For large projects can be many pages long y. Shows project path and sequences of tasks. y. Typically done before creating schedule. CS 556 - Winter David Lash 11

Conventions Used in a Network Diagram Source: The Complete Idiot’s Guide to Pro Management. Sunny and Kim Baker. CS 556 - Winter David Lash 12

Five Steps to Create a Network Diagram z z z List the tasks from the WBS Establish the interrelationships between tasks Identify Milestones Layout tasks and milestones on diagram Review the Network diagram logic CS 556 - Winter David Lash 13

Correct Network Diagram 2 concurrent paths Milestone (diamond) CS 556 - Winter David Lash 14

Incorrect Network Diagram diamond z z Common problem is removing redundant tasks for same resource May not have resources to execute 4&5 concurrently but diagram should not reflect that yet. (only task sequence not resource constraints). CS 556 - Winter David Lash 15

Setting Up Milestones z. Milestones - significant events worth special tracking z. Why track milestones? y. Make network diagram easier to read y. Can show input from an external dependency (E. g. , government agency releases report) y. Can represent significant events that aren’t tasks (e. g. , receive progress payments) Milestones should be drawn as a diamond CS 556 - Winter David Lash 16

Scheduled Activities and Milestones pp. 246 -247 Prjct manager usually has significant pressure to complete ilestones on time CS 556 - Winter David Lash 17

PERT Charts z. Program Evaluation and Review Technique (PERT) y. A type of network chart that uses circles and arrows x. Arrows represents tasks (activities) x. Circles represent events (end state for >=1 actives). x. Define Precedence network to plan sequence of activities x. Dependence – one activity cannot be completed (or begun) until another has been finished z. Like network diagrams defines precedence and activity sequence. CS 556 - Winter David Lash 18

PERT chart Components z. Start event = source z. End event = sink z. Link represents activity and time or effort z. Examples: Figures 11. 3, 11. 4 p. 252 CS 556 - Winter David Lash 19

Examples: Figures 11. 3, 11. 4 p. 252 CS 556 - Winter David Lash 20

Examples: Figures 11. 3, 11. 4 p. 252 Pert chart with critical path CS 556 - Winter David Lash 21

Critical Path z A sequence of events critical to successful completion of the project z PERT chart or project can have one or more critical paths z Shortening critical path can shorten project time y. Shortening a non-critical path item will NOT shorten project time z Can be used y. To represent resources and costs y. For analysis and simulation z May frequently need updating CS 556 - Winter David Lash 22

Schedules are not engraved in stone z. Milestone deliverable dates may need adjusting z. Schedule and sometimes budget may need adjusting at intervals CS 556 - Winter David Lash 23

Gantt Chart z Project development schedule z Start with high level z Add detail at lower levels z Good at showing y. Timing of activities y. Activity overlap z Not good at showing total amount of resources needed – just timeframe z Examples Figures 11. 1, 11. 2, pp. 249 -250 CS 556 - Winter David Lash 24

Gantt Chart - Figures 11. 1, 11. 2, pp. 249 -250 Does not indicate amount of resources required for each activity CS 556 - Winter David Lash 25

Complex Time Relationships Source: Complete Idiots Guide to Project Management. Pg 95. CS 556 - Winter David Lash 26

Development Team z. Scheduling people not the same thing as scheduling equipment z. Development team attributes includes y. Number of activities y. Intensity of activities y. Schedule/duration of activities z. Distribution varies with phases of project CS 556 - Winter David Lash 27

Development Team Size z. Varies over course of project z. Manager may do some functions when work is light z. Part time functions can sometimes be shared between projects y. Version control y. Library y. QA z. People might be shared with multiple projects. y. E. g. , test specialists CS 556 - Winter David Lash 28

Skills Needed on Team z. Varies by project and size ymight include programmers, QA specialists, test specialists, admin support, managers, technical writers, tool support, standard IT. z. Learning curve - often underestimated z. Training needs - sometimes can be hard to predict early y. E. g. , if programming language decision not made yet or technical platform requirements. CS 556 - Winter David Lash 29

Mythical Man Month (Work Month) z. How much work gets done during the time period allotted y. E. g. , how many actual work hours/day? How many actual days / month or year. z. What is the measure? y. Calendar y. Work y. Schedule z. Overhead when adding staff y. Law of diminishing returns (e. g, can 365 engineers reduce time to complete project from 1 year to 1 30 day? ) CS 556 - Winter David Lash

Scheduling Resources z. Space- may be critical especially for contract jobs. z. Equipment - e. g. , complex lab testing resources? z. Vendor/Subcontractor performance yhow control something not in your control yhow collect status? CS 556 - Winter David Lash 31

Schedule Monitoring z. Periodic - periodically PM gathers status and submits overall to management y. How does PM know if status is accurate (no developer fudging), how much CYA is occurring, how much you trust reports. x. E. g. , takes 50% of the time to complete last 105. z. When do you update project plan? y. May have to add activities, put in vacation/sick time, schedule slips, unexpected items z. PM needs to know enough about each status item to answer to management. CS 556 - Winter David Lash 32

Customer Expectations and Project Management z. Commitment- never commit to a schedule that doesn’t have a good chance of meeting z. Communicate - Your job is to keep the lines of communication open. Don’t expect customer to do it or you. z. Honesty is the best policy - Best not to try to “snow” customer on issues z. PM must keep a customer prospective, e. g. , easy-to-use, quality. CS 556 - Winter David Lash 33

Summary z Project Plan - what is it, what goes in one z Work Breakdown Structure - figuring out tasks, creating WBS, sequencing tasks. z Pert Chart z Gannt Chart z Dealing with Human Resources ydealing with teams, scheduling, training, customers. CS 556 - Winter David Lash 34