MIDTERM Flashcards
1
Q
Definition of a Project
A
- a temporary endeavor undertaken to create a unique product, service, or result
- has a definite beginning and end
- ends when the project objectives are achieved (or terminated due to not achieving the project)
2
Q
What is project management?
A
the discipline of planning, organizing, securing, managing, leading, and controlling resources to achieve specific goals
3
Q
How many PMBOK processes
A
49
4
Q
How many knowledge areas
A
10
5
Q
How many process groups
A
5
6
Q
What are the 5 process groups
A
Initiating
Planning
Executing
Monitoring and Controlling
Closing
7
Q
What are the knowledge areas
A
Integration
Scope
Time
Cost
Quality
Resources
Communications
Risk
Procurement
Stakeholder
8
Q
ITTO
A
Inputs
Tools and Techniques
Outputs
9
Q
SOW
A
Statement of Work
10
Q
What is a SOW
A
a narrative description of the work to be completed if/when the project is launched
11
Q
a document that is reviewed and approved before launching a formal project
A
SOW
12
Q
Who creates the SOW (from PPT)
A
senior manager or project sponsor
13
Q
a document where the initial ideas for a project are put on paper
A
SOW
14
Q
What are included in the SOW
A
- Strategic Plan
- Business need
- Description of the product or service(scope description)
Also include: - funding constraints
- high level schedule
- deliverables
- acceptance criteria
15
Q
It shows how the project supports the overall organization
A
Strategic Plan
16
Q
What is a Project Charter
A
- a document that formally authorizes a project (or phase)
- establishes a partnership between the performing organization and the requesting organization
- formally initiates the project
- assigns a project manager (who is typically involved in creating the Charter
17
Q
What is the project life cycle
A
starts the project
organizes project
closes the project
18
Q
What are included in the Statement of Work
A
Business Need
High level schedule
funding constraints
19
Q
What is not included in the Statement of Work
A
WBS
20
Q
Project management has ____ processes organized into ____ knowledge areas and ____process groups
A
49, 10, 5
21
Q
Statements about project life cycle
A
- phases are segmented into logical subsets
- as each phase closes, a decision is needed
- milestones dictate when phases close
22
Q
the output for develop project charter
A
project charter and assumption log
23
Q
who is the requesting organization
A
client (may be internal or external)
24
Q
inputs for developing a project charter
A
business documents
agreements
enterprise environmental factors
organizational process assets
25
what business documents are needed to create a project charter
business case
benefits management plan
26
business case may include:
business justification for the project
feasibility analysis
needs assessment
situation analysis
cost-benefit analysis
27
What are considered as business needs
market demand
organizational need
customer request
technological advance?
legal requirement
28
what is a benefits management plan
a plan that shows how and when the project benefits (outcomes of value to stakeholders) will be delivered
29
examples of agreements
Memorandums of Understanding
letters of intent
30
What are included in the Organizational Process Assets
- organizational processes and procedures for conducting project work (ex. templates, policies, procedures)
- organizational knowledge stored in databases and historical files (ex. past project files, cost databases)
31
What are Enterprise Environmental Factors
conditions that constrain or influence the project success such as organizational structure, market conditions, industry characteristics/environment, political climate, project management software or information system, government/industry standards or requirements
32
What are the tools and techniques in creating a project charter
- expert judgment
- data gathering
- interpersonal and team skills
- meetings
33
what are the data gathering techniques to create a project charter
brainstorming
focus groups
interviews
34
what interpersonal and team skills are needed to develop a project charter
conflict management
facilitation
meeting management
35
what is an assumption log
a document which the project manager and team use to capture, document, and track assumptions throughout the project's lifecycle
36
Also known as traditional or predictive projects
waterfall projects
37
characteristics of waterfall projects
- generally sequential
- project activities are planned at the start and executed as the project progresses
38
Also known as adaptive or iterative projects
agile projects
39
It uses a different methodology, with successive planning/execution cycles
agile
40
project management methodology used in Europe
PRINCE2
41
triple constraints
scope, cost, schedule
42
a formal, approved document that defines how the project is executed, monitored, and controlled
Project Management Plan
43
Inputs for developing Project Management Plan
project charter
outputs from other processes
enterprise environmental factors
organizational process assets
44
Tools and Techniques used to create Project Management Plan
expert judgment
data gathering
interpersonal and team skills
meetings
45
Data gathering techniques used to create Project management Plan
brainstorming
checklists
focus groups
interviews
46
Types of components that can be seen in a project management plan
scope management plan
cost management plan
change management plan
risk management plan
procurement management plan
quality management plan
lifecycle descriptions
baselines
47
It tells you what it is you are creating or building, what it is you are trying to accomplish
Scope (of a project)
48
the set of project management processes concerned with the determining and managing WHAT IS and WHAT IS NOT included in the project and product
Scope Management
49
6 processes related to scope management
1. plan scope management
2. collect requirements
3. define scope
4. create WBS
5. validate scope
6. control scope
50
a process which shows how the scope is going to be managed for the project
plan scope management
51
the process of defining and documenting stakeholder needs, to meet the project objective
collect requirements
52
- a process that produces a "Scope Statement", which is the master blueprint for the project and product
- develop a detailed description of the project or product
Define scope
53
the process of producing a detailed breakdown of work elements of the project
Create Work Breakdown Structure (WBS)
54
the process of obtaining the approval for the client for the deliverables that are produced
Validate Scope
55
the process of comparing the actual results to planned results
Control Scope
56
Outputs for Plan Scope Management
1. scope management plan
2. requirements management plan
57
describes how the scope will be defined, developed, monitored, controlled, and verified
Scope Management Plan
58
Scope Management Plan includes:
- how the detailed scope statement be prepared
- How will the WBS be prepared
- how the deliverables be accepted
- how changes to scope be handled
59
describes how the requirements will be identified, analyzed, documented, and managed
Requirements Management Plan
60
Requirements Management Plan includes:
- how the requirements activities be planned, tracked, and reported
- who will be involved in each tasks
- how will the priorities be determined
- RACI chart
61
RACI
Responsible, Accountable, Consult, Inform
62
Responsible in RACI means:
someone who performs the task or activity
63
Accountable in RACI means:
someone who makes the decisions (decision maker)
64
Consult in RACI
someone who will be asked/consulted before proceeding to the next level
65
Inform in RACI
who we let know after all is done
66
2 common classifications of requirements
Functional and Non-functional
67
Observable tasks or processes that must be performed by the system
Functional
68
requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors
Non-functional
69
person who identifies and defines solutions that deliver value to stakeholders
business analyst
70
Responsibilities of a business analyst
collecting, analyzing, managing, and communicating project requirements from stakeholders
71
body of knowledge used by business analysts
BABOK
72
Collect Requirements tools and techniques
expert judgment
data gathering
data analysis
decision making
data representation
interpersonal and team skills
context diagram
prototype
73
statements of fact and assumptions that define the expectations of the system in terms of mission objectives, environment, constraints, and measures of effectiveness and suitability
Customer requirements
74
It explains what has to be done by identifying the necessary system architecture of a system
Architecture Requirements
75
It explains what has to be done by identifying the necessary structure of a system
Structural Requirements
76
It explains what has to be done by identifying the necessary behavior of a system
Behavioral Requirements
77
the extent to which a mission or function must be executed; generally measured in terms of quantity, quality, coverage, timelines, and readiness
Performance Requirements
78
the "build to", "code to", and "buy to" requirements for products and "how to execute" requirements for processes expressed in technical data packages and technical manuals
Design Requirements
79
requirements that are implied or transformed from higher-level requirement
Derived Requirements
80
Requirement that is established by dividing or otherwise allocating a high-level requirement into multiple lower-level requirements
Allocated Requirements
81
refers to technical subject matter expertise, facilitation expertise, etc
Expert Judgment
82
data gathering methods
interviews, focus groups, questionnaires/surveys, benchmarking, brainstorming
83
refers to document analysis
data analysis
84
methods of decision making
voting, multi-criteria decision making
85
data representation methods
affinity diagrams, mind mapping
86
what interpersonal and team skills are needed to collect requirements
nominal group technique, observation/conversation, facilitation (workshops, collaborative construction of personas, user stories, use case diagrams)
87
a type of data gathering technique where a group of people are asked about their perceptions, opinions, beliefs, and attitudes
Focus groups
88
4 steps in conducting interviews and focus groups
1. prepare a plan
2. create questions
3. conduct interviews/focus groups
4. summarize the responses
89
Comparing actual or planned practices to those of comparable products to identify best practices, generate ideas for improvement, or providing a basis for measuring performance
Benchmarking
90
Sharing your ideas no matter how crazy they sound (data gathering technique)
Brainstorming
91
Results are tabulated and a summary of aggregated findings are produced (often using statistical procedures),
quick, cheap, can get information for a large sample group
Questionnaires/Surveys
92
Scaling method used in questionnaires and surveys
Likert Scale
93
Analyzing existing documents to identify information relevant to project requirements (ex. building codes, other regulatory information, problem/issue logs)
Document analysis
94
Everyone agrees on the requirement
Unanimity
95
more than 50% of the people agree on the requirement
Majority
96
when there's a choice of options, the choice that gets the most votes is the winner (even though it might not have received the numerical majority of votes)
Plurality
97
Making decisions about what criteria are more important than others (weighted criteria)
Multi-Criteria Decision Analysis
98
matrix used in multi-criteria decision analysis
Weighted Decision Matrix
99
Ideas are grouped into their natural relationships
Affinity Diagrams
100
A visual or graphic way to represent groupings of ideas, using branches or sub-branches
Mind Maps
101
A full-scale working model of something built for study, testing, or display
Prototype
102
Steps in Nominal Group Technique
1. Introduce and explain
2. Let members generate ideas silently
3. Share ideas
4. Discuss each ideas as a group
5. Vote and rank ideas
103
View individuals in their natural environment to understand how they behave, used when it is difficult for a user to articulate what they are doing
Observation
104
Observation is sometimes called what?
Job Shadowing (may be done undercover)
105
It's when people change their behavior/action if they know that they are being watched
Drawback
106
To identify and clarify requirements so they are clearly understood by the project team when documented
Facilitation
107
High-level visual maps of a system and how other people or other systems interface with it, including inputs, actors, and outputs
Context Diagrams
108
Imaginary representation of a user role
Persona
109
A concise statement of functionality or quality needed to deliver value to a specific stakeholder
user stories
110
a data representation that defines a goal-oriented set of interactions between external actors and the system under consideration
Use Case
111
MCQ
The project lifecycle
a. organizes the project
b. closes the project
c. starts the project
d. all of the above
d.
112
MCQ
Which of the following may not be included in the Statement of Work?
a. Work Breakdown Structure
b. High level schedule
c. business need
d. funding constraints
a.
113
MCQ
Project Management has ___ processes organized into ___ knowledge areas and ___process groups
a. 10, 5, 49
b. 5, 49, 10
c. 49, 10, 5
d. 10,49, 5
c.
114
MCQ
Which of the following statements about project lifecycle is false?
a. phases are segmented into logical subsets
b. there is a set number of phases
c. As each phase closes, a decision is needed
d. milestones dictate when phases close
b.
115
MCQ
The output of Develop Project Charter is
a. Project Charter and SOW
b. Project Charter and Assumption Logs
c. Project Charter and Scope Definition
d. Project Charter
b.
116
MCQ
Which of the following is not an input to the project charter?
a. stakeholder communication plan
b. letters of intent
c. feasibility analysis
d. templates and company policies
a.
117
MCQ
Which is not a tool and technique for Planning Scope management?
a. Data gathering
b. expert judgment
c. meetings
d. alternatives analysis
a.
118
MCQ
What does RACI mean?
a. Responsible, Assessed, Consulted, Included
b. Responsible, Accountable, Consult, Inform
c. Required, Accountable, Confirm, Inform
d. Required, Acknowledged, Clarified, Indicated
b.
119
True or False
A closed end question can be answered with a limited set of possible responses.
true
120
MCQ
What is the 4 step process for using focus groups?
a. plan questions, create groups, conduct focus groups, summarize results
b. create questions, plan focus group, conduct focus group, summarize results
c. plan focus group, create questions, conduct focus group, summarize results
d. plan focus group, plan questions, conduct focus group, summarize result
c.
121
MCQ
Which of the following is a non-functional requirement?
a. 4 second "click to glass" response time
b. ability to print invoice
c. email and username display
d. high contrast white background
a.
122
True or False
"How badly did you do on the test?" is a good example of a closed ended question.
False
123
True or False
An open ended question is better for conducting focus groups
True
124
MCQ
Which of the following is NOT a tool and technique for Collect Requirements?
a. expert judgment
b. prototypes
c. data representation
d. product analysis
d.
125
MCQ
You've been hired as a PM after the charter is complete. The sponsor wants to add more requirements. What should you do?
a. Review the business case
b. review the SOW
c. Submit a change request
d. Review the Charter
b.
126
MCQ
A use case in which the actors does not interact within the system is called
a. Independent activity
b. solitary interaction model
c. asynchronous system
d. neutrino complex
c.
127
MCQ
"When the zoo closes, the animals have a party" is an example of a disadvantage of which tool and technique?
a. Nominal Group technique
b. Observation
c. Case Studies
d. Facilitated workshops
b.
128
MCQ
Data mining, validating interviews, and studying org charts is an example of
a. document analysis
b. mind mapping
c. alternative analysis
d. multi-criteria decision making
a.
129
MCQ
Which of the following is not an input of Plan Scope management?
a. project Charter
b. Project management plan
c. requirements management plan
d. organizational process assets
c.
130
MCQ
Which of the following statements about Surveys is false?
a. relatively inexpensive to administer
b. easier to collect information from a large audience
c. typically requires a significant amount of time from respondents
d. effective for stakeholders who are geographically dispersed
c.
131
MCQ
Which of the following statements about benchmarking is incorrect?
a. competitors are not considered industry leaders
b. determines gaps between current and best practice
c. requires a survey of selected enterprise to understand practices
d. requires identification of areas to be studied
a.
132
MCQ
Which of the following statements about tools and techniques is true?
a. Mind maps are not effective communication tools
b. business analysts do not need to create content when using document analysis
c. brainstorming does not produce diverse results
d. prototypes do not provide a valid representation of future state
b.
133
MCQ
What is the most effective method to teach North American students?
a. satellite mind control
b. funny cartoon
c. smart pills
d. subliminal messages
b.
134
Non Functional Category:
degree to which the solution is operable and accessible when required for use, often expressed in terms of percent of time the solution is available
Availability
135
Non Functional Category:
degree to which the solution operates effectively with other components in its environment, such as one process with another
Compatibility
136
Non Functional Category:
degree to which the solution functions meet user needs, including aspects of suitability, accuracy, and interoperability
Functionality
137
Non Functional Category:
ease with which a solution or component can be modified to correct faults, improve performance or other attributes, or adapt to a changed environment
Maintainability
138
Non Functional Category:
degree to which a solution or component performs its designated functions with minimum consumption of resources. Can be defined based on the context or period, such as high-peak, mid-peak, or off-peak usage
Performance Efficiency
139
Non Functional Category:
ease with which a solution or component can be transferred from one environment to another
portability
140
Non Functional Category:
ability of a solution or component to perform its required functions under stated conditions for a specified period of time, such as mean time to failure of a device
Reliability
141
Non Functional Category:
degree to which a solution is able to grow or evolve to handle increased amount of work
Scalability
142
Non Functional Category:
Aspects of a solution that protect solution content or solution components from accidental or malicious access, use, modification, destruction, or disclosure
Security
143
Non Functional Category:
ease with which a user can learn to use the solution
usability
144
Non Functional Category:
constraints on the solution that are necessary to meet certain standards or industry conventions
Certification
145
Non Functional Category:
regulatory, financial, or legal constraints which can vary based on the context or jurisdiction
Compliance
146
Non Functional Category:
requirements dealing with the local languages, laws, currencies, cultures, spellings, and other characteristics of users, which requires attention to the context
Localization
147
Non Functional Category:
constraints of the organization being served by the solution that are formally agreed to by both the provider and the user of the solution
Service Level Agreements
