Module 1 Flashcards
RACI MATRIX
Provides clarity on the roles and responsibilities assigned to each project tram member.
Responsible Accountable Consult Informed or Support (RASI)
Virtual Teams
Group of people with a shared goal who fulfill their roles with little or no time spent meeting face-to-face. Creates opportunity for finding team members with greater skills, at lower costs.
Servant Leadership
Type of leadership used in agile which encourages the self-definition, self discovery, and self awareness of team members by listening, coaching and providing an environment which allows them to grow. Servant leaders facilitate the team’s work, remove any work barriers, educate stakeholders on the processes being followed.
Team Charter
A document that enables the team to establish its values, agreements, and practices as it performs its work together.
A good team charter should include:
- shared values.
- guidelines for team communications and use of tools.
- decisions.
- How team resolves conflicts.
- How and when the team meets.
- shared hours and improvement activities.
Conflict resolution methods
- Withdraw/Avoid
- Smooth/Accommodate
- Compromise/Reconcile (lose-lose)
- Force/Direct (win-lose)
- Collaborate/problem solve (win-win)
Service Level Agreement (SLA)
Contracts between a service provider and the end user that describes the level of service expected from the service provider. Incorporates expectations for functional performance and service warranty.
Go-Live Blackouts
Black out times occur when the deliverables are handed over for implementation. Go live occurs at the end of the project timeline, and black out times negotiated in advance .
Lesson Learned
The knowledge gained during a project which shows how project events were addressed or should be addressed in the future for the purpose of improving future performance.
MoSCoW Analysis
Prioritizes features as Must Have, Should Have, Could Have, and Wont Have. Helps customers organize their thinking about what is truly must have capabilities , and enables identification of a Minimum Viable Product (MVP).
100 Point Method
Each stakeholder is given 100 points and can multi-vote their points across all the stories, which then give a weighted priority when combined.
Roman Voting
A technique used to reach consensus. People vote either thumbs up (agreement) or thumbs down (disagreement).
Planning Poker
Estimation technique where a user story is presented to the team, where they use a card deck (with modified Fibonacci numbers) to vote for the number of points to assign to the story. This process is repeated several times
Retrospective
Time specifically set aside for the team to reflect on its performance and practices, identify and solve problems, and identify specific proposed improvements.
XP Metaphor
Extreme Programming (XP) technique is simple non technical description that enables stakeholders to understand the overarching approach to provide a capability or solve a problem.
T-Shaped Skills
Refers to a person with 1 deep area of specialization and broad ability in the rest of the skills required by the team.
(Breadth of Knowledge)
----------------------------->
|
| (Depth of knowledge)
|
|
Sprint Planning
A meeting that facilitates communication and collaboration between the customer (product owner in scrum) and the project team. Facilitates agreements on on small goals for a team to complete during a short, defined period of time (sprint).
Sprint Review (demo)
A review at the end of each iteration with the Product Owner and other stakeholders to review the progress of the product, get early feedback, and where the Product Owner reviews and accepts the stories delivered on that iteration.
Kanban Board
Visualization tool that enables improvements to the flow of work by making bottlenecks and work quantities visible.
Pre-assignment
There are a number of tools and techniques to support skill appraisals:
- Attitudinal Surveys
- Specific assessments
- structured interviews
- ability tests
- focus groups
Stakeholder
large group of people and organizations that can influence, or is affected by, the outcome of a project.
Members of the project team are also part of the stakeholder group, but not all stakeholders are part of of the project team.
Physical Resources
Include people, equipment, access rights. Identified what will be required by the team members to perform the work. It is encompassed in the The Plan Resource Management.
Ground Rules
setting clear expectations regarding the code of conduct for team members in the Team Charter. They include actions that are considered acceptable and unacceptable.
Brainstorming
Simple technique used to generate a list of ideas. Teams solutions to a given problem, and then performs various types of analysis to assist the team in selecting alternatives.
Resource Calendar
Identifies working days, shifts, and when specific resources are made available for a project.
Expert Judgment
used as key input for negotiating project agreement, the PM use subject matter expertise to help asses needs, identify, potential solutions, and approaches, and ensure understanding of the larger project context.
Kano Model
Prioritization technique that helps identify certain features or capabilities as Basic, Performance, or Excitement.
Paired Comparison Analysis
Looking at each pair of stories and prioritizing one over the other.
Fist of Five
Technique for building consensus. A fist is disagreement and will require adjudication. An open hand showing five fingers means agreement.
4 fingers show general agreement with minor questions
3 fingers show abdication - willing to go along with group
2 fingers show general disagreement
1 finger show disagreement
Polling
Technique used to reach consensus which is simple polling of the team to assess their point of view on an issue. If team is unanimous, team moves on. If objections raised, facilitator tries to help the team work to solve the problem.
Dot Voting
A technique to prioritize any list. Each stakeholder can then vote with sticky dots based on the weight they believed should be provided to that list item. Based on the number of dots received to each item, an overall priority can be identified.
SWOT Analysis
Examines the project from the perspective of Strengths, Weaknesses, Opportunities, and Threats. Helps identify risks.
Project Charter
A document issued by the sponsor that formally authorizes existence of project and provides the PM with authority to apply organizational resources to project activities.
Is the only document that never changes throughout the project.
Ensures stakeholders have a common understanding of the projects key milestone, deliverables, and roles and responsibilities.
Product Box Exercise
A technique used to explain an overarching solution. . Exercise can help team members better understand the different types of solutions.
Daily Standup (Daily Scrum)
A short 10-15 min meeting held each day for the team to reaffirm commitment to its objectives for the iteration and to surface any blockers to its ability to meet goals. Is not a status meeting, but to coordinate today’s work amongst themselves.
Sprint Retrospective
A meeting facilitated by the Scrum Master for the team to identify its own improvements. Reviews the team’s processes and practices and is used to identify ways the team can improve its performance and collaboration.
Focus Groups
An elicitation technique that brings together pre-qualified stakeholders and SME’s to learn about their expectations and attitudes about a proposed product, service, or result.
Predictive Life Cycle
A project lifecycle in which the project scope, time, and cost are determined in the early phases of the life cycle. Enables the project team to stay focused on each phase of the project before having to move forward into the next phase.
Iterative Life Cycle
A project life cycle where the project scope is determined early in the project life cycle, but time and cost estimates are routinely modified as the project team’s understanding of the product increases.
Hybrid Methodologies
Combines elements from predictive (waterfall) and adaptive (agile) approaches. Tend to do more in depth planning and requirements gathering up front.
Agile Estimating
Does not use absolute measurements to predict the level of work involved in a task.
Agile teams use relative estimations.
Ex: planning poker (i.e. story points)
Scope Management Plan
Component of the project management plan that describes how the project scope will be defined, developed, monitored, controlled, and validated.
A How-To document that describes how to manage scope related activities.
Context Diagrams
Visual depiction of the product scope showing a business system and how people and other systems interact with it.
Project Scope Statement
A document describing project scope, acceptance criteria, major deliverables, assumptions, and constraints.
WBS
Work Breakdown Structure. Hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create deliverables.
Control Accounts
Management control point where scope, budget, actual costs, and schedule are integrated and compared to earned value for performance measurement. Control points are tracked by finance to verify that costs are within budget.
Code of Accounts
Numbering system used to uniquely identify each component of the WBS.
User Stories
Brief description of deliverable value for a specific user.
Value is described in a template such as “As a {username or persona}, I want to {objective or intent}, so that I can {why the objective brings value}.”
Sprint Backlog
A list of work identified by the Scrum team to be completed during the Scrum sprint.
Acceptance Criteria
A set of conditions that is required to be met before deliverables are accepted.
Analogous Estimating
A technique for estimating the duration or cost of an activity by using historical data from a similar activity or project.
Bottom up Estimating
Estimates the cost of individual activities then “rolls up” to higher levels.
T-shirt Sizing
S, M, L, XL, XXL based on the combination of risk, complexity, & labor.
EVM
Earned Value Management. Is a methodology that combines scope, schedule, and resource measurements to assess project performance and progress during project execution.
Cost Baseline
The approved version of the time-phased project budget, excluding any management reserves, which can be changed only through formal change control procedures and is used as a basis for comparison to actual results.
Funding limit Reconciliation
Is the process of comparing the planned expenditures
of project funds against any limit on the commitment of funds for the project to identify any variances between the funding limits and the planned expenditures.
Task estimates
Review scope baseline for WBS, deliverables, assumptions/constraints.
Analyze & decompose each work package of the WBS into activities required to produce a deliverable.
Burn down charts
Chart tracks the work that remains to be completed.
4 types of precedence relationships
Finish-to-Start (FS)
Finish-to-Finish (FF)
Start-to-Start (SS)
Start-to-Finish (SF)
Critical Path
The sequence of activities that represents the longest path through a project which determines the shortest possible duration.
Calculated by doing a forward pass to calculate the ES & EF for each activity and then a backward pass to calculate the LS & LF.
Agile Release Planning
Determine number of iterations or sprints that are needed to complete each release, the features, the features each iteration will contain, and target rate for release.
SMART Objectives
When it comes to defining useful KPI's, it is important to remember SMART acronym. Specific Measurable Achievable Relevant Time bound
Agile Life cycles
A project life cycle that is iterative or incremental. Also referred to as change driven or adaptive, they work well in environments with high level of change and ongoing stakeholder involvement.
Incremental Life cycles
An adaptive life cycle in which the deliverables is produced through a series of iteration that successively add functionality within a predetermined time frame. The deliverable contains the necessary and sufficient capability to be considered complete only after the final iteration.
Traceability Matrix
Links product requirements from their origin to the deliverables that satisfy them.
Product Backlog
A prioritized list of customer requirements and the first step of Scrum in which priority is based on the riskiness and business value of the user story.
Affinity Diagramming
A technique that allows large numbers of ideas to be classified into groups for review and analysis.
Requirements Management Plan
A component of the project or program management plan that describes how requirements will be analyzed, documented, and managed.
Scope Baseline
Is the approved version of a scope statement, WBS, and its associated WBS dictionary, that can be changed using formal change control procedures and is used as a basis for comparison to actual results.
