Goal and Scope Where are we going and what path will we be taking?

Slides:



Advertisements
Similar presentations
Project Management 6e..
Advertisements

Software Quality Assurance Plan
Chapter 3 Managing the Information Systems Project
© 2005 by Prentice Hall Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Introduction to Project Management Chapter 6 Managing Project Scheduling Information Systems Project Management: A Process and Team Approach, 1e Fuller/Valacich/George.
CS3773 Software Engineering Lecture 8 Software Planning and Estimation.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Defining the Project CHAPTER FOUR Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Modern Systems Analysis and Design Third Edition
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 3 Managing the Information Systems Project
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java Project Management Introduction Using UML, Patterns,
Project Management Session 7
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
LSU 07/24/2004Defining Project Tasks1 Defining the Project Tasks Project Management Unit, Lecture 4.
Part II Project Planning © 2012 John Wiley & Sons Inc.
Project Management and Scheduling
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
© 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.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Edward B. Farkas, Managing Director, Project Management Practice
Typical Software Documents with an emphasis on writing proposals.
Bellevue Planning Exhibits1 Welcome to Project Planning Instructor Phyllis Sweeney Project Planning Class.
Chapter 4 Defining the Project.
Defining the Project CHAPTER FOUR PowerPoint Presentation by Charlie Cook Copyright © 2014 McGraw-Hill Education. All Rights Reserved.
Copyright © 2014 McGraw-Hill Higher Education. All rights reserved. CHAPTER 15 Project Management McGraw-Hill/Irwin.
What’s a Project? AD642. Why the Emphasis on Project Management? Copyright 2011 John Wiley & Sons, Inc. 1-2  Many tasks do not fit neatly into business-as-usual.
Week 6: Project Management E1102 – Design Fundamental Using Advanced Computer Technologies Spring 2010.
Scope Management Chapter 5.
Welcome to Session 4 – Project Management Process Overview (continued) Instructor:Phyllis Sweeney Instructor: Phyllis Sweeney Project Management Certificate.
Common Activities Activities and Tasks in the WBS.
CSCI 521 Night 3. 1.What does this talk have to do with Software Project Management? 2.What was your favorite example he used to illustrate a point, and.
Strong9 Consulting Services, LLC 1 PMI - SVC I-80 Breakfast Roundtable Monthly Meeting Thursday, October 12, :00 am – 9:00 am.
Lecture 6. Review of Lecture 5 Company strategic planning: mission and objective statements and competitive strategy. Planning Methods: Top-down, Bottom-up.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
5-1 Copyright © 2013 McGraw-Hill Education (Australia) Pty Ltd Pearson, Larson, Gray, Project Management in Practice, 1e CHAPTER 5 Defining the Scope of.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems The Integrated Master Plan (IMP) and the Integrated Master Schedule.
Scope Management Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 5 Learning Objectives After completing this chapter,
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall o P.I.I.M.T o American University of Leadership Ahmed Hanane, MBA, Eng, CMA, Partner.
© 2014 Pearson Education, Inc., Upper Saddle River, NJ. All rights reserved. This material is protected by Copyright and written permission should be obtained.
Project Management and Risk. Definitions Project Management: a system of procedures, practices, technologies, skills, and experience needed to manage.
Component 8 Installation and Maintenance of Health IT Systems Unit 4 Structured Systems Analysis and Design This material was developed by Duke University,
Initiation and Planning for Success Sridhar Seshagiri Rao, PMP Innova Solutions Inc. Santa Clara, CA. April 9 th 2004.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 3 Managing the Information Systems Project 3.1.
Initiation Project Management Minder Chen, Ph.D. CSU Channel Islands
The Goal: To Climb Above The Competition Copyright 2005: I Lead Projects, L.L.C. Course Description Project Process Workplates Project Process Workplates.
Quick Recap. Project Initiation overview Awareness of the need for change (situation, context) and recognition by stakeholders that only a project can.
The Project Plan Plan Your Work, then Work Your Plan
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
1 Chapter 11 Planning. 2 Project Planning “establishing a predetermined course of action within a forecasted environment” “establishing a predetermined.
V. 2. © Copyright and all rights reserved 4. Project Integration Management PMP Prep Course Based on the PMBOK ® Guide 3 rd Edition.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
HCIS 410 Read, Lead, Succeed/Uophelpdotcom For more course tutorials visit
IT-301 Project Management I: Unit 4: Cost Management.
CIS 170 MART Teaching Effectively/cis170mart.com FOR MORE CLASSES VISIT HCIS 410 AID Inspiring Minds/hcis410aid.com FOR MORE CLASSES.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Role of The Software Development Plan (SDP)
Project Management PTM721S
Systems Analysis and Design in a Changing World, 4th Edition
Business System Development
Defining the Activities
PMIS Initiating a Project Application of Project Management Processes Project Charter Stakeholder Analysis and Stakeholder Register 2. Planning.
Software Project Management
Project Management and Risk
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Presentation transcript:

Goal and Scope Where are we going and what path will we be taking?

Course Outline So far in this course… Development Process Models Fitting into the Business Process People in the Process Next… Establishing a target and direction Estimating the costs of getting there Creating a roadmap to get there

Steps in Every Project 1. Learn Why this is being done 2. Decide What needs to be done 3. Figure out How to get it done 4. Do it 5. Look back at how well it went

Getting Started Why – Goal Statement What – Statement(s) of Work How – Software Project Management Plan Do It Did It 4 of 16 Why What How

Why Why ask why? Establish boundaries and priorities Context, Information Objectives, Function Objectives Decision to do a project is usually based on return on investment feasibility study economic and operational feasibility technical feasibility schedule feasibility 5 of 16 > Why What How

Goal Statement - purpose Managing Expectations Good Goal Statements explain both what and why 6 of 16 > Why What How

Goal Statement is… States both deliverables and process Measurable Short Doable Communicated 7 of 16 > Why What How

Example Goal Statement “First, I believe that this nation should commit itself to achieving the goal, before this decade is out, of landing a man on the moon and returning him safely to the earth. No single space project in this period will be more impressive to mankind, or more important for the long-range exploration of space; and none will be so difficult or expensive to accomplish. ” -- JFK of 16 > Why What How

The Need to be Clear 9 of 16 Why > What How

Statement of Work Context Part of the SPMP Separate from the SRS Purpose “A SOW should specify in clear, understandable terms the work to be done in developing or producing the goods to be delivered or services to be performed by a contractor. A SOW defines all non-specification requirements for contractor effort. Specifications are typically referenced in the SOW but the specific qualitative or quantitative technical requirements shall not be spelled out in the SOW. “ 10 of 16 Why > What How

SOW Format – example 1 STATEMENT OF WORK 1. GENERAL. The Bureau of Reclamation has a requirement for … 2. BACKGROUND. 3. WORK TO BE PERFORMED BY CONTRACTOR. 4. GOVERNMENT-FURNISHED MATERIALS/SERVICES. 5. SUMMARY OF DELIVERABLE. 6. PROJECT COMPLETION/DELIVERY SCHEDULE 6.1 REVIEW OF DELIVERABLES. 6.2 ACCEPTANCE OF DELIVERABLES. 7. CONTRACTOR PAYMENT SCHEDULE 8. TECHNICAL COORDINATION 9. ADDRESS FOR DELIVERABLES 11 of 16 Why > What How

SOW Format – example 2 DOD-type SOW 1. Scope – what is in this SOW 2. Background 3. Related Documents 4. Deliverables Sub-Tasks Reports place of work review timetable 12 of 16 Why > What How

SPMP Contents Goal Statement Process Model management and technical Organization Timetable and Deliverables Work Breakdown – next topic tonight Schedule – next week’s topic Budget 13 of 16 Why What > How

Sample SPMP Table of Contents irmc.state.nc.us/documents/approvals/reporting/SPMPLAN.doc 1. Introduction Project Overview Project Deliverables Evolution of the Software Project Management Plan Reference Material Definitions and Acronyms 2. Project Organization 2.1 Process Model 2.2 Organizational Structure 2.3 Organizational Boundaries and Interfaces 2.4 Project Responsibilities 3. Management Process 3.1 Management Objectives and Priorities 3.2 Assumptions, Dependencies, and Constraints 3.3 Risk Management 3.4 Monitoring and Control Mechanisms 3.5 Staffing Plan 4. Technical Process 4.1 Methods, Tools, and Techniques 4.2 Software Documentation 4.3 Project Support Functions 14 of 16

5. Work Packages, Schedules, and Budget 5.1 Work Packages 5.2 Dependencies 5.3 Resource Requirements 5.4 Budget Requirements 5.5 Budget and Resource allocation 5.6 Schedule 5.7 Network Diagram 6. Project Success Criteria 6.1 Network Diagram 6.2 Project Milestones 6.3 Approval Process 6.4 Acceptance Criteria 6.5 Critical Success Factors 7. Additional Components 8. Plan Approvals 9. Glossary of Terms 10. Appendices 15 of 16 Why What > How

IEEE 1058 Standard for SPMP 1. Introduction 1.1 Project overview 1.2 Project deliverables 1.3 Evolution of the SPMP 1.4 Reference materials 1.5 Definitions and acronyms 2. Project organization 2.1 Process model 2.2 Organizational structure 2.3 Organizational boundaries and interfaces 2.4 Project responsibilities 3. Managerial process 3.1 Managerial objectives & priorities 3.2 Assumptions, dependencies & constraints 3.3 Risk management 3.4 Monitoring & controlling mechanisms 3.5 Staffing plan 4. Technical process 4.1 Methods, tools & techniques 4.2 Software documentation 4.3 Project support functions 5. Work packages, schedule & budget 5.1 Work packages 5.2 Dependencies 5.3 Resource requirements 5.4 Budget & resource allocation 5.5 Schedule 16 of 16 Why What > How

Where next… deciding on the sub-tasks the Work Breakdown Structure (WBS) estimating size, duration, … assigning tasks