“80% of software projects fail”  Standish Report (1995) Standish Report 16.2% completed on-time and on-budget with all features and functions as initially.

Slides:



Advertisements
Similar presentations
Work Breakdown Structures
Advertisements

F O U R T H E D I T I O N Project Management © The McGraw-Hill Companies, Inc., 2003 supplement 3 DAVIS AQUILANO CHASE PowerPoint Presentation by Charlie.
Chapter 3 Managing the Information Systems Project
3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
© 2005 by Prentice Hall Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Defining activities – Activity list containing activity name, identifier, attributes, and brief description Sequencing activities – determining the dependencies.
© 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.
Systems Analysis and Design 9th Edition
Project Management: A Managerial Approach
2 Project Management  Management of work to develop and implement an innovation or change in an existing organization Examples: –New buildings –Weapon.
8 September ProcessWithin the Steps  Put together minimal solution Start with external commitments Introduce internal milestones  Focus on the.
11 October Project Management Discipline of planning, organizing, and managing resources to bring about the successful completion of specific project.
McGraw-Hill/Irwin ©2008 The McGraw-Hill Companies, All Rights Reserved SECTION 12.1 PROJECT MANAGEMENT.
Project Management 30 January. Odds and ends Tournament on the webweb In the newsnews.
Project Plan The Development Plan The project plan is one of the first formal documents produced by the project team. It describes  How the project will.
Project Time Management
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
Project Management March 9, 2001 Dr. Richard Chung Dept. Chemical & Materials Engineering San Jose State University.
Risk Management 25 January. What is due next week Website: Monday (send me URL as soon as you have it) Team rules: Monday Functional spec: Tuesday Project.
Chapter 11 - Project Management ME101 Dr. Nhut Tan Ho 1.
Prepared by: Michael Palazzo
Project Management and Scheduling
Managing Project Scheduling. What is Project Scheduling? The process of: – defining project activities – determining their sequence – estimating their.
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
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.
Chapter 3 : Managing the Information Systems Project.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Business Plug-In B15 Project Management.
BSBPMG503A Manage Project Time Project Time – Covers all aspects of time and duration, from how long it takes to complete one activity right through to.
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.
McGraw-Hill/Irwin © 2006 The McGraw-Hill Companies, Inc. All rights reserved. BUSINESS DRIVEN TECHNOLOGY Business Plug-In B10 Project Management.
(from Dr. Diane Pozeksky. “80% of software projects fail” Standish Report (1995) Standish Report 16.2% completed on-time and on-budget with all features.
CPAN 410 & GAME 410 Project Management
Appendix A Project Management: Process, Techniques, and Tools.
EGNR 300 Project Management Planning & Scheduling ENGR 300 Dept. of Computer Science and Engineering University of Bridgeport,
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
IT Project Management, Third Edition Chapter 6 1 Chapter 3: Project Time Management.
Project Management: A Managerial Approach
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 7 Project Manager’s Toolkit for Time Management.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Lecture 7. Review of Lecture 6 Project Scheduling: The process of defining project activities, determining their sequence, estimating their duration Scheduling.
Software Project Management By Deepika Chaudhary.
Project Planning Techniques U08784Software Project Management Rosemary Phillimore.
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
1 OMGT 3123 Project Management  Project Controlling  Project Management Techniques: PERT And CPM  The Framework Of PERT And CPM  Network Diagrams And.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Chapter 3 Managing the Information Systems Project
Project Management Inspections and Reviews 1 February.
Project Management Organization Scheduling 31 January.
24 January Software Engineering Processes Risk Management.
McGraw-Hill/Irwin Copyright © 2011 The McGraw-Hill Companies, All Rights Reserved Chapter 10 Projects.
(M) Chapter 12 MANGT 662 (A): Procurement, Logistics and Supply Chain Design Purchasing and Supply Chain Analysis (1/2)
Project Management Why do projects fail? Technical Reasons
PROJECT MANAGEMENT TOOLS AND TECHNIQUES SEMINAR December 2003.
Project Management Planning and Scheduling. “Failing to plan is planning to fail” by J. Hinze, Construction Planning and Scheduling Planning: “what” is.
Tools to Help  Product flow Dependencies and relationships of deliverables  Work breakdown structure The parts  PERT charts Program Evaluation and.
What is a Functional Spec?  Defines what the functionality will be NOT how it will be implemented  Describes features of the software product product's.
Project Management Project Controlling
PROJECT MANAGEMENT.
Project Management Systems
Copyright All Rights Reserved by
BUSINESS DRIVEN TECHNOLOGY
Project Management Chapter 3.
REQUIREMENTS Project management tools
Project Management and Information Security
Martha Grabowski LeMoyne College
CIS 210 Systems Analysis and Development
Importance of Project Schedules
REQUIREMENTS Project management tools
Presentation transcript:

“80% of software projects fail”  Standish Report (1995) Standish Report 16.2% completed on-time and on-budget with all features and functions as initially specified. 52.7% completed and operational but over-budget, over the time estimate, and offers fewer features and functions than originally specified. 31.1% cancelled at some point during the development cycle.  Sauer et al (2007) Sauer et al 67% “delivered close to budget, schedule, and scope expectations” with experienced project managers

Project Management Discipline of planning, organizing, and managing resources to bring about the successful completion of specific project goals and objectives

Should we eliminate risk?  Patton: Take calculated risks. That is quite different from being rash.  Nehru: The policy of being too cautious is the greatest risk of all.  Herodotus: Great deeds are usually wrought at great risks.  The Net: No risk => no challenge

Sources of Risk 1. Top management commitment 2. User commitment 3. Misunderstood requirements 4. Inadequate user involvement 5. Mismanaged user expectations 6. Scope creep 7. Lack of knowledge or skill Keil et al, “A Framework for Identifying Software Project Risks,” CACM 41:11, November 1998A Framework for Identifying Software Project Risks

Technical Risks  New features  New technology  Developer learning curve  Changes that may affect old code  Dependencies  Complexity  Bug history  Late changes  Rushed work  Tired programmers  Slipped in “pet” features  Unbudgeted items

ProcessWithin the Steps  Put together minimal solution Start with external commitments Introduce internal milestones  Focus on the risks  Add next level of features where possible  Identify components  Identify dependencies  Estimate (guess) Prefer educated guess  Lay out assignments and time frames Scheduling

Project Plan for this course Use simple spreadsheet (or equivalent) Deliverable/MilestoneResponsibleDue Revision 1 (7 Feb) Delivered project web siteSam20-Jan architectureJane (all)8-Feb15-Feb23-Feb project planHarry10-Feb15-Feb16-Feb initial user interfaceSam13-Feb15-Feb18-Feb contractJane20-Feb15-Feb18-Feb

Questions project plan answers  What is Joe working on this week?  Who can help me if I run into trouble?  If I have to choose an activity to be late, which one will impact the project more?

What needs to be in the plan?  All Deliverables  Code  Design  Test  Documentation  Learning  Presentation and demo prep  Reviews

Reviews and Inspections  Why? Developer can’t correct unseen errors More eyes to catch problems Earlier is cheaper ○ Integration fix typically 3-10 times the cost at design  Difference in terms Review implies completed work, often reviewed by someone at a different level Inspection implies peer review of work in progress

Inspections  Introduced by Michael Fagan in 1976 (IBM Systems Journal)  Formalized process Specific roles and steps Heavy preparation and follow-up  Used for documents and code In 1999, survey identified 117 checklists covering requirements, design, code, testing, documentation and process

Tools to Help  Product flow Dependencies and relationships of deliverables  Work breakdown structure The parts  PERT charts Program Evaluation and Review Technique  Critical Path Method Equivalent to PERT charts  Gantt charts Schedule overview

Product Flow  Identify sequences and dependencies  Distinguish new from existing components  Important if you have many different deliverables

Product Flow

Work Breakdown Structure  Need to break down the tasks into component parts and tasks  Level of detail important: The more detailed, the better  Lacks any time component

Work Breakdown

Graphical WBS

PERT Charts  Critical path identification Program Evaluation and Review Technique Also known as activity networks  Developed by Navy in 1958  Three stages: Planning (tasks and sequence) Scheduling (start and finish times) Analysis (float and revisions)  Two different models Activities are nodes (most common) or arcs

Pert Charts

CPM: Critical Path Method  Alternative to PERT  Dupont 1957  Graphical view of project  Predicts time required to complete  Shows which activities are critical to maintaining the schedule  Lacks the built in model of float  Easy to use informally

Planning 1. Identify the specific activities and milestones. 2. Determine the proper sequence of the activities. 3. Construct a network diagram. 4. Estimate the time required for each activity. 5. Determine the critical path (longest path through the network). 6. Update the PERT or CPM chart as the project progresses

Gantt Charts  Milestone charts  Invented by Harvey Gantt in 1916  Advantages Less detailed Amenable to management overlays

Gantt Chart with Overlays Note that dates are Day/Month

Scheduling Steps with Tools  Put together minimal solution Primary requirements  Start with external commitments Functional spec Milestones  Introduce internal milestones Work breakdown structure Product Flow PERT Chart or CPM, Gantt chart  Focus on the risks  Add next level of features where possible Secondary requirements

Resources  No shortage of available tools dmoz.org/Computers/Software/Project_Management  Project Management as a discipline Degrees Certification ○ Project Management Institute Project Management Institute