PrepCast info Flashcards
Proof of Concept
A prototype, study, etc before project begins to demonstrate if product will have value.
The proof of concept is so valuable because it’s a test project to evaluate before work begins on an actual project. Can help determine what skills/resources will be needed
Information Radiator
Big visual chart placed in a prominent location. It conveys key information and shows the health of a team
Force Majeure
Contractual clause that frees parties, bound by a contract, from liability or obligation if an “act of god” happens. Both natural and man made (War)
(Hurricane, Tornado, War, etc)
Tornado Diagram
Used to analyze the influence of a whole range of potential risks.
Often created by Sensitivity Analysis (Where we take 1 risk event, and ask ourselves “If this event happens, how will it affect our whole project?” Not necessarily domino effect of what could happen, but how will this single event effect the overall project)
Project Documents
any project related documents that are not part of project management plan (includes assumption logs, issue logs, lessons learned, project schedule, resource calendars, etc)
Organization Breakdown Structure (OBS)
a hierarchical model describing the established organizational framework for project planning, resource management, time and expense tracking,etc.
It shows work packages and activities that are assigned to each team
SWOT Analysis
Used in Risk Analysis. Analyzes a project from the strenghts, weaknesses, opportunites, and threats
Reserve Analysis
Analytical technique to determine relationships of components in PM Plan to establish a reserve for schedule duration, budget, cost, etc.
Risk-based spike
short, time-boxed effort used to investigate and hopefully eliminate and issue or threat to project
Architectural Spike
technical timeboxed experiement aimed to explore a technical approach to use an unfamiliar technology or technique
Issue Log to Change Request Process
During M & C, Issues may arise. Those issues should be recorded in the issue log first. If after review of the issue log, it is determined a change request is needed, you enter it into the change log, and it then goes through integrated change control.
Requirements documentation
describes how each requirement meets the business needs for the project.
Feasability Study
An analysis that takes all of a project’s relevant factors into account—including economic, technical, legal, and scheduling considerations—to ascertain the likelihood of completing the project successfully
Business Case is a feasibility study to establish the validitity of the benefits of the project and if its worth taking on.
Benefits Management Plan
Document explaining how we’ll create, maximize, and sustain the benefits of the project. Also includes who is responsible for those benefits after the project.
Muda
Japanese word meaning waste. Used in Lean Manufacturing