https://mloey.github.io/courses/pmp2017.html
We will discuss the following: Project Management Processes, Initiating Process, Planning Process, Executing Process, Monitoring and controlling Process, Closing Process, Knowledge Areas, Project Management Process and Knowledge Area Mapping
The concepts and processes on how to perform project cost management according to PMBOK Guide 6th edition. You'll find key concepts and terms, plan cost management, estimate costs, determine budget, and control cost.
https://mloey.github.io/courses/pmp2017.html
We will discuss the following: Project Management Processes, Initiating Process, Planning Process, Executing Process, Monitoring and controlling Process, Closing Process, Knowledge Areas, Project Management Process and Knowledge Area Mapping
The concepts and processes on how to perform project cost management according to PMBOK Guide 6th edition. You'll find key concepts and terms, plan cost management, estimate costs, determine budget, and control cost.
The concepts and processes on how to perform project schedule management according to PMBOK Guide 6th edition. You'll find key concepts and terms, plan schedule management, define activities, sequence activities, estimate activity duration, develop schedule, and control schedule.
Project management tools and techniquesTata Dinyuy
The different tools and techniques used to plan projects ( both micro and macro projects) including human, material, financial and scheduling techniques (how to draw up Gantt charts, work breakdown schedule, network diagrams and the Program Evaluation and Review Technique)
Contents are sourced from different authors including PMBOK 5th Edition.
This is provided for free as part of our Continuing Practice in Project Management Professional Certification. You may download, share but please refrain from commercializing it or altering parts. Thanks.
For more on Innovations and Project Management, please visit www.facebook.com/SigmaProcessExcellence
Chapter 11 of ICT Project Management based on IOE Engineering syllabus. In this chapter you can learn about importance of communication management, its planning process, organizing and conducting effective meeting etc. Provided By Project Management Sir of KU
Chapter 06 of ICT Project Management based on IOE Engineering syllabus. This chapter provides knowledge on project management processes, overlaps of process groups in a phase and mapping of project management.Provided by Project Management Sir of KU.
The concepts and processes on how to perform project scope management according to PMBOK Guide 6th edition. You'll find key concepts and terms, plan scope management, collect requirements, define scope, create WBS, validate scope, and control scope.
What is a Project and Project Management? This presentation helps you to gain more knowledge about how to manage a project and helps in understanding the Project Life Cycle.
The concepts and processes on how to perform project schedule management according to PMBOK Guide 6th edition. You'll find key concepts and terms, plan schedule management, define activities, sequence activities, estimate activity duration, develop schedule, and control schedule.
Project management tools and techniquesTata Dinyuy
The different tools and techniques used to plan projects ( both micro and macro projects) including human, material, financial and scheduling techniques (how to draw up Gantt charts, work breakdown schedule, network diagrams and the Program Evaluation and Review Technique)
Contents are sourced from different authors including PMBOK 5th Edition.
This is provided for free as part of our Continuing Practice in Project Management Professional Certification. You may download, share but please refrain from commercializing it or altering parts. Thanks.
For more on Innovations and Project Management, please visit www.facebook.com/SigmaProcessExcellence
Chapter 11 of ICT Project Management based on IOE Engineering syllabus. In this chapter you can learn about importance of communication management, its planning process, organizing and conducting effective meeting etc. Provided By Project Management Sir of KU
Chapter 06 of ICT Project Management based on IOE Engineering syllabus. This chapter provides knowledge on project management processes, overlaps of process groups in a phase and mapping of project management.Provided by Project Management Sir of KU.
The concepts and processes on how to perform project scope management according to PMBOK Guide 6th edition. You'll find key concepts and terms, plan scope management, collect requirements, define scope, create WBS, validate scope, and control scope.
What is a Project and Project Management? This presentation helps you to gain more knowledge about how to manage a project and helps in understanding the Project Life Cycle.
I am Continuously seeking to improve my competencies and skills to provide first class professional Project Management training courses; and develop my scope experience in Project Management functions.
I am confident that my innovative and results-focused approach would make significant contribution to the continued success of your organization.
this is the first presentations uploaded to Slide Share,
For more information do not hesitate to contact me.
Ahmad H. Maharma - PMP®
Ramallah, Palestine
Phone: + (972) (2) 2968644
Mobile: + (972) (599) 001155E-Mail: ahmad.maharma@gmail.com
Project management methodologies change over time but one element of all projects always remains important - Project Charter. Here I am sharing a template for a medium to large implementation project type of project, for example SAP system implementation.
PROJECT PART ONE
1
Part-1: Creating a New Plane
Students Name
Institution Affiliation
Course
Date
Part-1: Creating a New Plane
Project Title: Creating a New Plane
A Work Breakdown Structure (WBS) lists all project duties. WBS is hierarchical and offers logical, ambiguity-free categorization. Activities or deliverables may define these categories. The WBS must represent the approved work. The project's scope statement should be used to create a timetable and cost estimate. Project managers must construct a WBS before developing a strategy and timeline. Developing a WBS and WBS Dictionary will allow the project team to: 1)gather information on the project's work requirements for creating a new plane, 2)divide operations into smaller portions that will fulfill the project's goals, and 3)design the project so that it is proactive and logical from beginning to end.
Before the project begins, the PM has minimal influence. without specifying project scope. Through scope management, the project manager can design and maintain the scope statement. This statement describes the project manager's deliverables. This phase ensures and communicates to project management that only scope-related activity is done. This step helps complete the work.
Planning
Most firms that use project management make their OPA available to project managers. This, along with a Project Charter and Preliminary Project Scope Statement, will help the PM launch this part of the project. The Project Manager will have a Scope Management Plan after this stage. According to the Scope Management Plan, the PM will document, refine, verify, and oversee the project scope.
Define.
Project scope is next. To define project requirements, the project manager must interview all relevant parties. After understanding the project's stakeholders' needs and expectations, the scope can be established by prioritizing outputs. Discussing some options now may be helpful if they need to be documented later. After completing the scope definition, the project manager should conclude the scope statement. This will help in later project stages when making selections and ensuring everyone knows the project's goals.
Create a WBS.
A well-designed WBS should focus on project deliverables, not tasks (WBS). If you don't use the Work Breakdown Structure (WBS) as a checklist of activities to do (your project plan will help), you can focus on the WBS's primary purpose: organizing and outlining the project's scope. Work packages should be the foundation of the Work Breakdown Structure (WBS). These work bundles should help you estimate the project's cost and timeline.
Verification
In "Scope Verification," you'll win stakeholders' formal approval of your project's scope. To acquire this degree of acceptability, you must often undergo Inspection.
Control
Change Integrated Any project changes require a Control Process (ICCP). During Scope Control, you'll address ever.
6 Work Breakdown Structure and SchedulingCavan ImagesSto.docxevonnehoggarth79783
6 Work Breakdown Structure and Scheduling
Cavan Images/Stone/Getty Images
Learning Objectives
By the end of this chapter, you will be able to:
• Discuss the creation of a project work breakdown structure.
• Describe the scheduling process.
• Explain how to create schedules.
CO_CRD
CN
CT
CO_LO
CO_TX
CO_BL
co-cn
co-cr
co-box
co-intro
co-photo
co
bar81677_06_c06_173-198.indd 173 9/9/14 10:52 AM
Section 6.1 The Work Breakdown Structure
Pretest
1. To prepare a work breakdown structure for a project, the project manager starts from
the project’s end point and works backward.
a. True
b. False
2. Project schedules can act as constraints rather than efficiency tools.
a. True
b. False
3. Using a project template is recommended for simplifying the scheduling process.
a. True
b. False
Answers can be found at the end of the chapter.
Introduction
If you have ever been part of a team effort where it was unclear who was doing what, then you
have experienced the consequences of not planning out project work. When a team takes on
a project, there must be a plan for the work, a way to identify all the work tasks that must be
done in sequence to produce the project deliverable. In project management, this is called the
work breakdown structure. The WBS is the “what” in the question of who does what. Later,
team members are assigned to the work, but the first step is deciding what the work is.
This chapter will cover the process of defining and breaking down project work and schedul-
ing work tasks and milestones. It will focus on the WBS and scheduling process and the issues
involved in effective scheduling. This is important because outlining what needs to be done to
produce a project’s requirements and deliverables is a proven technique in producing a suc-
cessful project. This process of breaking down project work is a bread-and-butter function in
the project management field.
This chapter covers the definition of project work using a top-down WBS and scheduling the
work from the bottom up. It will illustrate the process and identify ways to reflect risk and
uncertainty in the scheduling process.
6.1 The Work Breakdown Structure
A WBS is a valuable description and documentation of the work involved in producing the
project deliverable. Sometimes the WBS is easy to define, but in more complex projects it is a
complicated and detailed listing of work tasks, milestones, and resources (resources include
personnel, materials, equipment, supplies, facilities, and other assets used in a project). The
WBS is the structure of the work, not the components of the product. Although some work is
directly related to product parts, the purpose of the WBS is to enable an accounting of the costs
of the project and the sequence of work activity and resource use so these can be scheduled.
H1
sec_n sec_t
bar81677_06_c06_173-198.indd 174 9/9/14 10:52 AM
Design Develop
Get
acceptance
Deliver
New information .
Being entrusted to initiate and plan your company’s new project can be a great responsibility—and it’s something you don’t want to mess up.
Project initiation, the process by which you start a project, and project planning, the process in which you create schedules and plan a project systematically, are integral to the project management process.
Project planning, the most important phase of the project management process, should be executed well, as poor planning may lead to serious problems and setbacks later.
Below, we list the twelve steps of the project management process that can help you get started initiating and planning a successful project.
Step 1: Develop Project Charter
The first step to starting your new project is to develop your project charter. Basically, your charter will serve as your project’s mission statement and serve as your guide throughout the project. In your charter, you should define the scope of your project (what you plan to do) as well as an overview of how it will be done (who will do what).
Successful project charters are prepared from information from three main sources: contracts, Service Level Agreements (SLA), and Letters of Award.
Your contracts are the agreements between you (the service provider) and your client. Your SLA is a special type of contract in which you and your client define and agree to the scope and deliverables of the project, and your Letter of Award states that you’ve won a particular bid for the project.
Within your project charter, be sure to provide a comprehensive overview of the scope and direction of the project. Also known as your project’s content, this information is key to the success and to the professionalism of your charter.
This document signifies to your project manager that (s)he has permission to start work on the tasks, as laid out in the charter. Having a clear direction, purpose, and high-level project description can keep all parties on the same page and help your team to provide a service as agreed to with your client.
In order to do this, your charter should include any and all requirements and key deliverables as well as provide a general milestone schedule. Parties responsible for the project, such as the project manager, the project sponsor, and keyholders, should be listed.
Step 2: Identify Stakeholders
It’s imperative that you identify all stakeholders while developing your project charter. Stakeholders are any individual, group, or organization that will be affected by the outcome of the project.
In order to do this, most organizations run what’s called a stakeholder analysis. This analysis identifies the stakeholders in a project and determines what outcome the project should provide to each one.
A stakeholder register is also made. This register identifies project stakeholders and lists their influence over its outcome.
Scope refers to all the work involved in creating the products of the project and the processes used to create them. It defines what is or is not to be done
4. Proper planning of a software project unless the project is trivia.pdfeyevisioncare1
4. Proper planning of a software project unless the project is trivial in size, is obviously
important for a software project to succeed. What information must be included in software
project planning document? Explain in a paragraph or two (15pt.) 5. Risk management is one of
CMMI KPA (Key Process Area). Explain its concept in a paragraph or two (10pt.)
Solution
Typically many of the project\'s key stakeholders, that is those affected by both the project and
the project\'s end result, do not fully understand the nature of the project plan. Since one of the
most important and difficult aspects of project management is getting commitment and buying,
the first step is to explain the planning process and the project plan to all key stakeholders. It is
essential for them to understand the importance of this set of documents and to be familiar with
its content, since they will be asked to review and approve the documents that pertain to them.
Components of the Project Plan Include:
Baselines. Baselines are sometimes called performance measures, because the performance of
the entire project is measured against them. They are the project\'s three approved starting points
and include the scope, schedule, and cost baselines. These provide the \'stakes in the ground.\'
That is, they are used to determine whether or not the project is on track, during the execution of
the project.
Baseline management plans. These plans include documentation on how variances to the
baselines will be handled throughout the project. Each project baseline will need to be reviewed
and managed. A result of this process may include the need to do additional planning, with the
possibility that the baseline(s) will change. Project management plans document what the project
team will do when variances to the baselines occur, including what process will be followed,
who will be notified, how the changes will be funded, etc.
Other work products from the planning process. These include a risk management plan, a quality
plan, a procurement plan, a staffing plan, and a communications plan.
Step 2: Define roles and responsibilities. Not all key stakeholders will review all documents, so it
is necessary to determine who on the project needs to approve which parts of the plan. Some of
the key players are:
Step 3: Hold a kickoff meeting. The kickoff meeting is an effective way to bring stakeholders
together to discuss the project. It is an effective way to initiate the planning process. It can be
used to start building trust among the team members and ensure that everyone\'s idea are taken
into account. Kickoff meetings also demonstrate commitment from the sponsor for the project.
Here are some of the topics that might be included in a kickoff meeting:
Step 4: Develop a Scope Statement. The Scope Statement is arguably the most important
document in the project plan. It\'s the foundation for the rest of the project. It describes the
project and is used to get common agreement among the sta.
Operation “Blue Star” is the only event in the history of Independent India where the state went into war with its own people. Even after about 40 years it is not clear if it was culmination of states anger over people of the region, a political game of power or start of dictatorial chapter in the democratic setup.
The people of Punjab felt alienated from main stream due to denial of their just demands during a long democratic struggle since independence. As it happen all over the word, it led to militant struggle with great loss of lives of military, police and civilian personnel. Killing of Indira Gandhi and massacre of innocent Sikhs in Delhi and other India cities was also associated with this movement.
The French Revolution, which began in 1789, was a period of radical social and political upheaval in France. It marked the decline of absolute monarchies, the rise of secular and democratic republics, and the eventual rise of Napoleon Bonaparte. This revolutionary period is crucial in understanding the transition from feudalism to modernity in Europe.
For more information, visit-www.vavaclasses.com
2024.06.01 Introducing a competency framework for languag learning materials ...Sandy Millin
http://sandymillin.wordpress.com/iateflwebinar2024
Published classroom materials form the basis of syllabuses, drive teacher professional development, and have a potentially huge influence on learners, teachers and education systems. All teachers also create their own materials, whether a few sentences on a blackboard, a highly-structured fully-realised online course, or anything in between. Despite this, the knowledge and skills needed to create effective language learning materials are rarely part of teacher training, and are mostly learnt by trial and error.
Knowledge and skills frameworks, generally called competency frameworks, for ELT teachers, trainers and managers have existed for a few years now. However, until I created one for my MA dissertation, there wasn’t one drawing together what we need to know and do to be able to effectively produce language learning materials.
This webinar will introduce you to my framework, highlighting the key competencies I identified from my research. It will also show how anybody involved in language teaching (any language, not just English!), teacher training, managing schools or developing language learning materials can benefit from using the framework.
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
Unit 8 - Information and Communication Technology (Paper I).pdfThiyagu K
This slides describes the basic concepts of ICT, basics of Email, Emerging Technology and Digital Initiatives in Education. This presentations aligns with the UGC Paper I syllabus.
The Roman Empire A Historical Colossus.pdfkaushalkr1407
The Roman Empire, a vast and enduring power, stands as one of history's most remarkable civilizations, leaving an indelible imprint on the world. It emerged from the Roman Republic, transitioning into an imperial powerhouse under the leadership of Augustus Caesar in 27 BCE. This transformation marked the beginning of an era defined by unprecedented territorial expansion, architectural marvels, and profound cultural influence.
The empire's roots lie in the city of Rome, founded, according to legend, by Romulus in 753 BCE. Over centuries, Rome evolved from a small settlement to a formidable republic, characterized by a complex political system with elected officials and checks on power. However, internal strife, class conflicts, and military ambitions paved the way for the end of the Republic. Julius Caesar’s dictatorship and subsequent assassination in 44 BCE created a power vacuum, leading to a civil war. Octavian, later Augustus, emerged victorious, heralding the Roman Empire’s birth.
Under Augustus, the empire experienced the Pax Romana, a 200-year period of relative peace and stability. Augustus reformed the military, established efficient administrative systems, and initiated grand construction projects. The empire's borders expanded, encompassing territories from Britain to Egypt and from Spain to the Euphrates. Roman legions, renowned for their discipline and engineering prowess, secured and maintained these vast territories, building roads, fortifications, and cities that facilitated control and integration.
The Roman Empire’s society was hierarchical, with a rigid class system. At the top were the patricians, wealthy elites who held significant political power. Below them were the plebeians, free citizens with limited political influence, and the vast numbers of slaves who formed the backbone of the economy. The family unit was central, governed by the paterfamilias, the male head who held absolute authority.
Culturally, the Romans were eclectic, absorbing and adapting elements from the civilizations they encountered, particularly the Greeks. Roman art, literature, and philosophy reflected this synthesis, creating a rich cultural tapestry. Latin, the Roman language, became the lingua franca of the Western world, influencing numerous modern languages.
Roman architecture and engineering achievements were monumental. They perfected the arch, vault, and dome, constructing enduring structures like the Colosseum, Pantheon, and aqueducts. These engineering marvels not only showcased Roman ingenuity but also served practical purposes, from public entertainment to water supply.
Read| The latest issue of The Challenger is here! We are thrilled to announce that our school paper has qualified for the NATIONAL SCHOOLS PRESS CONFERENCE (NSPC) 2024. Thank you for your unwavering support and trust. Dive into the stories that made us stand out!
Model Attribute Check Company Auto PropertyCeline George
In Odoo, the multi-company feature allows you to manage multiple companies within a single Odoo database instance. Each company can have its own configurations while still sharing common resources such as products, customers, and suppliers.
How to Create Map Views in the Odoo 17 ERPCeline George
The map views are useful for providing a geographical representation of data. They allow users to visualize and analyze the data in a more intuitive manner.
How to Split Bills in the Odoo 17 POS ModuleCeline George
Bills have a main role in point of sale procedure. It will help to track sales, handling payments and giving receipts to customers. Bill splitting also has an important role in POS. For example, If some friends come together for dinner and if they want to divide the bill then it is possible by POS bill splitting. This slide will show how to split bills in odoo 17 POS.
2. Project Scope Management
What is Project Scope Management?
Scope refers to all the work involved in
creating the products of the project and the
processes used to create them
A deliverable is a product produced as part of
a project, such as hardware or software,
planning documents, or meeting minutes
Project scope management includes the
processes involved in defining and controlling
what is or is not included in a project
2
3. Project Scope Management
Project Scope Management Processes
Scope planning: deciding how the scope will be
defined, verified, and controlled
Scope definition: reviewing the project charter and
preliminary scope statement and adding more
information as requirements are developed and change
requests are approved
Creating the WBS: subdividing the major project
deliverables into smaller, more manageable
components
Scope verification: formalizing acceptance of the
project scope by key project stakeholders
Scope control: controlling changes to project scope
which impact project cost and time goals3
5. Project Scope Management
Scope Planning and the
Scope Management Plan
The scope management plan is a document that
includes descriptions of how the team will prepare
the project scope statement, create the WBS,
verify completion of the project deliverables, and
control requests for changes to the project scope
Key inputs include the project charter, preliminary
scope statement, and project management plan
It should be reviewed with the project sponsor to
make sure the approach meets expectations
5
6. Project Scope Management
What Went Right?
Many financial service companies use customer
relationship management (CRM) systems to improve
their understanding of and responsiveness to customers
A senior management team at the Canadian money
management company Dynamic Mutual Funds (DMF)
launched an enterprise-wide, national program to build
and manage its customer relationships
They needed a faster and more organized, highly
participative approach, so they proposed a new seven-
step concept called project scope design
DMF won an eCustomer World Golden Award for world-
class innovation
6
7. Project Scope Management
What Went Right?
The Seven Steps
1. Analyze the project atmosphere, staekholders and
centers of influence
2. Align the project scope with the organization’s strategic
objectives and business challenges
3. Determine where to add value to the business
4. Study the process flow between the business units
5. Develop an efficient communication strategy
6. Develop the project approach
7. Coordinate the new project with the other initiatives
already under way
7
10. Project Scope Management
Scope Definition and the
Project Scope Statement
The project team develops a preliminary scope
statement in initiating a project as part of the
project integration management knowledge
area
The preliminary scope statement, project
charter, organizational process assets, and
approved change requests provide a basis for
creating the more specific project scope
statement
10
11. Project Scope Management
Scope Definition and the
Project Scope Statement
Project scope statements should contain at a minimum:
Description of the project – overall objectives,
justification
Detailed descriptions of all project deliverables
Characteristics and requirements of products and
services produced as part of the project
Other helpful information:
Project success criteria
Project boundaries
Product acceptance criteria
Schedule milestones
Order of magnitude costs estimates…
11
13. Project Scope Management
Media Snapshot
Many people enjoy watching television shows like Changing Rooms
or Trading Spaces, where participants have two days and $1,000 to
update a room in their neighbor’s house. Since the time and cost are set,
it’s the scope that has the most flexibility. Designers on these shows often
have to change initial scope goals due to budget or time constraints.
Although most homeowners are very happy with work done on the
show, some are obviously disappointed. Unlike most projects where the
project team works closely with the customer, homeowners have little say
in what gets done and cannot inspect the work along the way… What
happens when the homeowners don’t like the work that’s been done? The
FAQ section of tlc.com says, “Everyone on our show is told upfront that
there’s a chance they won’t like the final design of the room. Each
applicant signs a release acknowledging that the show is not responsible
for redecorating a room that isn’t to the owner’s taste.”
Too bad you can’t get sponsors for most projects to sign a similar
release form. It would make project scope management much easier!
13
14. Project Scope Management
Work Breakdown Structure (WBS)
A WBS is a deliverable-oriented grouping of the
work involved in a project that defines the total
scope of the project
WBS is a foundation document that provides the
basis for planning and managing project schedules,
costs, resources, and changes
Decomposition is subdividing project deliverables
into smaller pieces
A work package is a task at the lowest level of the WBS
Tasks on a WBS represent work that needs to be done to
complete the project, not specifications (e.g., type of
server)
14
15. Project Scope Management
Work Breakdown Structure (WBS)
The project scope statement and project
management plan are the primary inputs for
creating a WBS
The outputs include the WBS itself, the WBS
dictionary, a scope baseline and updates to the
project scope statement and scope
management plan
The WBS is often depicted as a task-oriented
family tree of activities
The WBS can be organized around project products,
project phases or using the project management
process groups15
18. Project Scope Management
Partial Intranet WBS in Tabular Form
1.0 Concept
1.1 Evaluate current systems
1.2 Define Requirements
1.2.1 Define user requirements
1.2.2 Define content requirements
1.2.3 Define system requirements
1.2.4 Define server owner requirements
1.3 Define specific functionality
1.4 Define risks and risk management approach
1.5 Develop project plan
1.6 Brief Web development team
2.0 Web Site Design
3.0 Web Site Development
4.0 Roll Out
5.0 Support
18
21. Project Scope Management
Approaches to Developing WBSs
Using guidelines: some organizations, like the
DOD, provide guidelines for preparing WBSs
The analogy approach: review WBSs of
similar projects and tailor to your project
The top-down approach: start with the largest
items of the project and break them down
The bottom-up approach: start with the
specific tasks and roll them up
Mind-mapping approach: mind mapping is a
technique that uses branches radiating out
from a core idea to structure thoughts and
ideas21
22. Project Scope Management
Mind Mapping
Mind Mapping is a way of creating pictures
that show ideas in the same way that they
are represented in your brain.
Your brain uses words, pictures, numbers,
logic, rhythm, color and spatial awareness to
build up unique pictures of information.
The ideas are linked together in a way that
makes it easy to understand and remember.
http://www.novamind.com/mind-mapping/
http://www.youtube.com/watch?v=MlabrWv25qQ
22
24. Project Scope Management
Mind Mapping
Use just key words, or wherever possible images.
Start from the center of the page and work out.
Make the center a clear and strong visual image that depicts the general theme
of the map.
Create sub-centers for sub-themes.
Put key words on lines. This reinforces structure of notes.
Print rather than write in script. It makes them more readable and memorable.
Lower case is more visually distinctive (and better remembered) than upper
case.
Use color to depict themes, associations and to make things stand out.
Anything that stands out on the page will stand out in your mind.
Think three-dimensionally.
Use arrows, icons or other visual aids to show links between different elements.
Don't get stuck in one area. If you dry up in one area go to another branch.
Put ideas down as they occur, wherever they fit. Don't judge or hold back.
Break boundaries. If you run out of space, don't start a new sheet; paste more
paper onto the map. (Break the 8x11 mentality.)
Be creative. Creativity aids memory.
From http://www.peterrussell.com/MindMaps/HowTo.php
24
27. Project Scope Management
The WBS Dictionary and Scope Baseline
Many WBS tasks are vague and must be
explained more so people know what to do
and can estimate how long it will take and
what it will cost to do the work
A WBS dictionary is a document that
describes detailed information about each
WBS item
The approved project scope statement and its
WBS and WBS dictionary form the scope
baseline, which is used to measure
performance in meeting project scope goals
27
29. Project Scope Management
Creating a WBS and WBS Dictionary*
A unit of work should appear at only one place in the
WBS
The work content of a WBS item is the sum of the
WBS items below it
A WBS item is the responsibility of only one individual,
even though many people may be working on it
The WBS must be consistent with the way in which
work is actually going to be performed; it should serve
the project team first, and other purposes only if
practical
*Cleland, David I. Project Management: Strategic Design and Implementation, 1994
29
30. Project Scope Management
Creating a WBS and WBS Dictionary *
Project team members should be involved in
developing the WBS to ensure consistency and buy-
in
Each WBS item must be documented in a WBS
dictionary to ensure accurate understanding of the
scope of work included and not included in that item
The WBS must be a flexible tool to accommodate
inevitable changes while properly maintaining control
of the work content in the project according to the
scope statement
30
*Cleland, David I. Project Management: Strategic Design and Implementation, 1994
31. Project Scope Management
Scope Verification
It is very difficult to create a good scope
statement and WBS for a project
It is even more difficult to verify project scope
and minimize scope changes
Scope verification involves formal acceptance
of the completed project scope by the
stakeholders
Acceptance is often achieved by a customer
inspection and then sign-off on key deliverables
31
32. Project Scope Management
What Went Wrong?
A project scope that is too broad and grandiose can
cause severe problems
Scope creep and an overemphasis on technology for
technology’s sake resulted in the bankruptcy of a large
pharmaceutical firm, Texas-based FoxMeyer Drug
In 2001, McDonald’s fast-food chain initiated a project to
create an intranet that would connect its headquarters with
all of its restaurants to provide detailed operational
information in real time; after spending $170 million on
consultants and initial implementation planning,
McDonald’s realized that the project was too much to
handle and terminated it
32
33. Project Scope Management
Scope Control
Scope control involves controlling changes to the
project scope
Goals of scope control are to:
Influence the factors that cause scope changes
Assure changes are processed according to
procedures developed as part of integrated change
control
Manage changes when they occur
Tools for performing scope control include a change
control system and configuration management
Variance is the difference between planned and
actual performance33
34. Project Scope Management
Best Practices for Avoiding Scope Problems
1. Keep the scope realistic: Don’t make projects so large that
they can’t be completed; break large projects down into a
series of smaller ones
2. Involve users in project scope management: Assign key
users to the project team and give them ownership of
requirements definition and scope verification
3. Use off-the-shelf hardware and software whenever possible:
Many IT people enjoy using the latest and greatest
technology, but business needs, not technology trends, must
take priority
4. Follow good project management processes: As described in
this chapter and others, there are well-defined processes for
managing project scope and others aspects of projects
34
35. Project Scope Management
Suggestions for Improving User Input
Develop a good project selection process and insist
that sponsors are from the user organization
Have users on the project team in important roles
Have regular meetings with defined agendas, and
have users sign off on key deliverables presented at
meetings
Deliver something to users and sponsors on a
regular basis
Don’t promise to deliver when you know you can’t
Co-locate users with developers
35
36. Project Scope Management
Suggestions for Reducing Incomplete
and Changing Requirements
Develop and follow a requirements
management process
Use techniques such as prototyping, use case
modeling, and JAD to get more user
involvement
Put all requirements in writing, keep them
current and readily available
Create a requirements management database
for documenting and controlling requirements
(CASE tools)
36
37. Project Scope Management
Suggestions for Reducing Incomplete
and Changing Requirements
Provide adequate testing and conduct testing
throughout the project life cycle
Review changes from a systems perspective
Project scope changes must include associated cost
and schedule changes
Focus on approved scope goals and don’t get side
tracked
Emphasize completion dates to help focus on what’s
most important
What should we drop in order to add something new?
Allocate resources specifically for handling change
requests/enhancements like NWA did with ResNet
37
38. Project Scope Management
Using Software to Assist in
Project Scope Management
Word-processing software helps create several
scope-related documents
Spreadsheets help to perform financial
calculations and weighed scoring models, and
develop charts and graphs
Communication software like e-mail and the Web
help clarify and communicate scope information
Project management software helps in creating a
WBS, the basis for tasks on a Gantt chart
Specialized software is available to assist in
project scope management
38