PMP - Planning Projects Flashcards
artifacts
project documents. could also be a physical prototype.
documentation and content created by teh team to plan and manage the project effectively. need to maintained and then archived at the end of the project.
configuration management system
document library. card catalog, you will get your documents through this.
rolling wave planning
plan as we go, do it in chunks. no final complete universal plan. progressive elaboration. learn as we go, premature to over plan because too many unknowns
project scope vs. product scope
project scope is the umbrella that includes the initiation, plan, product creation, and close. Product scope i child concept that is just the making of the deliverable.
product roadmap
- Envisions and plans the “big picture”
- Displays product strategy and direction and the value to be delivered
- Leads with the overarching product vision and uses progressive elaboration to refine vision
- Uses themes (goals) to provide structure and associations
- Provides short-term and long-term visualization
Adaptive Planning
release dates
release plan with iterations
iteration plan with features a, b, c) - time boxed
tasks to do with sprint points, hours
product roadmap
- Envisions and plans the “big picture”
- Displays product strategy and direction and the value to be delivered
- Leads with the overarching product vision and uses progressive elaboration to refine vision
- Uses themes (goals) to provide structure and associations
- Provides short-term and long-term visualization
milestones
markers for big events, reviews, due dates, payments or decision-making. communication device, not project tracking devices.
- Triggers for reporting requirements or sponsor/customer approval
* Created by project managers, customers or both
A milestone list identifies all milestones and indicates which are:
* Mandatory - required by contract, or
* Optional (estimated on historical information)
ROM
rough estimate of magnitude – estimate of time, money, needed. guess of the size of the project.
30% of budget on initiation and planning !!!!
requirements
A requirement is one single measurable statement of a condition or capability. Must be unambiguous (measurable and testable), traceable, complete, consistent and acceptable to key stakeholders.
Note: make sure it’s specific and not just ‘faster’ ‘better’
need noun, direct object, and measurable change of state
requirements management plan
tool to document requirements that includes:
- tracing, tracking, reporting plans
- authorization level/approvals
- prioritization
- metrics and rationale
- traceability (i.e. the configuration management system)
nominal group technique
way to get consensus from a group
What are some methods of collecting requriements
observation - go down to marsh in your boots and observe
facilitation
data gathering - brainstorming, interviews, focus groups, questionnaires and surveys, benchmarking
data analysis - reading over docs
decision making techniques - dot voting, may need to consider multiple factors (e.g. compliance)
data representation - mid mapping, affinity diagrams, context or use case diagrams
prototyping or storyboards
benchmarking
sourcing data from outside your organization
state of the art, what are industry leaders doing?
(inside = historical info)
MoSCoW analysis
must have, should have, could have, wont have
common for agile software, used to get stakeholders to have a common understanding of which requirements are most important. in predictive only used in the planning stage, not after the scope has been set.
Kano model
delighters/exciters
satisfiers
dissatisfiers
indifferent
categories customer requirements into these diff categroies
paired comparison analysis
rate and rank alternatives by comparing one against the other
similar to a bracket, but comparing all pairs
100 points methods
like monopoly money
aka fixed or sun of fixed allocations
vote for importance of things on a list if ou
representation of data
mind mapping - put all ideas in little bubbles and connect related ideas.
affinity diagram - classify ideas and review/analyze. affinity = category
context diagram
visual that shows a database, whats in it, and the internal and external users. looks like a system diagram.
prototyping
- Evaluation and experimentation tool
- Enables early feedback for further development and to develop a detailed
list of project requirements - Storyboarding is a type of prototyping that uses visuals or images to illustrate a
process or represent a project outcome.
scope management plan
1 of the official docs. doesnt contain the actual scope, but does have the scope baseline. plan the plan plan. includes how you will prep a project scope doc.
- Review of the scope activities for the project and how that work will be done
- Should include processes to prepare a project scope statement
- Enables the creation of the WBS from the detailed project scope statement
- Establishes how the scope baseline will be approved and maintained
- Specifies how formal acceptance of the completed project deliverables will be obtained
- Can be formal or informal, broadly framed or highly detailed
what is included in a project scope statement/document
- Scope description - project and product
- Acceptance criteria
- Any required deliverables
- Any out-of-scope items needed for clarification
- Constraints and assumptions
List tools/techniques for analysis
document analysis
alternatives analysis
product analysis
expert judgement
product analysis
definition: breaking something into it’s constituent parts. decomposition
synonyms:
product breakdown
systems engineering
system analysis
requirement analysis
value engineering
value analysis
work breakdown structure (WBS)
flow chart thingie that lists all the documents you need. comprehensive inventory. Doesn’t need to be chronological left to right.
levels: project name, control account, planning package, work package
analysis – metrics and reports, then metrics are composed of data and security
design - database, UI, reports
(slide 180)
code of accounts
numbering scheme that identifies where a particular item is in the heirarchy of the work breakdown structure.
scope baseline
everyone agrees its a sensible money, time, energy sped
scrum/iteration/spring board – what are the three columns
to do, in progress, done
kanban board as more than 3 columns.
schedule management plan
describes how activities will be defined and progressively elaborated.
doesn’t contain the schedule itself, just defines how to handle scheduling.
defines the maintenance process for updating status and track project progress
components: schedule model, accuracy, units of measure, organizational procedural limits, control thresholds, rules, reporting, process descriptions.
what is the order for predictive schedule planning
- break down the work packages into activities
- sequence the activities (determine dependencies, precedence)
- estimate duration of activities
- determine critical path
- resolution of resource overallocations
- compression of the schedule, if needed to meet constraints
critical path
tasks that for their duration or relationship to other tasks determine the end date of the project. excel example when they turn red. if they are not done they can push the end date out.
