8 - Agile & Hybrid Management Terminology Flashcards
Acceptance Criteria
Customer identified functionality written in enough detail to validate product performance.
Objective criteria that determines if the story achieves the value it represents.
Acceptance Test
Activities that validate that the features perform in accordance with customer defined functionality.
Activity
The Agile term for TASK.
Adaptive PMLC Model
(Project Management Life Cycle)
A change-tolerant life cycle model used for projects where the details of the expected result (solution) are incomplete and/or not well-defined and some functionality is incomplete and/or not well-defined.
An example of an adaptive PMLC Model is an APF (Adaptive Project Framework) project.
Agile
An iterative software development approach, expressed in a variety of methodologies, which embraces incremental delivery, flexiblity, cross-functional and self-organizing teams, direct customer-developer communication and collaboration, and frequent inspection and adaptation.
Agile Coach
An experienced leader who consistently directs team members to move beyond the performance of Agile practices and adopt Agile thinking.
Agile Development
Life Cycle
A comprehensive elaboration that includes continuous integration, refactoring, acceptance testing, cross-functional teams, planning poker, burnup charts, information radiators, and burndown charts.
Agile Manifesto
Declaration of values and principals for Agile development including prioritizing individuals over processes and working software over extensive documentation.
Agile Model
A barely sufficient representation that is free from error, understandable, unembellished and coherent.
Agile Planning
The processes and practices that result in flexible and effective management of a project and include a vision and roadmap among other artifacts.
Agreement
A Scrum term used to describe the agreement between a product owner and the team that includes the definition of done, the acceptance criteria, and any general agreements.
Can be applied to stories, capabilities, sprints, and releases.
Artifact
Something made by the team for the project, especially something that may be reused.
Backlog
An evolving list of customer-prioritized stories, tasks, and bugs that have not been completed and are not being worked on during the current iteration.
Backlog Item
Any story, task, or bug that has not been completed and is not being worked on during the current iteration.
Backlog Refinement
(also referred to as Backlog Grooming or Backlog Maintenance)
Continuously updating the prioritized product backlog to reflect any changes, including adding new items, removing items that are no longer appropriate, re-prioritizing existing items as necessary, and refining/cleaning user stories to get them ready for planning and execution.
Bug
A code defect or error.
Burndown Chart
A graphical representation of the work (represented by story points for a release and hours for an iteration) remaining over time.
Burnup Chart
A graphical representation of the work that has been completed over time plotted against the total work.
Capacity
The amount of work that can be completed in a defined time period taking into consideration the need to perform administrative tasks, the need to perform other work, and absence.
Change Management
A proactive approach to controlling, communicating and responding effectively to fluctuations.
Colocation
The desirable state of working in close proximity to promote face-to-face communication.
Context Model
A graphical representation of the system within the overall environment.
Continuous Integration
The process of assimilating newly developed iterations into the existing system at frequent intervals via an automated and tested build, so that any faults can be quickly determined and corrected.
Core Team
Group composed of cross-functional team members with varying levels of Agile knowledge; typically comprised of a sponsor, project management, developers, quality assurance personnel, architecture expert, product manager, and business knowledge experts.
Cross-Functional Team
A group whose members collectively provide the skills required to complete the project.
Daily Scrum
Team meeting held on a daily basis used to share the daily reality:
1. What have you done since the last daily scrum?
2. What will you do until the next daily scrum?
3. What impediments stand in your way?
…and to adapt to that reality, which usually involves an immediate re-planning meeting and additional meetings (based on the availability of team members, what technical debt was revealed, and other information that impacts today’s work).
Dashboard
An information radiator that contains graphical representations depicting progress, trends, and identification of potential issues.
Data-Flow Diagram (DFD)
Graphical representation depicting the movement of data between processes, objects, and storage within the system.
Definition of Done
A Scrum team representing the object criteria used to determine if a story meets internal standards/constraints.
Demo
A working version of the product shown to the customer at the end of an iteration to evidence work done and solicit feedback.
Development Team
A self-organizing, cross-functional group of individuals who do the work of the project including analysis, design, development, testing, technical communication, and documentation.
Distributed Team
A team working on same project whose members are physically located in separate work sites or locations.
Elevator Statement
The synopsis of a concept, such as the purpose of a project, which can be expressed in thirty seconds or so.
Emotional Intelligence Quotient (EQ)
The capacity to acknowledge and effectively manage feelings in onself and others.
Empirical Process Control
The continuous inspection and adaptation of procedures to ensure any variances in output are within acceptable limits.
Epic
A large story, usually undeveloped, that needs to be decomposed into smaller stories.
Feature
Business functionality comprised of one or more user stories.
Fibonacci Sequence
A series of numbers that begins with 0 and 1, and then is expanded by adding the two previous numbers together: 0, 1, 1, 2, 3, 5, 8, 13…
Flow
The rate of value delivery to the customer.
Impediment
Anything that prevents the team from working efficiently and effectively.
Impediment Backlog
An evolving list of impediments that have not been completed and are not being worked on during the current iteration.
Increment
Consecutive changes that increase the amount or value of something.
Information Radiator
A wall in the common workspace that contains highly visible, graphic representations of progress.
Inspect and Adapt
The practice of inspecting a solution at pre-determined stages and, based upon the inspection results, making improvements (adaptations).
Interdependent Stories
User stories that, considered together, solve a problem.
INVEST
An acronym that stands for the rules that define a user stroy.
Independent
Negotiable
Valuable
Estimable
Small
Testable
Issue
A disputed or unsettled condition.
Issue Log
A project document that tracks elements which cause stakeholder concern or dissension.
Iteration Demo
A working version of the product shown to the customer at the end of an iteration to evidence work done and solicit feedback.
Kanban
An evloutionary, incremental process improvement method.
Kanban System
A pull system that uses virtual signal cards.
Kano Analysis
A model for customer satisfaction that categorizes features as -
Must Have’s
Linear (the more, the better)
Exciters/Delighters
Dissatisfiers
Lean
A methodology that emphasizes the elimiation of waste, producing only what is valuable to the customer.