The document discusses project scope management. It defines scope management as ensuring a project includes all required work and only the required work to complete the project successfully. Scope management is important because schedule and budget cannot be managed if scope is uncontrolled. There are five key processes for managing scope: collect requirements, define scope, create a work breakdown structure (WBS), verify scope, and control scope. The WBS is a graphical representation of all work packages that breaks the project deliverables into manageable components. Scope change management involves documentation, tracking, and approval processes for any changes to product or project scope.
This document provides an overview of project scope management. It defines scope management as ensuring a project includes all required work and only the required work to complete the project successfully. It then outlines the six key processes for managing scope: plan scope management, collect requirements, define scope, create a work breakdown structure (WBS), validate scope, and control scope. These processes involve identifying deliverables, decomposing work, and monitoring the project to ensure it stays within scope. Managing scope is important for also managing schedule and budget (the "triple constraint").
This document discusses project scope management. It defines scope management as the processes required to ensure a project includes all necessary work and only necessary work to complete successfully. The six key processes of scope management are: 1) plan scope management, 2) collect requirements, 3) define scope, 4) create a work breakdown structure (WBS), 5) validate scope, and 6) control scope. Managing scope is important because scope impacts schedule and budget, known as the triple constraint of project management.
The document discusses the processes involved in scope management for a project. It defines scope management, product scope, and project scope. It then explains the six key processes for scope management: 1) plan scope management, 2) collect requirements, 3) define scope, 4) create the work breakdown structure (WBS), 5) validate scope, and 6) control scope. For each process, it provides an overview and lists the typical inputs, tools and techniques, and outputs.
This document discusses project scope management. It defines project scope management as the processes required to ensure a project includes all the work required, and only the work required, to complete the project successfully. Scope management is important because schedule and budget cannot be managed if scope is out of control. The key aspects of scope management are the work breakdown structure (WBS), which graphically shows all work packages, and the five scope management processes: collect requirements, define scope, create WBS, validate scope, and control scope. These processes are used to develop the scope baseline which establishes the project scope.
This document discusses project scope management for construction projects. It defines project scope as ensuring a project contains all required work and only the required work. The key processes are: collecting requirements, defining the scope statement, creating a work breakdown structure (WBS), validating the scope, and controlling scope. Requirements are gathered from stakeholders using techniques like interviews and workshops. The scope statement and WBS break the project scope into manageable components. Scope validation obtains customer acceptance, while scope control compares work to the baseline to ensure all approved scope is delivered.
This document discusses project integration and scope management. It defines integration management as coordinating all project elements and balancing competing demands. The seven key integration processes are outlined, including developing plans, directing execution, monitoring work, controlling changes, and closing projects. Scope management aims to include all necessary work and only that work. It discusses collecting requirements, defining scope, creating a work breakdown structure (WBS), verifying scope, and controlling scope.
Here are the answers to the questions:
1) B
2) C
3) B
4) B
5) A
The project manager should contact the customer to determine if the proposed scope change adds value before making any changes. Scope verification ensures customer acceptance and allows differences to come to light. The project scope statement is created during the planning process. If a team is subdividing work packages, they are decomposing. A WBS is a tool for tracking the schedule by breaking down work into smaller, more manageable components.
The document discusses project scope management, which involves defining and controlling what is included in a project. It covers developing a work breakdown structure (WBS) to plan and track a project's scope. A WBS breaks a project into smaller, more manageable components using a hierarchical structure. It also discusses collecting requirements, selecting projects, and managing scope through processes like defining scope, creating a WBS, and controlling scope. Weighted scoring models are presented as a method for selecting projects based on prioritized criteria.
This document discusses the key processes involved in project scope management: defining requirements, defining the scope, creating a work breakdown structure (WBS), verifying the scope, and controlling the scope. It describes collecting requirements by documenting stakeholder needs, defining scope by detailing the project and product description, creating a WBS by breaking work down into smaller components, verifying scope through formal acceptance of deliverables, and controlling scope by monitoring status against the baseline and managing changes.
The document discusses the six processes of scope management: plan scope management, collect requirements, define scope, create work breakdown structure (WBS), validate scope, and control scope. It provides key points about each process, including that plan scope management establishes how scope will be defined, validated and controlled throughout the project. Collect requirements determines stakeholder needs in detail. Define scope establishes requirement boundaries. The WBS breaks down all work into manageable parts and is critical for estimating and tracking project progress. Validate scope involves formal acceptance of deliverables. Control scope monitors project status against the scope baseline to prevent uncontrolled changes.
Help my project is in trouble. I have put this together to give project managers a guideline on how to move your project back into a successful journey
Project Management Cycle and MS Project 2013 By Subodh Kumar PMPSubodh Kumar
油
This document introduces project management concepts including the project management cycle, project and product lifecycles, and the Project Management Institute (PMI) framework. It discusses that a project has a definite beginning and end and is created to deliver a unique product or service. It then explains the five process groups that make up the project management cycle according to PMI: initiation, planning, execution, monitoring and control, and closing. Finally, it provides an overview of how Microsoft Project 2013 can be used to manage the schedule, resources, and other aspects of a project.
Presentation - Scope and Schedule Management of Business Analytics ProjectSharad Srivastava
油
This document summarizes the scope and schedule management of a business analytics project at a university. The project involves installing Oracle's EPM and OBIEE software to create a data warehouse and business intelligence system. Key aspects of the project include:
1) Defining the project scope to extract data from existing systems using ETL, create proof of concepts using delivered data marts, and demonstrate reporting and dashboards.
2) Developing a work breakdown structure and function point analysis to plan and track the work.
3) Implementing the project in three phases with deliverables, milestones, and quality standards to verify scope.
4) Establishing a change control process where only designated leads can request
2013 Project Management Institute. A Guide To The Project Management Body Of ...Arlene Smith
油
This document describes the process of planning scope management. It involves creating a scope management plan that documents how project scope will be defined, validated, and controlled. The plan is a component of the project management plan and is informed by the project charter, organizational process assets, and enterprise environmental factors. It provides guidance on how scope will be managed throughout the project.
This document provides an overview of project scope management processes, including planning how scope will be defined, collecting requirements, developing the project scope statement, creating the work breakdown structure (WBS), verifying completed deliverables meet requirements, and controlling scope changes. It discusses techniques for collecting requirements, balancing stakeholder needs, and developing the scope statement, WBS, and WBS dictionary to describe project and product scope. Formal acceptance of deliverables and managing changes to the scope baseline are also covered.
The document discusses project scope management which includes the processes required to ensure a project includes all the work needed and only the work needed to complete the project successfully. It defines key processes for scope management planning including collecting requirements, defining scope, and creating a work breakdown structure (WBS). Collecting requirements involves determining and documenting stakeholder needs. Defining scope develops a detailed product description. Creating a WBS subdivides deliverables into smaller, more manageable components to provide a framework for what needs to be delivered.
This document discusses project scope management. It begins with an agenda that outlines key topics like why manage project scope, defining project and product scope, and processes for planning, collecting requirements, defining, validating, and controlling scope. It then defines each process in more detail, providing inputs, tools and techniques, and outputs for planning scope management, collecting requirements, defining scope, creating a work breakdown structure, validating scope, and controlling scope. It also discusses the differences between project and product scope, and defines scope creep and gold plating, providing examples of each.
The document discusses project scope management based on the PMBOK Guide. It covers the key processes involved in scope management: plan scope management, collect requirements, define scope, create the work breakdown structure (WBS), validate scope, and control scope. For each process, it describes the inputs, tools and techniques, and outputs as defined by PMBOK. It also includes an example WBS and questions about the scope management processes.
This document is part of a series that explain the newly released PMBOK 5th edition. These documents provide simple explanation and summary of the book. However they do not replace the necessity of reading the book.(The 10 Knowledge Areas & ITTOs)
Triple Constraints of Projects: Scope, Cost & Scheduleshofiulalom
油
This document discusses project scope management and time management. It provides details on the key processes for each, including scope planning, definition, verification and control. For time management, it outlines the processes of activity definition, sequencing, resource and duration estimating, schedule development, and schedule control. The goal of both scope and time management is to ensure projects are completed on time and within budget by defining and controlling the work to be performed.
The document discusses the key processes in project scope management: collecting requirements, defining scope, creating a work breakdown structure (WBS), verifying scope, and controlling scope. It describes the inputs, tools and techniques, and outputs of each process. Specifically, it explains how to collect stakeholder requirements, define the project scope statement, develop the WBS and WBS dictionary, verify deliverables meet requirements, and manage scope changes through the project life cycle. The objective is to understand these critical scope management processes and how they are applied to define and control the scope of a project.
The document discusses key concepts in project management including:
1. It defines the difference between project strategy and objectives, with strategy being the general approach and objectives being specific results to achieve.
2. It outlines the typical project life cycle including planning, implementation, testing, and commissioning phases.
3. It describes the Project Management Body of Knowledge (PMBOK) which defines 9 knowledge areas and 44 processes for effective project management.
4. It focuses on scope management and how to create a work breakdown structure (WBS) to decompose a project into deliverables and tasks. The WBS helps estimate timelines, costs, and monitor progress.
Here is the PMP Training Project Scope Management Part 2 presented by Skillogic Knowledge Solutions.
Skillogic is one of the top training institute for PMP Certification Course in India. Classroom training available in Bangalore, Hyderabad and Chennai. Classes are conducting during the weekends.
For more details visit our website: http://in.skillogic.com/
Project Mangement - overview of the Scope Management knowledge area within project management. Describes the 6 processes within scope management and the process groups impacted.
Blog: https://agile-mercurial.com
YouTube: https://www.youtube.com/channel/UCPM82of2YuqIR1SgLGHa1eg
Twitter: https://twitter.com/agile_mercurial
Tumblr: https://agilemercurial.tumblr.com/
The document discusses how to structure web projects for success. It emphasizes understanding both the internal project environment and client environment. A successful project requires defining goals and metrics, establishing control structures like status meetings and issue tracking, structuring production into defined phases, and validating deliverables through testing and signoff. Roles and responsibilities must also be divided among strategic, tactical, operational, and production levels to ensure proper support, escalation procedures, and respect for each team member's area.
The document discusses the key elements of an effective project plan, including authorization, project scope, an integrated management plan, and resource estimates. It emphasizes that the project plan guides both project execution and control by documenting planning assumptions, decisions, and establishing baselines for progress measurement. The project plan is a formal document that is composed of various artifacts including the project charter, scope statement, schedule, budget, and risk management plan. It defines how the project will be executed, monitored, controlled and closed.
The document discusses document-oriented databases and MongoDB. It provides an overview of MongoDB, including that it is an open-source, document-based database that stores data in JSON-like documents with dynamic schemas. It supports common operations like CRUD and indexing to query and modify data efficiently. Some key features are that MongoDB is horizontally scalable, uses dynamic schemas, and is suitable for large, unstructured data like that needed in applications with big data requirements.
The document discusses project scope management, which involves defining and controlling what is included in a project. It covers developing a work breakdown structure (WBS) to plan and track a project's scope. A WBS breaks a project into smaller, more manageable components using a hierarchical structure. It also discusses collecting requirements, selecting projects, and managing scope through processes like defining scope, creating a WBS, and controlling scope. Weighted scoring models are presented as a method for selecting projects based on prioritized criteria.
This document discusses the key processes involved in project scope management: defining requirements, defining the scope, creating a work breakdown structure (WBS), verifying the scope, and controlling the scope. It describes collecting requirements by documenting stakeholder needs, defining scope by detailing the project and product description, creating a WBS by breaking work down into smaller components, verifying scope through formal acceptance of deliverables, and controlling scope by monitoring status against the baseline and managing changes.
The document discusses the six processes of scope management: plan scope management, collect requirements, define scope, create work breakdown structure (WBS), validate scope, and control scope. It provides key points about each process, including that plan scope management establishes how scope will be defined, validated and controlled throughout the project. Collect requirements determines stakeholder needs in detail. Define scope establishes requirement boundaries. The WBS breaks down all work into manageable parts and is critical for estimating and tracking project progress. Validate scope involves formal acceptance of deliverables. Control scope monitors project status against the scope baseline to prevent uncontrolled changes.
Help my project is in trouble. I have put this together to give project managers a guideline on how to move your project back into a successful journey
Project Management Cycle and MS Project 2013 By Subodh Kumar PMPSubodh Kumar
油
This document introduces project management concepts including the project management cycle, project and product lifecycles, and the Project Management Institute (PMI) framework. It discusses that a project has a definite beginning and end and is created to deliver a unique product or service. It then explains the five process groups that make up the project management cycle according to PMI: initiation, planning, execution, monitoring and control, and closing. Finally, it provides an overview of how Microsoft Project 2013 can be used to manage the schedule, resources, and other aspects of a project.
Presentation - Scope and Schedule Management of Business Analytics ProjectSharad Srivastava
油
This document summarizes the scope and schedule management of a business analytics project at a university. The project involves installing Oracle's EPM and OBIEE software to create a data warehouse and business intelligence system. Key aspects of the project include:
1) Defining the project scope to extract data from existing systems using ETL, create proof of concepts using delivered data marts, and demonstrate reporting and dashboards.
2) Developing a work breakdown structure and function point analysis to plan and track the work.
3) Implementing the project in three phases with deliverables, milestones, and quality standards to verify scope.
4) Establishing a change control process where only designated leads can request
2013 Project Management Institute. A Guide To The Project Management Body Of ...Arlene Smith
油
This document describes the process of planning scope management. It involves creating a scope management plan that documents how project scope will be defined, validated, and controlled. The plan is a component of the project management plan and is informed by the project charter, organizational process assets, and enterprise environmental factors. It provides guidance on how scope will be managed throughout the project.
This document provides an overview of project scope management processes, including planning how scope will be defined, collecting requirements, developing the project scope statement, creating the work breakdown structure (WBS), verifying completed deliverables meet requirements, and controlling scope changes. It discusses techniques for collecting requirements, balancing stakeholder needs, and developing the scope statement, WBS, and WBS dictionary to describe project and product scope. Formal acceptance of deliverables and managing changes to the scope baseline are also covered.
The document discusses project scope management which includes the processes required to ensure a project includes all the work needed and only the work needed to complete the project successfully. It defines key processes for scope management planning including collecting requirements, defining scope, and creating a work breakdown structure (WBS). Collecting requirements involves determining and documenting stakeholder needs. Defining scope develops a detailed product description. Creating a WBS subdivides deliverables into smaller, more manageable components to provide a framework for what needs to be delivered.
This document discusses project scope management. It begins with an agenda that outlines key topics like why manage project scope, defining project and product scope, and processes for planning, collecting requirements, defining, validating, and controlling scope. It then defines each process in more detail, providing inputs, tools and techniques, and outputs for planning scope management, collecting requirements, defining scope, creating a work breakdown structure, validating scope, and controlling scope. It also discusses the differences between project and product scope, and defines scope creep and gold plating, providing examples of each.
The document discusses project scope management based on the PMBOK Guide. It covers the key processes involved in scope management: plan scope management, collect requirements, define scope, create the work breakdown structure (WBS), validate scope, and control scope. For each process, it describes the inputs, tools and techniques, and outputs as defined by PMBOK. It also includes an example WBS and questions about the scope management processes.
This document is part of a series that explain the newly released PMBOK 5th edition. These documents provide simple explanation and summary of the book. However they do not replace the necessity of reading the book.(The 10 Knowledge Areas & ITTOs)
Triple Constraints of Projects: Scope, Cost & Scheduleshofiulalom
油
This document discusses project scope management and time management. It provides details on the key processes for each, including scope planning, definition, verification and control. For time management, it outlines the processes of activity definition, sequencing, resource and duration estimating, schedule development, and schedule control. The goal of both scope and time management is to ensure projects are completed on time and within budget by defining and controlling the work to be performed.
The document discusses the key processes in project scope management: collecting requirements, defining scope, creating a work breakdown structure (WBS), verifying scope, and controlling scope. It describes the inputs, tools and techniques, and outputs of each process. Specifically, it explains how to collect stakeholder requirements, define the project scope statement, develop the WBS and WBS dictionary, verify deliverables meet requirements, and manage scope changes through the project life cycle. The objective is to understand these critical scope management processes and how they are applied to define and control the scope of a project.
The document discusses key concepts in project management including:
1. It defines the difference between project strategy and objectives, with strategy being the general approach and objectives being specific results to achieve.
2. It outlines the typical project life cycle including planning, implementation, testing, and commissioning phases.
3. It describes the Project Management Body of Knowledge (PMBOK) which defines 9 knowledge areas and 44 processes for effective project management.
4. It focuses on scope management and how to create a work breakdown structure (WBS) to decompose a project into deliverables and tasks. The WBS helps estimate timelines, costs, and monitor progress.
Here is the PMP Training Project Scope Management Part 2 presented by Skillogic Knowledge Solutions.
Skillogic is one of the top training institute for PMP Certification Course in India. Classroom training available in Bangalore, Hyderabad and Chennai. Classes are conducting during the weekends.
For more details visit our website: http://in.skillogic.com/
Project Mangement - overview of the Scope Management knowledge area within project management. Describes the 6 processes within scope management and the process groups impacted.
Blog: https://agile-mercurial.com
YouTube: https://www.youtube.com/channel/UCPM82of2YuqIR1SgLGHa1eg
Twitter: https://twitter.com/agile_mercurial
Tumblr: https://agilemercurial.tumblr.com/
The document discusses how to structure web projects for success. It emphasizes understanding both the internal project environment and client environment. A successful project requires defining goals and metrics, establishing control structures like status meetings and issue tracking, structuring production into defined phases, and validating deliverables through testing and signoff. Roles and responsibilities must also be divided among strategic, tactical, operational, and production levels to ensure proper support, escalation procedures, and respect for each team member's area.
The document discusses the key elements of an effective project plan, including authorization, project scope, an integrated management plan, and resource estimates. It emphasizes that the project plan guides both project execution and control by documenting planning assumptions, decisions, and establishing baselines for progress measurement. The project plan is a formal document that is composed of various artifacts including the project charter, scope statement, schedule, budget, and risk management plan. It defines how the project will be executed, monitored, controlled and closed.
The document discusses document-oriented databases and MongoDB. It provides an overview of MongoDB, including that it is an open-source, document-based database that stores data in JSON-like documents with dynamic schemas. It supports common operations like CRUD and indexing to query and modify data efficiently. Some key features are that MongoDB is horizontally scalable, uses dynamic schemas, and is suitable for large, unstructured data like that needed in applications with big data requirements.
Cassandra is an open source, distributed database management system designed to handle large amounts of data across many commodity servers. It provides high availability with no single point of failure, linear scalability and performance, as well as flexibility in schemas. Cassandra finds use in large companies like Facebook, Netflix and eBay due to its abilities to scale and perform well under heavy loads. However, it may not be suited for applications requiring many joins, transactions or strong consistency guarantees.
This document provides an introduction to NoSQL databases. It discusses the history and limitations of relational databases that led to the development of NoSQL databases. The key motivations for NoSQL databases are that they can handle big data, provide better scalability and flexibility than relational databases. The document describes some core NoSQL concepts like the CAP theorem and different types of NoSQL databases like key-value, columnar, document and graph databases. It also outlines some remaining research challenges in the area of NoSQL databases.
The document discusses software security testing. It defines software security testing as testing that aims to uncover vulnerabilities in a system and ensure data and resources are protected from intruders. The document then describes common security measures, approaches to security testing including functional and risk-based methods, and how security processes can be integrated into the software development lifecycle. It outlines how security testing is relevant at various stages including requirements, design, coding, integration, and system testing.
E governance and digital india initiativenehabsairam
油
The document discusses e-governance and India's Digital India initiative. E-governance uses information technologies to make government more efficient and transparent for citizens. India implemented e-governance in phases from the late 1980s onward. Digital India, launched in 2015, aims to transform India into a digitally empowered society through initiatives like expanding broadband internet access nationwide, digitizing government services, and improving digital literacy. The nine pillars of Digital India focus on areas like digital infrastructure, governance, healthcare, education, and financial inclusion to promote digital transformation across India.
This document discusses localization techniques in wireless sensor networks. It begins with introducing wireless sensor networks and their components. It then discusses the need for localization to track objects within sensor networks. There are two main types of localization schemes - range-based which uses distance or angle measurements, and range-free which uses approximate distance estimates. Examples of range-based techniques include time of arrival, time difference of arrival, received signal strength indicator, and angle of arrival. Range-free techniques include proximity and distance-based localization using hop counts. The document compares the advantages and disadvantages of different localization methods.
How to Configure Flexible Working Schedule in Odoo 18 EmployeeCeline George
油
In this slide, well discuss on how to configure flexible working schedule in Odoo 18 Employee module. In Odoo 18, the Employee module offers powerful tools to configure and manage flexible working schedules tailored to your organization's needs.
How to Configure Restaurants in Odoo 17 Point of SaleCeline George
油
Odoo, a versatile and integrated business management software, excels with its robust Point of Sale (POS) module. This guide delves into the intricacies of configuring restaurants in Odoo 17 POS, unlocking numerous possibilities for streamlined operations and enhanced customer experiences.
Useful environment methods in Odoo 18 - Odoo 際際滷sCeline George
油
In this slide well discuss on the useful environment methods in Odoo 18. In Odoo 18, environment methods play a crucial role in simplifying model interactions and enhancing data processing within the ORM framework.
Research & Research Methods: Basic Concepts and Types.pptxDr. Sarita Anand
油
This ppt has been made for the students pursuing PG in social science and humanities like M.Ed., M.A. (Education), Ph.D. Scholars. It will be also beneficial for the teachers and other faculty members interested in research and teaching research concepts.
Database population in Odoo 18 - Odoo slidesCeline George
油
In this slide, well discuss the database population in Odoo 18. In Odoo, performance analysis of the source code is more important. Database population is one of the methods used to analyze the performance of our code.
Information Technology for class X CBSE skill SubjectVEENAKSHI PATHAK
油
These questions are based on cbse booklet for 10th class information technology subject code 402. these questions are sufficient for exam for first lesion. This subject give benefit to students and good marks. if any student weak in one main subject it can replace with these marks.
Prelims of Kaun TALHA : a Travel, Architecture, Lifestyle, Heritage and Activism quiz, organized by Conquiztadors, the Quiz society of Sri Venkateswara College under their annual quizzing fest El Dorado 2025.
QuickBooks Desktop to QuickBooks Online How to Make the MoveTechSoup
油
If you use QuickBooks Desktop and are stressing about moving to QuickBooks Online, in this webinar, get your questions answered and learn tips and tricks to make the process easier for you.
Key Questions:
* When is the best time to make the shift to QuickBooks Online?
* Will my current version of QuickBooks Desktop stop working?
* I have a really old version of QuickBooks. What should I do?
* I run my payroll in QuickBooks Desktop now. How is that affected?
*Does it bring over all my historical data? Are there things that don't come over?
* What are the main differences between QuickBooks Desktop and QuickBooks Online?
* And more
Mate, a short story by Kate Grenvile.pptxLiny Jenifer
油
A powerpoint presentation on the short story Mate by Kate Greenville. This presentation provides information on Kate Greenville, a character list, plot summary and critical analysis of the short story.
1. Project Scope
Project Scope
Management
Management
Sections of this presentation were adapted
Sections of this presentation were adapted
from
from A Guide to the Project Management
A Guide to the Project Management
Body of Knowledge
Body of Knowledge 4
4th
th
Edition, Project
Edition, Project
Management Institute Inc., 息 2009
Management Institute Inc., 息 2009
2. Project Scope Management
Project Scope Management
The processes required to ensure that the
The processes required to ensure that the
project includes all the work required, and
project includes all the work required, and
only the work required, to complete the
only the work required, to complete the
project successfully
project successfully
Answers the question What will the
Answers the question What will the
project produce in the end.
project produce in the end.
3. Why Do We Manage Scope?
Why Do We Manage Scope?
Cant manage schedule
Cant manage schedule
and budget if scope is
and budget if scope is
out of control (Triple
out of control (Triple
Constraint)
Constraint)
Scope docs are used to
Scope docs are used to
manage expectations
manage expectations
TIME
COST
SCOPE
Quality
4. Scope Management Key Points
Scope Management Key Points
What is scope management
What is scope management
Checking to ensure that one is completing work
Checking to ensure that one is completing work
Saying No to additional work not in the charter
Saying No to additional work not in the charter
Preventing extra work/gold plating
Preventing extra work/gold plating
Work Breakdown Structure
Work Breakdown Structure
(WBS)
(WBS)
Foundation of the project, all
Foundation of the project, all
planning and controlling is based
planning and controlling is based
on the WBS
on the WBS
Identifies all work to be
Identifies all work to be
performed, if it is not in the WBS
performed, if it is not in the WBS
it does not need to be done
it does not need to be done
Graphical picture of work
Graphical picture of work
WBS
Estimating
Network
Diagrams
Staffing Risk
5. How Do We Manage Scope?
How Do We Manage Scope?
Five processes
Five processes
Collect Requirements
Collect Requirements
Define Scope
Define Scope
Create WBS
Create WBS
Verify Scope
Verify Scope
Control Scope
Control Scope
Collect
Requirements
Define
Scope
Create
WBS
Verify
Scope
Control
Scope
6. Collect Requirements
Collect Requirements
Project Charter
Interviews
Focus groups
Facilitated workshops
Group creativity techniques
Group decision making techniques
Questionnaires and surveys
Observations
Prototypes
Inputs Outputs
Tools & Techniques
Requirements docs
Stakeholder
Register
Collect
Requirements
Define
Scope
Create
WBS
Verify
Scope
Control
Scope
Requirements mgmt
plan
Requirements
traceability matrix
7. Collect Requirements
Collect Requirements
Determine product of the project
Determine product of the project
requirements
requirements
Make sure all requirements support the
Make sure all requirements support the
business need of the project as
business need of the project as
described in the charter
described in the charter
11. Work Breakdown Structure
Work Breakdown Structure
Start with major project deliverables or phases
Start with major project deliverables or phases
Decomposition is breaking down the
Decomposition is breaking down the
deliverables into more manageable parts
deliverables into more manageable parts
Not all branches need the same level of
Not all branches need the same level of
decomposition!
decomposition!
Decompose into Work Packages
Decompose into Work Packages
8-80 Hour Rule
8-80 Hour Rule
Dont break work down too
Dont break work down too
much
much
14. Control Scope
Control Scope
Project
Management Plan
Work Performance
Information
Requirements
Documentation
Variance analysis
Inputs
Tools & Techniques
Requirements
Traceability Matrix
Work Performance
Measures
Outputs
Organizational
Process Assets
Organizational
Process Assets
Change Requests
Project Management
Plan Updates
Project Document
Updates
Collect
Requirements
Define
Scope
Create
WBS
Verify
Scope
Control
Scope
15. Scope Definitions
Scope Definitions
Change Control System
Change Control System
Documentation, tracking, and approvals required to
Documentation, tracking, and approvals required to
change
change project
project scope
scope
Configuration Management System
Configuration Management System
Documentation, tracking, and approvals required to
Documentation, tracking, and approvals required to
change
change product
product scope
scope
Management by Objectives (MBO)
Management by Objectives (MBO)
Establish unambiguous and realistic objectives
Establish unambiguous and realistic objectives
Periodically evaluate if objectives are being met
Periodically evaluate if objectives are being met
Take corrective action
Take corrective action
16. Other Topics Project Selection
Other Topics Project Selection
Benefit Measurement
Benefit Measurement
Methods (Comparative
Methods (Comparative
Approach)
Approach)
Murder Board Panel
Murder Board Panel
that tries to shoot down
that tries to shoot down
new ideas
new ideas
Scoring Models
Scoring Models
Benefit Compared to
Benefit Compared to
Cost
Cost
Constrained
Constrained
Optimization Methods
Optimization Methods
(Mathematical)
(Mathematical)
Linear Programming
Linear Programming
Integer Programming
Integer Programming
Multi-Objective
Multi-Objective
Programming
Programming