Shared Flashcard Set

Details

PgMP Study
Based on SPMv3
367
Business
Professional
04/03/2014
Click here to study/print these flashcards.

Create your own flash cards! Sign up here.

Additional Business Flashcards

 

 

Cards

Term
1.
 Definition
The standard for program management 3rd edition (SPMv3) defines a program as “A group of related projects, subprograms, and program activities, managed in a coordinated way to obtain benefits not available from managing them individually.”
Term
2.
 Definition
Organizational strategy establishes the foundation for program and portfolio management.
Term
3.
 Definition
The role of the executive sponsor, as part of the governance board/ steering committee, is to document the intended benefits to be delivered and to develop meaningful measures and metrics that will be used to evaluate the progress against the program intended objectives and benefits.
Term
4.
 Definition
The primary context for program management within an organization is the planning and performance against organizational strategy.
Term
5.
 Definition
Once program goals and benefits have been defined, structured plans are developed to execute individual plan.
Term
6.
 Definition
The primary purpose of the program definition phase is to progressively elaborate the strategic objectives to be addressed by the program, define the expected outcomes, and seek program approval.
Term
7.
 Definition
Program activities seldom directly support individual program components as the components implement and support their own activities.
Term
8.
 Definition
While risk control is performed at the component level, the program monitors the result and ensures overall risk management and control.
Term
9.
 Definition
During organization's portfolio review process, programs are reviewed to ensure the program's business case, charter, and the Benefit Realization Plan (BRP) reflects the current and most recent profiles of the intended outcomes.
Term
10.
 Definition
A key difference between program and project management is the strategic focus of programs.
Term
11.
 Definition
The more mature an organization is in terms of program management, the more likely it is to have a formalized selection process.
Term
12.
 Definition
Program mandate: A document defining the strategic objective and benefits the program is expected to deliver to confirm commitment of resources to the program and triggers the Initiation Phase.
Term
13.
 Definition
The program is defined in terms of the expected outcomes, resources needed, and the complexity for delivering the changes needed to implement new capabilities across the organization.
Term
14.
 Definition
Environmental assessments are conducted to provide inputs that ensure the business case, program plan, and roadmap. It also provides the right value based on the environment in which the program will be operated to deliver the expected benefits.
Term
15.
 Definition
The program management plan establishes the outline used to achieve organizational strategy and objectives through program implementation.
Term
16.
 Definition
The Vision, Mission, and Goals and Objectives are part of the Program Plan as part of Strategy Alignment.
Term
17.
 Definition
The program plan, prepared in the program preparation sub-phase, is the overall documented reference by which programs will measure its success.
Term
18.
 Definition
The program plan provides authority for constituent subprograms, projects to be initiated as well as the framework by which these program components will be managed and monitored.
Term
19.
 Definition
Feasibility study is meant to clarify and define program objectives, requirements and risks.
Term
20.
 Definition
Studies can support the business case by providing information such as scope, cost, environmental factors, feasibility, political climate that may impact the program.
Term
21.
 Definition
Program vision acts as a constant reminder of the objectives and intended benefits of the program.
Term
22.
 Definition
Roadmap is used for effective governance by showing how components are organized within major stages or blocks.
Term
23.
 Definition
Environmental Assessment include : 1) Enterprise Environmental Factors( business environment, market, funding, resource, industry, cultural diversity, geographic diversity, regulatory, legislative, growth, supply base, technology, and risk) 2)Environmental Analysis( comparative advantage analysis, SWOT, Assumptions, Feasibility Study, Historical information).
Term
24.
 Definition
The ongoing management of programs includes active and continual monitoring of the business environment, program functional requirements, and BRP to ensure strategic objectives.
Term
25.
 Definition
The program plan (business case, vision, mission, goals and objectives) is an input to the definition phase. The output is the roadmap, charter, and program management plan.
Term
26.
 Definition
Before presenting opportunities to steering committee, consult with your sponsor as he will be able to tell you what to do next.
Term
27.
 Definition
The portfolio manager makes sure that projects and programs directly support business objectives.
Term
28.
 Definition
Program success depends on funding and available resources.
Term
29.
 Definition
The purpose of program benefit management is to focus Stakeholders (SHs) on the outcomes and benefits to be provided by the program.
Term
30.
 Definition
Benefits realized by the organization performing the program are: expanded market presence, improved financial performance, operational efficiencies, and consistently deliver and sustain the resulting products, services or capabilities produced.
Term
31.
 Definition
The roadmap may be defined to produce incremental benefits and begin to realize ROI that may help fund the future program benefits and outcome.
Term
32.
 Definition
As incremental benefits are produced, the intended recipients should be prepared for the resulting change and are able to sustain the incremental benefits.
Term
33.
 Definition
Benefit identification: identify and qualify benefits.(check identify and quantify benefits)
Term
34.
 Definition
Benefit analysis and planning: Derive & prioritize components, Derive benefits metrics, Establish benefit realization & monitoring, Map benefits into program plan (DDEM).
Term
35.
 Definition
Benefit Delivery: Monitor components, Maintain benefit register, Report benefits (MMR).
Term
36.
 Definition
Benefit transition: Consolidate coordinated benefits, Transfer the ongoing responsibility (CT).
Term
37.
 Definition
Benefits sustainment: Monitor performance of benefits, Ensure continued realization of benefits (ME).
Term
38.
 Definition
The Benefit Realization Plan (BRP) is also used during program delivery phase to verify that benefits are being realized as planned.
Term
39.
 Definition
The BRP define each benefit and associated assumptions, and determine how each benefit will be achieved.
Term
40.
 Definition
BRP defines how and when benefits will be delivered. Serves as baseline with the existing metrics and roles and responsibilities. It is communicated to stakeholders (SHs) for metrics approval.
Term
41.
 Definition
The BRP defines how the resulting benefits and capabilities will be transitioned into an operational state to achieve benefits.
Term
42.
 Definition
The benefit register is updated during benefit analysis and planning by mapping benefits to the program components based on the program roadmap.
Term
43.
 Definition
Tools to monitor benefits are: variance analysis, what if scenarios, simulations, and causal analysis.
Term
44.
 Definition
Program progress is recorded in the benefit register in the benefit delivery phase.
Term
45.
 Definition
The benefit delivery phase ensures that there is a defined set of reports or metrics reported to the PMO, program governance board, program sponsors, and other program SHs.
Term
46.
 Definition
Benefit transition may be performed following the close of an individual program component.
Term
47.
 Definition
Transition may be formal activity between functions within one organization or contract-based with an entity outside the organization.
Term
48.
 Definition
In benefit sustainment, you may need to develop business case to provide additional functionality to meet evolving requirements.
Term
49.
 Definition
The primary objective of Stakeholders (SHs) engagement is to gain and maintain buy-in for the program objectives, benefits and outcome.
Term
50.
 Definition
Stakeholders (SHs) engagement concerns negotiation of objectives, agreement of sought benefits, commitment to resources, and ongoing support throughout the program.
Term
51.
 Definition
CRM is useful when identifying SHs and mapping their relationship to the program.
Term
52.
 Definition
The program manager engages SHs by assessing their attitudes towards the program and change readiness.
Term
53.
 Definition
Leadership skills is required to set clear SHs engagement goals for the program team to address the change the program will bring.
Term
54.
 Definition
The Stakeholders (SHs) register, created through detailed SHs analysis, lists the SHs and categorize their relationship to the program, their ability to influence the program outcome, their degree of support for the program, and other attributes as decided by the program manager.
Term
55.
 Definition
Stakeholder register is an output of both Communication Planning (to document information requirements) and S.H identifications.
Term
56.
 Definition
SHs Map visually represents the interaction of all SHs current and desired support and influence; high power and high interest manage closely, high power and low interest keep satisfied, low power and high interest keep informed, low power and low interest manage with minimum effort. For the SHs Map please refer to P47-SPMv3.
Term
57.
 Definition
SHs register should not be accessible to all as it may contain politically or legally sensitive information.
Term
58.
 Definition
Program Sponsor is ultimately responsible for delivering program benefits.
Term
59.
 Definition
Program Governance board is responsible to achieve program goals.
Term
60.
 Definition
The customer can judge whether the program is successful or not.
Term
61.
 Definition
Impacted competitors may be managed as SHs.
Term
62.
 Definition
Brainstorming sessions among the initial program team are useful in SHs identification.
Term
63.
 Definition
In SHs engagement planning, the SHs register is analyzed with consideration of the organization strategic plan, program charter, and program business case to understand the environment in which the program will operate.
Term
64.
 Definition
The SHs engagement plan provides critical information to develop the communication management plan.
Term
65.
 Definition
Questions raised by SHs should be captured and published in a way that will allow multiple SHs to benefit from the exchange.
Term
66.
 Definition
To help defuse SH opposition to the program, program manager needs to utilize strong communication, negotiation, and conflict resolution skills. For large programs with diverse SH groups, facilitated negotiation sessions may be required.
Term
67.
 Definition
The program manager must define how conflicts will be managed among SHs and should include escalation path to ensure that stalemates do not occur.
Term
68.
 Definition
Negotiation and influence skills are required in stakeholder engagement.
Term
69.
 Definition
Program charter and business case (which contain risks, dependencies and benefits) will help set SHs expectations.
Term
70.
 Definition
Decision making SHs should be provided with adequate information to make the right decision at the right time necessary to move the program forward (e.g. Dashboard, EAC, and VAC).
Term
71.
 Definition
The primary metrics for SH engagement are positive contribution to the realization of program's objectives and benefits, SH participation, and frequency and rate of communication with the program team.
Term
72.
 Definition
Use an issues log to document and track SHs feedback. Impact analysis techniques should be used to understand the urgency and probability of SHs issues and determine which issues may turn into program risks.
Term
73.
 Definition
Program managers review SHs metrics regularly to identify potential risks caused by lack of participation from SHs. Root-cause analysis is used to identify and address causes of non-participation.
Term
74.
 Definition
Program Performance reporting provide SHs with information about how resources are being used to deliver program benefits.
Term
75.
 Definition
Through information distribution activity, SHs will get timely and accurate information in a useful format about the program status. Program team will also get information about the performance of the program.
Term
76.
 Definition
Effective program governance support the success of programs by: ensuring that the goals of the program remain aligned with the strategic vision, operational capabilities, and resource commitments of the sponsoring organization.
Term
77.
 Definition
The governance model should be designed with a strong understanding of the organizational culture, hierarchy, politics, relationships, vendors, and partners, along with internal and external alliances. Pratt_2011.
Term
78.
 Definition
Governance decision forums focus on facilitating the adaptive realignment of program approach to enable the delivery of intended program benefits.
Term
79.
 Definition
Governance Board is composed of executive SHs who have been selected for their strategic insights, technical knowledge, functional responsibilities, operational accountabilities, and so on.
Term
80.
 Definition
In circumstances where there are more than one single program governance board (GB), systems and methods for program governance and authority for decision making should be clearly established.
Term
81.
 Definition
Governance approves the framework by which components will be measured.
Term
82.
 Definition
Governance board (GB) responsibilities: 1) Vision and goal of the organization. 2) Program approval, endorsement, and initiation (charter approval & business case approval). 3) Program funding (funding may have limitations due to law, regulations and other limitations). 4) Establishing a program governance plan. 5) Program success criteria, communication, and endorsement. 6) Approving program approach and plans. 7) Program performance support (through allocation of organization resources). 8) Program reporting and control processes. 9) Program quality standards and planning (quality is often planned at the component level, but sometimes need to be planned at program level). 10) Monitoring program progress and need for change. 11) Phase gate and other decision point reviews. 12) Approving component initiation or transition. 13) Program Closure.
Term
83.
 Definition
Vision and goals of the program is the responsibility of the program GB, alignment of the program goal with the organization goals is the responsibility of the program manager.
Term
84.
 Definition
Vision and goals provide the basis for strategic mandates that drive initiation of most programs.
Term
85.
 Definition
Phase gate reviews provide an opportunity to assess whether a program is delivering benefits in accordance with the program benefit management plan.
Term
86.
 Definition
Initiation of components is based on the business case.
Term
87.
 Definition
Programs provide business value to the sponsoring organization.
Term
88.
 Definition
The initiation of a program component may require additional governance structure for monitoring and managing the component, and commitment of organizational resources for its completion.
Term
89.
 Definition
Recommendation for program closure must be consistent with the organization vision and strategy.
Term
90.
 Definition
PMIS enable collection, access, reporting, and analysis of information relevant to the management of programs and projects within the portfolio.
Term
91.
 Definition
Escalation approach can be part of the risk management plan.
Term
92.
 Definition
Knowledge management (KM) involves knowledge collected and shared across the program, individuals and SMEs who possess specific elements of program knowledge, and PMIS where KM and program artifacts are stored.
Term
93.
 Definition
Knowledge management (KM) includes the activities associated with timely identification, storage and delivery of key knowledge to SHs to support decision making.
Term
94.
 Definition
The governance function ensures programs are prepared for audits that are required or desired.
Term
95.
 Definition
Program audits focus on program finances, management processes and practices, program quality, and program documentation.
Term
96.
 Definition
Information repository is created by the program governance function as an infrastructure to support the organization preparedness for audit.
Term
97.
 Definition
The program typically begins when funding is approved or when program manager is assigned.
Term
98.
 Definition
When the program is not authorized the decision should be recorded in the charter & stored in the lessons learned (LL).
Term
99.
 Definition
The portfolio management activity develops concept, scope framework, initial requirements, timelines, deliverables, and acceptable cost guidelines.
Term
100.
 Definition
The primary purpose of the definition phase is to elaborate the business case or strategic plan objectives and expected program outcomes. The output is approval of program management plan.
Term
101.
 Definition
Component planning and authorization involves formalizing the scope of the work to be accomplished and identifying the deliverables that will satisfy the program goals and benefits.
Term
102.
 Definition
The output of Comm. Planning is the Comm. Plan, Stakeholders Register and Comm. Requirements.
Term
103.
 Definition
The program manager should translate program strategic goals into day-today tactical and operational activities by creating a detailed program management plan.
Term
104.
 Definition
Use communication Strategy as a quick reference to ensure that appropriate message is delivered to the correct audience and to communicate to a wide range of stakeholders.
Term
105.
 Definition
The communication strategy should be updated regularly as audiences and messages change.
Term
106.
 Definition
An initial cost estimate is prepared in the program definition phase to determine the feasibility of the organization's ability to perform the program.
Term
107.
 Definition
Calculating full lifecycle cost and including sustainment cost result in total cost of ownership (TCO). TCO is a technique to derive program cost estimates and used as a program selection criterion.
Term
108.
 Definition
The type of program and the funding structure dictate the financial environment for the duration of the program.
Term
109.
 Definition
Timing and source of funding have direct impact on the program to perform.
Term
110.
 Definition
Program Financial Framework coordinates funding, determines constraints, and determines how the money is paid out.
Term
111.
 Definition
If changes are identified as financial framework is prepared, the program manager should revise the business case and involve the decision makers in its revision, revise Comm. & SHs Engagement plans.
Term
112.
 Definition
The financial management plan describes the management of items such as risk reserves, cash flow problems, inflations, currency devaluation, contract incentive and penalty clauses, etc.
Term
113.
 Definition
The business case is updated when the charter is either approved or rejected.
Term
114.
 Definition
In component cost estimating, it is a generally accepted practice to calculate an estimate as close to the beginning of the work effort as possible.
Term
115.
 Definition
Financial tracking and monitoring is the responsibility of the program manager with oversight by the governance board.
Term
116.
 Definition
The purpose of program initiation is to define the program, secure financing, and demonstrate how the program will deliver the desired organizational benefits.
Term
117.
 Definition
Program management plan development is an iterative activity as competing priorities, assumptions, and constraints are resolved to address business goals, deliverables, benefits, time, and cost.
Term
118.
 Definition
After business case is prepared, a high level requirement is determined.
Term
119.
 Definition
As part of the program charter SHs consideration should be complemented with a draft of the program communication management plan.
Term
120.
 Definition
The program infrastructure development includes program organization and core team assignments, resource plan development, activity definition, PMO, and PMIS.
Term
121.
 Definition
A component initiation request is presented by the component manager or sponsor. Component initiation maybe delayed or accelerated as defined by program team and its needs.
Term
122.
 Definition
Performance reports contain what work has been accomplished, earned value status, remaining work, risks, issues, and change under consideration.
Term
123.
 Definition
Resource availability is a key factor to determine whether or not to conduct procurement.
Term
124.
 Definition
(RFI), feasibility study, trade study and market analysis are analysis of alternatives to formulate requirements and identify qualified sellers to support procurement.
Term
125.
 Definition
Qualified seller list facilitates procurement process, it is used to issue RFP
Term
126.
 Definition
Make or buy and PWBS chart aid in the program procurement management plan.
Term
127.
 Definition
Address commonalities among components to best determine procurement approaches.
Term
128.
 Definition
Key aspect of conducting program procurement is to set standard for components such as blanket purchase agreement, qualified seller list, pre-negotiated contracts and formalized proposal agreement.
Term
129.
 Definition
A best practice is to centralize procurement to be conducted by program team rather than to assign that responsibility to be handled by individual components.
Term
130.
 Definition
Administration and closeout of contracts is the responsibility of individual components.
Term
131.
 Definition
Before closing procurement contracts, ensure that all deliverables have been satisfactorily completed, all payments have been made, and that there are no outstanding contractual issues.
Term
132.
 Definition
One way to improve quality is to set standards that are relevant to the entire program.
Term
133.
 Definition
The quality management plan provides the quality assurance control that will be placed on the program and the methods of inspection based on the program scope.
Term
134.
 Definition
Within a program there are many differing quality assurance requirements.
Term
135.
 Definition
If new laws and specifications are introduced, new quality control tools and techniques must be introduced. Quality assurance audits will ensure proper updates are being performed.
Term
136.
 Definition
Once the initial quality assurance specifications are determined, Quality should be continuously monitored and analyzed.
Term
137.
 Definition
Through program quality control activity, the program manager can know whether quality plans are implemented by all projects in the program.
Term
138.
 Definition
In resource planning, historical information is useful to determine the type of resources required for similar projects and programs.
Term
139.
 Definition
SOW can be used to contract necessary resources.
Term
140.
 Definition
In resource prioritization and optimization, the program manager identify, document, and assign roles and responsibilities. The output is the resource plan and resource priorities.
Term
141.
 Definition
Program resource requirements identify resources required by the program. This includes roles and necessary competencies, experience and capabilities.
Term
142.
 Definition
Resource Interdependency is achieved by controlling schedule for scarce resources. Resources are released for other programs when they are no longer necessary for the current program.
Term
143.
 Definition
The program manager should ensure the PWBS accounts for timed use of scarce resource when developing schedule.
Term
144.
 Definition
Assumption analysis is a tool to identify risk.
Term
145.
 Definition
Resources of risks are program components and their interactions with each other, technical complexities, schedule and/or cost constraint, and the broader environment of the program.
Term
146.
 Definition
Program risk situations, risk plans, and effectiveness of ongoing or completed risk responses should be part of program reviews.
Term
147.
 Definition
All modifications resulting from program reviews and other changes in risks should be entered in the risk response plan.
Term
148.
 Definition
Risk control involves implementing the actions and contingency plans contained in the risk response plan.
Term
149.
 Definition
Organizations may have predefined approaches to risk management such as risk categories, common definition of concepts and terms, risk statement formats, roles and responsibilities, standard templates, and authority levels for decision making.
Term
150.
 Definition
The format of the risk statement should be consistent. This allows for the comparison of risk events in the program.
Term
151.
 Definition
Initial risk assessment is an activity conducted to determine the probability of benefit delivery.
Term
152.
 Definition
Risks profiles may be expressed in policy statements or revealed in actions.
Term
153.
 Definition
Risk targets and risk thresholds can influence the program management plan.
Term
154.
 Definition
Contingency plan is for known-unknown, management reserve is for unknown-unknown. Mitigation, avoidance and acceptance are for Known-Known risks.
Term
155.
 Definition
Five factors to consider by program team in program risk analysis are: 1) availability of information, 2) availability of resources, 3) time and cost, 4) quality of information, and 5) control.
Term
156.
 Definition
Risk monitoring is conducted to determine if program assumptions are still valid, proper risk management procedures and policies are followed, assessed risks has changed from its prior state , and cost or schedule contingency reserves are modified in line with the risks of the program.
Term
157.
 Definition
Program Innovative Strategy is meant to reserve a budget for opportunity development and engagement of project team and stakeholders to compensate for threats and efficiency losses.
Term
158.
 Definition
Program schedule planning begins with the scope management plan and PWBS.
Term
159.
 Definition
The program's delivery date and the major milestones are determined using the program roadmap and program charter.
Term
160.
 Definition
Program master schedule should include component milestones that represent an output to the program or that share interdependency with other components.
Term
161.
 Definition
The program master schedule determines the timing of individual components. Benefits should be on the critical path.
Term
162.
 Definition
The program schedule management plan identifies the agreed- upon sequence of component deliverables to facilitate effective planning of the individual components deliverables.
Term
163.
 Definition
Schedule standards for components are included in the program schedule management plan.
Term
164.
 Definition
Changes in the program master schedule MIGHT require changes in the program roadmap, and changes in the program roadmap SHOULD be reflected in the program master schedule.
Term
165.
 Definition
Approval of deviations to component schedules may be necessary to realize program benefits as a result of component performance deviation.
Term
166.
 Definition
Program scope definition activity starts with the program charter, program scope statement, and the benefit realization plan.
Term
167.
 Definition
The PWBS provides an overview of the program and shows how each component contributes to the objectives of the program.
Term
168.
 Definition
When the PWBS is developed, decomposing stops at a level of control desired by the program manager, typically the first one or two levels of the components.
Term
169.
 Definition
The purpose of program scope statement is to establish the program direction and its proposed accomplishments. It is the basis for future program decisions and articulates scope of the program.
Term
170.
 Definition
PWBS formalizes scope and used to build realistic schedule and develop cost estimates. It provides the framework for reporting tracking and controlling.
Term
171.
 Definition
In scope control, when changes are accepted and approved, the program management plan and scope statement are updated. The program manager should determine which components are affected and update the PWBS accordingly.
Term
172.
 Definition
As Benefit Realization Plan (BRP) is updated, also the roadmap should be updated.
Term
173.
 Definition
Component Governance focus on control while Program Governance focus on changing strategies.
Term
174.
 Definition
A roadmap is a good tool for programs that last for long time. Roadmap has documented success criteria for each event.
Term
175.
 Definition
After Skill set inventory (what skills set each team member has) is completed, team assignments can be made.
Term
176.
 Definition
Improve team motivation by developing compensation, incentive, and career alignment plans.
Term
177.
 Definition
Roadmap indicates the timing of the components to be initiated.
Term
178.
 Definition
The most significant change requests are those affect resource use, strategy, or plans.
Term
179.
 Definition
Residual activities may be required to oversee the ongoing benefits.
Term
180.
 Definition
There are three types of programs; Strategic, Compliance and Emergent program. After an emergent program is recognized, initiating activities must be done to clarify program objectives and align the program with the organization's strategic objectives.
Term
181.
 Definition
Regardless of how the program was initiated (Strategic, Emergent, or Compliance) it is important to develop the program definition and initiative activities, including the business case and benefit realization plan.
Term
182.
 Definition
PWBS encompasses all benefits to be delivered.
Term
183.
 Definition
Use focus group (deeper understanding), questionnaire & surveys (large number of SHs) and open-ended questions (tool and technique) to solicit SH feedback. Focus group is also used for requirements analysis in Strategy Alignment.
Term
184.
 Definition
Phase gate reviews are defined in the roadmap and their requirements are developed in the governance plan.
Term
185.
 Definition
After approving the Program Management Plan, components must be authorized by the governance function.
Term
186.
 Definition
Benefit register is used to measure and communicate the delivery of benefits during the program. KPIs and thresholds are included to evaluate benefit achievement. Also, target dates, milestones are included for benefits achievement.
Term
187.
 Definition
PMO defines quality standards for the program and components.
Term
188.
 Definition
Allocating resources is carried by Governance through performance support to optimize programs.
Term
189.
 Definition
Program scope statement: a common understanding of the program scope.
Term
190.
 Definition
Payback period is calculated as initial investment divided by annual net cash inflows.
Term
191.
 Definition
Factors for the program manger to assume component governance are: the experience of the program manager, the complexity of the program, and extend of the coordination efforts required to manage the program in the organization.
Term
192.
 Definition
Knowledge is used for decision making and as a reference.
Term
193.
 Definition
The content of the Program Charter: justification, vision, strategic fit, outcomes, scope, benefit strategy, assumptions and constraints, components, risks and issues, time scale, resources needed, and SHs consideration.
Term
194.
 Definition
The charter links the program to the business case and organizational strategic priorities, objectives and ongoing work.
Term
195.
 Definition
Contract close out report is an output of contract closure.
Term
196.
 Definition
Contract payment is made in accordance with the contracts, financial infrastructure, and contract deliverables.
Term
197.
 Definition
During benefit review, you can identify further benefits to the program.
Term
198.
 Definition
Mission statement describes why the program is important and why it exists. It is prepared by evaluating Stakeholders (SHs) concerns and expectations.
Term
199.
 Definition
PMIS is an output of lessons learned.
Term
200.
 Definition
Strategic Visioning and Planning are required to align program goals with organization long term goals.
Term
201.
 Definition
The business case and current goals of the organization are used to judge successful completion of the program.
Term
202.
 Definition
During the program closing phase, a key activity is to review the status of the benefits with the Governance Board.
Term
203.
 Definition
Periodic health checks focus on ongoing performance and progress (against the BRP).
Term
204.
 Definition
The roadmap provides a snap shot of supporting infrastructure and component plans.
Term
205.
 Definition
Once the high level master schedule is determined, the dates for each component are identified. These dates are constraints for each project team.
Term
206.
 Definition
Program schedule risks should be tracked as part of risk management activity. After schedule risks are identified, the next step is to incorporate them in the risk register.
Term
207.
 Definition
During benefit delivery phase: Value Delivery and Strategy Alignment should be analyzed and assessed.
Term
208.
 Definition
The program manager maintains visibility in program procurements to ensure program budget is being spent properly. An output is performance/earned value reports.
Term
209.
 Definition
Standard measurement criteria are done by analysis of SHs expectations and requirements.
Term
210.
 Definition
Gate reviews assess the benefit realization plan.
Term
211.
 Definition
Components are defined and configured during initiation phase.
Term
212.
 Definition
The benefit register follows each identified benefit throughout the life cycle until it is realized. The benefits realization plan describes how the identified benefits will be realized, measured, and transitioned. Once realized, it would be noted in the benefit register. Dr. Ginger(LinkedIn )
Term
213.
 Definition
Benefit register is developed based on the business case, strategic plan and other relevant program objectives.
Term
214.
 Definition
Forecasts and performance reports are outputs of Program Performance Monitoring and Control.
Term
215.
 Definition
SWOT is used to develop the charter and program plan.
Term
216.
 Definition
To promote program goals in building relationship with SHs, the program manager should use political skills. To manage the program effectively, the program manager needs to blend control-oriented leadership and management skills with goal-centric adaptive skills.
Term
217.
 Definition
Compliance programs are initiated due to legislation, regulation or contractual obligation.
Term
218.
 Definition
Constraints affect schedule, cost, resource or deliverables.
Term
219.
 Definition
Once the funding model is determined, then the high level financial benefits of the program can be determined.
Term
220.
 Definition
Business value measurement is especially useful in measuring intangible benefits.
Term
221.
 Definition
Benefit register is used to report the benefits to SHs via communication plan.
Term
222.
 Definition
Analyze and update the BRP to determine if corrective actions are required.
Term
223.
 Definition
The program manager needs skills in business strategy to align the program with the organization plan, objectives, priorities, vision, and mission statement.
Term
224.
 Definition
Sustainment Plan ensures the continued realization of intended benefits.
Term
225.
 Definition
SH engagement can generate visibility of the program.
Term
226.
 Definition
To proceed to the next phase of the program, present program status to the governance board.
Term
227.
 Definition
Assumptions are key sources of risk.
Term
228.
 Definition
If changes are accepted and approved, the next step is to update the scope statement and the program management plan.
Term
229.
 Definition
For procurement administration use Contract Management Plan.
Term
230.
 Definition
Analyze environmental and legislative changes during program financial monitoring & control. These changes could create changes to the budget baseline.
Term
231.
 Definition
The purpose of program performance reporting is to consolidate data on performance as to how resources are being used to deliver benefits.
Term
232.
 Definition
Status reviews is part of program performance reporting to ensure compliance with contract, cost, and schedule baselines.
Term
233.
 Definition
Program performance reports are helpful to determine if program benefits will be met.
Term
234.
 Definition
EAC is a useful measure to present it at governance meeting.
Term
235.
 Definition
After the change request is accepted the next step is to analyze it.
Term
236.
 Definition
Program Mandate and Business Case are used by organization leadership to charter and authorize programs.
Term
237.
 Definition
Roadmap links between business strategy and planned work.
Term
238.
 Definition
Analysis to assess the validity of the Business Case is: Comparative analysis (Sensitivity), feasibility study, SOWT analysis, Assumption analysis, Historical information.
Term
239.
 Definition
Business Case serves as the formal declaration of program value and key resources it needs.
Term
240.
 Definition
Roadmap establishes the relationship between the program activities and expected benefit.
Term
241.
 Definition
In Benefit management the Program Manager needs strategic visioning.
Term
242.
 Definition
Analyze the potential impact on any planned changes on expected benefit.
Term
243.
 Definition
KPIs are identified during benefit identification phase.
Term
244.
 Definition
Five items to include in benefit sustainment plan are: risks, processes, measures, metrics, and tools.
Term
245.
 Definition
Once benefit register has been prepared, next step is to review it with key SHs to develop performance measures for each benefit.
Term
246.
 Definition
Benefit register, created in benefits identification, is updated during benefit analysis & planning.
Term
247.
 Definition
To have a common understanding of the program benefits, stakeholders should have the charter and the business case.
Term
248.
 Definition
To communicate the overall program direction, stakeholders should have charter and roadmap.
Term
249.
 Definition
Program financial framework is a high-level plan to coordinate available funds for the program, determine constraints, and describe how funds are to be allocated.
Term
250.
 Definition
Communication Strategy should be updated whenever stakeholders and messages change during the program.
Term
251.
 Definition
Program manager can best prioritize resources by managing resources at the program level and working with project managers to balance the needs of the program.
Term
252.
 Definition
If change is approved eight items need to updated; record of the rational for the change, a record of the decision in a decision register, communication of the change to SHs, the program management plan and governance plan, budget and funding, program structure and roles and responsibilities.
Term
253.
 Definition
Benefit realization report is the last thing to do in benefit management.
Term
254.
 Definition
During program transition you need to make sure estimates of the cost to sustain the benefits are finalized prior to transition, the GB should be consulted and lessons learned are archived.
Term
255.
 Definition
Charter and roadmap are developed in the program formulation (part of the definition phase).
Term
256.
 Definition
In program preparation; program management plan, initial program organization, and a governance structure are prepared.
Term
257.
 Definition
Component Planning and Authorizing formalizes the scope of the work to be accomplished by the components and identifies the deliverables to satisfy the program goals and benefits.
Term
258.
 Definition
Information is distributed to the receiving parties including the clients, sponsors, component managers.
Term
259.
 Definition
The program manager, in collaboration with the customer/sponsor, agrees and secures resources to undertake the component transition activities. Roadmap is updated to reflect go/no- go decision.
Term
260.
 Definition
Benefit Sustainment may be achieved through operations, maintenance, new projects, or other efforts.
Term
261.
 Definition
The program may be cancelled due to poor performance or by changes in the business case that make the program unnecessary.
Term
262.
 Definition
Program payment schedule identifies schedule and milestone points where funding is RECEIVED by the funding organization.
Term
263.
 Definition
Program scope is typically described as expected benefits but may also be described as user stories and experiences depending on the type of the program.
Term
264.
 Definition
PWBS serves as the framework for developing the program schedule and defines the program manager's management control points.
Term
265.
 Definition
Scope changes may originate from SHs, components within the program, unidentified requirements or architecture issues, and/or external sources.
Term
266.
 Definition
Order of scope change management activities: capture requested changes, evaluate each requested change, determine the disposition of each requested change, communicate the decision to impacted SHs, document the change request and supporting details, authorize funding and work.
Term
267.
 Definition
Lessons learned database should be updated at the completion of components and at the end of the program.
Term
268.
 Definition
Assumptions analysis is part of the progressive elaboration.
Term
269.
 Definition
Ownership of the program is the responsibility of the program director.
Term
270.
 Definition
Rules and procedures are enterprise environmental factors.
Term
271.
 Definition
The program communication management plan should address SH needs and expectations, and provide key message in a timely fashion and in a format designed specifically for the interested party.
Term
272.
 Definition
Program Document Archive Plan, prepared early in the program, describes in advance how the various documents in the program will be handled - how they will be stored, ways to easily retrieve them for use in the future, and who will be able to access them. It also describes how the various plans in the program should be structured so they follow a similar format. (Dr. Ginger-LinkedIn).
Term
273.
 Definition
Program closing sequence: Close all projects and subprograms - see page 70, close program procurements - pp. 91-92, close the program budget - see page 82, submit a recommendation to the Governance Board to close the program - see pages 61-62, obtain approvals from the sponsoring organization - page 70, 88 prepare the final report; update it with the lessons learned session, p. 88, return resources - pp. 88-89, receive approval from the sponsor and/or the Governance Board - p.89 ( Dr. Ginger-LinkedIn discussion).
Term
274.
 Definition
Read Code of Ethics Thoroughly. It specifies obligations of responsibility, respect, fairness, and honesty and carries with it the obligation to comply with laws, regulations, and organizational and professional policies.
Term
1.
 Definition
Communication plan, an
Term
2.
 Definition
Stakeholder register & communication requirements.
Term
1.
 Definition
PMIS (if applicable)
Term
2.
 Definition
Lessons learned, and
Term
3.
 Definition
Data archiving and retrieval instructions
Term
1.
 Definition
Contractually and/or sponsor-required data reports and accompanying formats,
Term
2.
 Definition
Customer feedback requests, and
Term
3.
 Definition
Periodic reports, presentations, and key performance indicators.
Term
1.
 Definition
Program cost estimates.
Term
1.
 Definition
Program financial framework,
Term
2.
 Definition
Business case updates, and
Term
3.
 Definition
Updates to the communications management and stakeholder engagement plans.
Term
1.
 Definition
Program financial management plan,
Term
2.
 Definition
Program funding schedules,
Term
3.
 Definition
Component payment schedules,
Term
4.
 Definition
Program operational costs, and
Term
5.
 Definition
Program financial metrics.
Term
1.
 Definition
Component cost estimates and documentation.
Term
1.
 Definition
Program budget baseline,
Term
2.
 Definition
Program payment schedules, and
Term
3.
 Definition
Component payment schedules.
Term
1.
 Definition
Contract payments,
Term
2.
 Definition
Component budgets closed,
Term
3.
 Definition
Program budget baseline updates,
Term
4.
 Definition
Approved change requests,
Term
5.
 Definition
Estimate at completion,
Term
6.
 Definition
Program management plan updates, and
Term
7.
 Definition
Corrective actions.
Term
1.
 Definition
Input to final performance reports,
Term
2.
 Definition
Updates to the program financial management plan,
Term
3.
 Definition
Input into the knowledge repository,
Term
4.
 Definition
Documentation of new tools and techniques used in the course of the program into the knowledge management system,
Term
5.
 Definition
Financial closing statements, and
Term
6.
 Definition
Closed program budget.
Term
1.
 Definition
Program procurement standards,
Term
2.
 Definition
Program procurement plan, and
Term
3.
 Definition
Program budget/financial plan updates.
Term
1.
 Definition
Request for Quotation (RFQ),
Term
2.
 Definition
Request for Proposal (RFP),
Term
3.
 Definition
Invitation for Bid (IFB),
Term
4.
 Definition
Proposal Evaluation Criteria,
Term
5.
 Definition
Contract Management Plan, and
Term
6.
 Definition
Awarded Contracts.
Term
1.
 Definition
Performance/earned value reports,
Term
2.
 Definition
Monthly progress reports, and
Term
3.
 Definition
Vendor/contract performance reports including key performance indicators assigned to contractors.
Term
1.
 Definition
Contract closeout reports,
Term
2.
 Definition
Updates to lessons learned, and
Term
3.
 Definition
Closed contracts.
Term
1.
 Definition
Quality management plan that may contain:
Term
?
 Definition
Program quality policy,
Term
?
 Definition
Program quality standards,
Term
?
 Definition
Program quality estimates of cost,
Term
?
 Definition
Quality metrics, service level agreements, or memorandums of understanding,
Term
?
 Definition
Quality checklists, and
Term
?
 Definition
Quality assurance and control specifications.
Term
1.
 Definition
Quality assurance audit findings,
Term
2.
 Definition
Quality assurance standards reports, and
Term
3.
 Definition
Quality assurance change requests.
Term
1.
 Definition
Quality change requests,
Term
2.
 Definition
Quality control completed checklists and inspection reports, and
Term
3.
 Definition
Quality test reports or measurement results.
Term
1.
 Definition
Program resource requirements, and
Term
2.
 Definition
Program resource plan.
Term
1.
 Definition
Program resource priorities and
Term
2.
 Definition
Program resource plan.
Term
1.
 Definition
The program resource plan.
Term
1.
 Definition
The Program Risk Management Plan.
Term
1.
 Definition
Program Risk Register.
Term
1.
 Definition
Updated risk register, and
Term
2.
 Definition
Periodic risk reports showing threat and opportunity key performance indicator trends.
Term
1.
 Definition
Definitive response plans,
Term
2.
 Definition
Risk register updates,
Term
3.
 Definition
Contingency budgets, and
Term
4.
 Definition
Change requests (if required).
Term
1.
 Definition
Timely execution of a risk response when a risk event occurs,
Term
2.
 Definition
Monitoring the effects of the response with further action if required,
Term
3.
 Definition
Documented lessons learned, and
Term
4.
 Definition
An updated risk registers.
Term
1.
 Definition
Program schedule management plan,
Term
2.
 Definition
Program schedule standards,
Term
3.
 Definition
Program master schedule,
Term
4.
 Definition
Inputs to the program risk register, and
Term
5.
 Definition
Updates to the program roadmap.
Term
1.
 Definition
Updates to the program master schedule,
Term
2.
 Definition
Updates to the program risk register, and
Term
3.
 Definition
Updates to the roadmap.
Term
1.
 Definition
Program scope statement,
Term
2.
 Definition
Program scope management plan, and
Term
3.
 Definition
Program work breakdown structure.
Term
1.
 Definition
An updated program scope statement,
Term
2.
 Definition
Dispositions of requests with documentation of the rationale for the decision, and
Term
3.
 Definition
An updated program work breakdown structure.
Supporting users have an ad free experience!