Initiate and Plan - Memorization Flashcards
Project Charter
Document that formally authorizes the project.
Assumption log
Used to record and track assumptions and constraints throughout the project.
Performance measurement baseline
Combination of the scope, schedule and cost baseline used by the earned value management technique.
Planning iterations
Establishes the project baselines and defines how the project will be managed.
Assumptions
Factors that, although uncertain, are accepted as givens for planning purposes.
Project baseline
Formally approved version of project objectives that may be used to assess project performance.
Planning
Define, refine and formalize project objectives and establish the actions and approach required to pursue those objectives.
Initiation
Authorize the project of phase and understand the project context, define a common vision and establish boundaries.
Product overview statement
Statement that briefly summarize the project’s objectives, business need and acceptance criteria.
Project management plan
Planning effort required to balance the different project management plan elements.
Tolerance
Limits of decision-making authority levels for specific project targets and management levels.
Governance framework
Establishes the set of procedures, rules, systems, relationships, decision-making authority levels, roles and responsibilities that will govern projects.
Tailoring
Adapting the project management processes to the project’s needs, size, complexity, risk, importance, and environment.
Vision
Early high-level understanding of the project’s objectives, outcomes, products or solutions.
Subsidiary management plans
Project management elements used to define management rules for specific project management areas.
Product box technique
Using the different sides of a physical box to record
potential users, user needs, key requirements to
address user needs, alternative products to
address user needs, reasons to fund the project
and existing constraints.
Minimum viable product
Minimum set of requirements that must be developed to release a viable and valuable product.
Kanban board
Board used to visualize the process flow and limit work in progress when adopting a flow-based agile.
Release
Aggregates the features of multiple iterations and deploys them to end users.
Incremental product development
Develops usable partial products.
Product backlog preparation
Agile practice of creating a prioritized list of product requirements.
Timeboxing
Limiting the time dedicated to project events (e.g., iterations and planning meetings).
Iteration planning meeting
Agile event in which the team reviews the prioritized items in the product backlog to agree on what can be done in the upcoming iteration.
Product review
Agile event in which the team inspects and adapts the emerging product as well as engages stakeholders.
Iterative product development
Develop a partial version of the product and then expand that product version through repetitive, short-term development cycles.
Retrospective
Agile event in which the team inspects and adapts the process.
Disciplined agile
Principle-based framework that aggregates different agile practices and techniques used to scale agile to the organization.
Scrumban
Hybrid framework that combines elements of Scrum and Kanban.
Crystal methods
Family of agile methodologies with different levels of depth designed to suit projects with different sizes and criticality levels.
Kanban
Method that reduces delivery cycles and improves workflow by limiting the work in progress to available capacity.
Scrum
Lightweight product development framework based on empirical processes and founded on the principles of inspection, adaptation and transparency.
Scaled agile framework
Knowledge base of agile software development, lean and system thinking practice and information that can be used to implement agile at the team, program, large solution or portfolio level.
Empirical processes
Processes that may be adjusted with the acquired experience and knowledge.
Large-scale scrum
Framework that extends the single-team scrum model to multiple cross-functional teams collaborating to create a common product.
Agile
Broad term that refers to any concept, practice or framework that embeds the agile manifesto’s values and principles.
Scrum of scrums
Scaled agile technique used to synchronize and integrate the work of several teams working on the same product.
Predictive approach
Project approach by which work flows downward, like a waterfall, through linear and sequential phases.
Product backlog refinement
Process of regularly updating the backlog, by removing, adding, disaggregating, estimating or updating items.
Iterative approach
Project approach by which the product is developed through continuous cycles or iterations to maximize learning.
Scrum events
Time-boxed ceremonies that sustain the Scrum process and provide an opportunity to inspect and adapt.
Hybrid approach
Project approach that combines other project approaches.
Scrum artifacts
Outputs of the Scrum framework that provide key project information to the Scrum team and other stakeholders, ensuring that performance is completely transparent.
Incremental approach
Project approach by which product components may be developed in parallel and be integrated whenever they are built.
Agile approach
Project approach by which the scope is vaguely defined at the beginning of the projects and each iteration or cycle may enhance or add components to the existing product version.
Collaboration
Team members work closely throughout the project in an open environment and engage with key stakeholders to create a common sense of purpose.
Feature-driven development
Software development agile approach focused on releasing valuable features repeatedly and frequently.
Extreme programming
Software development agile approach designed to quickly respond to a very dynamic and uncertain environment based on core values and a holistic set of practices.
Increment
Set of features deliveres at the end of the iteration.
Self-organization
Teams are empowered to manage their own work instead of relying on the project manager direction.
Iteration
Short fixed-duration period of time during which the team designs, develops, and tests features.
Generalizing specialists
Team members that combine a deep specialization in their area of expertise with some experience and skills in other related areas.
Timeboxes
Short, fixed-duration units of time.
I-Shaped People
Team members with a deep specialization in their area of expertise but no experience and skills in other associated areas.
Daily standup
Short term, time-boxed meeting to coordinate the team’s work, share information and provide transparency.
