CS3100 Software Project Management: Monitoring & Control 1 Software Project Management Week 10: Project Monitoring & control Ian Blackman.

Slides:



Advertisements
Similar presentations
Applying evo to a project An Agile and EVO Workshop Based on the article Measuring Agile Value in Overload 89, by Ryan Shriver, and used with his permission.
Advertisements

Higher Business Management Budgets. What is a Budget? A document showing what the organisation predicts they are going to spend in the future Usually.
CS405 Project Management 1. Project Management “A well-planned project will take twice as long as originally expected; a poorly-planned project, three.
CS3500 Software Engineering Project Management (1) In 1986 one well-known software engineer (Tom DeMarco) made the simple but important observation: “You.
© The McGraw-Hill Companies, Software Project Management 4th Edition Monitoring and control Chapter 9.
University of Sunderland ENGM91 Unit 6 ENGM91 Project Execution Unit 6.
Monitoring and Control
SWE Introduction to Software Engineering
Project Workshops Project Planning 1. Project planning proper management is essential the responsibility of the student with the advice of supervisor.
Understanding and Managing Finance Presentation 2 Brief Version.
Nov. 13, 2003CS WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003.
1 F. Performance, Tracking & Reporting Part 3.4 of “3. Managerial process” of the software development plan template presented earlier consists of “ –3.4.
Section 4.0 Project Implementation. Factors that Ensure Success  Update the project plan  Stay within scope  Authorized change implementation  Providing.
Software Project Management
Project Management Basics
Chapter 9. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Chapter 3 Project Management
Information Technology Project Management By Denny Ganjar Purnama, MTI Universitas Pembangunan Jaya May 2014.
INFO 637Lecture #31 Software Engineering Process II Launching & Strategy INFO 637 Glenn Booker.
Chapter 3 : Managing the Information Systems Project.
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
Software Project Management
1 F. Performance, Tracking & Reporting Part 3.4 of “3. Managerial process” of the software development plan template presented earlier consists of “ –3.4.
1 Software Process Lecture Outline Nature of software projects Engineering approaches Software process A process step Characteristics of a good.
Chapter 11 Management Skills
University of Sunderland COM369 Unit 8 COM369 Project Monitoring and Control Unit 8.
T Project Review Magnificent Seven Project planning iteration
Project Management From Planning to Action A matter of communication.
COMP 208/214/215/216 Lecture 3 Planning. Planning is the key to a successful project It is doubly important when multiple people are involved Plans are.
Software Development Process and Management (or how to be officious and unpopular)
Copyright , Dennis J. Frailey CSE7315 – Software Project Management CSE7315 M29 - Version 9.01 SMU CSE 7315 Planning and Managing a Software Project.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Successfully recording Continuing Professional Development.
Lecture 3 Managing the Development Project SFDV Principles of Information Systems.
1 The University of California Berkeley Extension X470 Project Management Lisa Bausell.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
CS3100 S/w Project ManagementWeek 9: Earned value Sept ‘12 1 CS3100 Software Project Management November 22 nd 2012 Week 7: Earned value.
Project monitoring and Control
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Copyright 2008  Project management process groups progress from initiating activities to planning activities, executing activities, monitoring and controlling.
© 2001 Change Function Ltd USER ACCEPTANCE TESTING Is user acceptance testing of technology and / or processes a task within the project? If ‘Yes’: Will.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
CS 425/625 Software Engineering Project Management
Introducing Project Management Update December 2011.
1 Notes from
Information System Project Management Lecture Five
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
Project Management.
1 Chapter 3: Project Management Chapter 22 & 23 in Software Engineering Book.
Software Engineering REQUIREMENT ENGINEERING. Software Engineering Phases.
Project Time Management
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Evaluating EVM January 13, EVM Issues and Opportunities ▪ EVM Basics ▪ EVM Issues ▪ EVM ETC and EAC Calculations ▪ EVM Cost and Schedule Value Calculations.
Project Planning A2 ICT Edexcel. Learning Objective To look at ways of breaking down a project into manageable stages To produce a project plan with suitable.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
Extreme programming (XP) Advanced Software Engineering Dr Nuha El-Khalili.
Chapter 3 Project Management Parts of this presentation is extracted from Ian Sommerville’s slides located at
Team Assignment Importance of the assignment Assignment details Team Allocations Presentation details Submission Requirements Feed forward into Assignment.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
A Brief intro to Project Management What can it do for you
Project Communication, Tracking, and Reporting
Project Management Processes
Software engineering Lecture 21.
Resources BTEC National.
Organizations, Constraints & Projects
Monitoring and Reporting Project Progress
Project Management Processes
Introduction to Management
Presentation transcript:

CS3100 Software Project Management: Monitoring & Control 1 Software Project Management Week 10: Project Monitoring & control Ian Blackman

CS3100 Software Project Management: Monitoring & Control 2 learning outcome  To be able critically to discuss ways of monitoring and intervening in projects in order to ensure smooth progress towards a result that satisfies the customer by meeting the Triple Constraint.

CS3100 Software Project Management: Monitoring & Control 3 Once a project is running… Measure & assess progress Predict impact at end Analyse options Take action And that’s all there is to it! time budget quality With respect to the…… triple constraint More on this: Week 20 – Quality Week 25 – CRM

CS3100 Software Project Management: Monitoring & Control 4 Lets try to take this apart a little… Measure & assess progress Predict impact at end Analyse options Take action NB Cadle & Yeates and Hughes & Cotterell do it slightly differently What do we measure? time budget quality How long is it taking? How are we meeting schedule? How much time is being booked on timesheets? How long are the sub-contractors taking? How much progress have we really made? Which milestones have we met? What’s on staff activity logs? How much has been spent? What’s on the financial returns? How much is left in the bank or the job code?

CS3100 Software Project Management: Monitoring & Control 5 But you can’t measure everything! JI G B F C E D A C H time Start with measures on the Critical Path… Every now and then, dive deep into the project just to make sure everything is going the way you think it is. And then follow-up high impact risks (Week 19)

CS3100 Software Project Management: Monitoring & Control 6 Lets try to take this apart a little… Measure & assess progress Predict impact at end Analyse options Take action NB Cadle & Yeates and Hughes & Cotterell do it slightly differently How do we measure? time budget quality Time sheets Personal records Contracts of employment Lab books On-line internal notes Management accounts Bank statements Analysis of transactions Records of staff time Payroll! Sign-off with customer Internal progress reports Milestone negotiations Demonstrators, etc. The textbooks have some good ideas

CS3100 Software Project Management: Monitoring & Control 7 Moving on… Measure & assess progress Predict impact at end Analyse options Take action NB Cadle & Yeates and Hughes & Cotterell do it slightly differently time budget quality EV Earned value analysis enables you to estimate the predicted outturn on budget and schedule!

CS3100 Software Project Management: Monitoring & Control 8 … and on… Measure & assess progress Predict impact at end Analyse options Take action time budget quality See how different strategies impact upon the 3 constraints EV

CS3100 Software Project Management: Monitoring & Control 9 Back to our example from last week… weeks Task A Task B Task C Task D Task E £30,000 Task A A £20,000 time budget quality After 4 weeks: 1.Planned spend was £40,000 2.Actual spend was £30,000 3.Completed 1 task instead of 2 But what was the prediction?

CS3100 Software Project Management: Monitoring & Control 10 Earned Value Analysis told us weeks Task A Task B Task C Task D Task E Task A A To complete the project (& meet the customer’s expectations), Predictions: 1.Planned overspend of an extra 50% (£50,000) 2.Planned delay of an extra 100% (10 extra weeks) time budget quality So what are we going to do?

CS3100 Software Project Management: Monitoring & Control 11 Final picture weeks Task A Task B Task C Task D Task E £30,000 Task A A £20,000 Task B Task C Replace 2 low-cost coders with a top class coder who doubles productivity time budget quality

CS3100 Software Project Management: Monitoring & Control 12 What’s the comparison? time budget quality time budget quality What we would have guessed First review - prediction Later review - prediction time budget quality First review

CS3100 Software Project Management: Monitoring & Control 13 The next steps Measure & assess progress Predict impact at end Analyse options Take action Measurement and prediction can tell us if we have a problem or not… … but what can we do about it? Let’s break this down into three scenarios. Scenario 1: The project is on or ahead in terms of spend and schedule Scenario 2a: The project is slightly behind in terms of either spend or schedule. Scenario 2b: The project is in fairly or very serious trouble. Wks 16 & 17

CS3100 Software Project Management: Monitoring & Control 14 Scenario 1 Measure & assess progress Predict impact at end Analyse options Take action Your monitoring and predictions indicate that everything is fine or ahead of schedule Possible strategies and actions Do nothing! Reduce frequency of reviews, or supervision of staff Find out what is going right and try to get more of it! Praise or reward the team (ONLY) if you are confident… See whether the customer will pay for earlier delivery!

CS3100 Software Project Management: Monitoring & Control 15 Scenario 2a Measure & assess progress Predict impact at end Analyse options Take action Your monitoring and predictions indicate that you are predicting a minor overrun or overspend FIRST Try to work out what has really happened

CS3100 Software Project Management: Monitoring & Control 16 Scenario 2a Measure & assess progress Predict impact at end Analyse options Take action Your monitoring and predictions indicate that you are predicting a minor overrun or overspend Options: Do nothing! (provides a benchmark for everything else and sometimes works). Increase effort – more staff or overtime (speeds progress, costs extra). Modify team roles or skill mix (can be cost neutral and may create a big improvement) Encouragement and/or incentives

CS3100 Software Project Management: Monitoring & Control 17 Scenario 2a Measure & assess progress Predict impact at end Analyse options Take action Your monitoring and predictions indicate that you are predicting a minor overrun or overspend Options with the customer: Change phasing of the deliverables Negotiate changes in specification Negotiate for more time or money Other options: Subcontract some of the work

CS3100 Software Project Management: Monitoring & Control 18 Scenario 2b Measure & assess progress Predict impact at end Analyse options Take action Your monitoring and predictions indicate that you are in dire straights FIRST: REALLY find out what has gone wrong (THINKSPOT: Why is this difficult) More in week 16, Recovering from Failure 1 & week 17, Recovering from Failure 2

CS3100 Software Project Management: Monitoring & Control 19 Scenario 2b Measure & assess progress Predict impact at end Analyse options Take action Your monitoring and predictions indicate that you are dire straights Options are generally radical Re-plan project Re-organise team Bring in specialist help Major negotiations with internal management Major negotiations with customer

CS3100 Software Project Management: Monitoring & Control 20 Implementation issues Measure & assess progress Predict impact at end Analyse options Take action Communication & documentation Change control

CS3100 Software Project Management: Monitoring & Control 21 Documentation Lab books PDAs (make sure there is back-up) On-line activity logs You can use – if you structure it well WHAT? Factors leading to change Analysis and predictions Reasons for the change Risk associated with it People who objected Poor documentation will ruin your whole career Formal docu- ments later

CS3100 Software Project Management: Monitoring & Control 22 Everyone must be clear about why Manager(s) Communication & listening Measure & assess progress Predict impact at end Analyse options Take action Customer? You Team You have to take everyone with you You may need to draw them in earlier, too (weeks 16 & 20)

CS3100 Software Project Management: Monitoring & Control 23 Change management Forms: Will fit with the Company’s system Will capture the reasons and the results May record any deviations from the plan Usually require formal authorisation There are software systems: Document control Version control Change authorisation, etc. Thinkspot: why does this matter? Bid documents Meetings, minutes, etc Formal deliverables

CS3100 Software Project Management: Monitoring & Control 24 Summary  The basics are simple: measure, predict, analyse, act  We bring each of these to the Triple Constraint  EV helps to link the predicted quality/performance to time and budget  Keep a good set of records

CS3100 Software Project Management: Monitoring & Control 25 Next week  Guest Lecture