From “Acceptance Test” to “User Story,” our agile glossary contains several frequently-used agile terms and definitions to be familiar with as a product manager.
In agile methodologies, acceptance criteria refers to a set of predefined requirements that must be met in order to mark a user story complete. Acceptance criteria are also sometimes called the “definition of done” because they determine the scope and requirements that must be executed by developers to consider the user story finished.
Read Full Definition
In software development, an acceptance test refers to the process of testing a new system, feature, or functionality against predefined acceptance criteria. In other words, an acceptance test evaluates whether or not the product has met predefined requirements.
Adaptive Software Development (ASD) is a direct outgrowth of an earlier agile framework, Rapid Application Development (RAD). It aims to enable teams to quickly and effectively adapt to changing requirements or market needs by evolving their products with lightweight planning and continuous learning. The ASD approach encourages teams to develop according to a three-phase process: speculate, collaborate, learn.
Agile is an iterative product-development methodology in which teams work in brief, incremental “sprints,” and then regroup frequently to review the work and make changes. The agile methodology encourages frequent feedback and the ability to switch focus and priority quickly. This is in contrast to the more traditional, sequence-based, Waterfall methodology, where product managers set long-term plans in discrete phases for development teams to execute.
An agile framework is one of many documented software-development approaches based on the agile philosophy articulated in the Agile Manifesto.
The Agile Manifesto is a brief document built on 4 values and 12 principles for agile software development. The Agile Manifesto was published in February 2001 and is the work of 17 software development practitioners who observed increasing need for an alternative to documentation-driven and heavyweight software development processes.
There are 12 agile principles outlined in The Agile Manifesto in addition to the 4 agile values. These 12 principles for...
Agile transformation is the process of transitioning an entire organization to a nimble, reactive approach based on agile principles.
Agile Values refers to the set of 4 values outlined by the Agile Alliance in The Agile Manifesto. This set...
Back to top
A backlog is a list of task-level details required to execute on a larger strategic plan. A quick glance at a prioritized backlog conveys the next items on a project's to-do list.
Backlog grooming, also referred to as backlog refinement or story time, is a recurring event for agile product development teams. The primary purpose of a backlog grooming session is to ensure the next few sprints worth of user stories in the backlog are prepared for sprint planning. Regular backlog grooming sessions also help ensure the right stories are prioritized and that the product backlog does not become a black hole.
A burndown chart is a visual display of work completed and remaining in a project, sprint, or iteration. In most cases the x-axis of the chart represents time, while the y-axis represents work either completed or remaining.
Business agility applies the principles of agile development to the entire organization. This allows companies to be more responsive to...
In software product development, continuous delivery (CD) is the successful execution of continuous deployment. Whereas continuous deployment aims to reduce...
In software product development, continuous deployment refers to a strategy that aims to reduce the amount of time between writing code and pushing it live. Common practices under this agile-inspired strategy may include automated testing and automated releases.
Continuous integration or CI, refers to an engineering practice that is said to help automate certain pieces of work and identify bugs early in the process. Engineers practicing continuous integration merge their code to a shared repository several times each day. That code is then passed through several automated tests to help identify any errors.
A cross-functional team refers to a group which contains expertise or representation from various "functional" departments. For example, an agile cross-functional team may consist of a product manager, product owner, scrum master, engineers, QA, and design.
Crystal is an agile framework focusing on individuals and their interactions, as opposed to processes and tools. In other words,...
A DEEP Backlog is one of the suggested objectives of a product backlog grooming session. DEEP is an acronym used to indicate a few key traits of an effective product backlog.
In the Scrum agile framework, Definition of Done describes the requirements that must be met in order for a story to be considered complete. Definition of Done is typically used by the entire team to agree on the overall quality and completeness that a finished product must exhibit. This concept differs from acceptance criteria in that it is a wide-ranging set of requirements that can apply to all items in the backlog (i.e. quality).
In the Scrum agile framework, Definition of Ready describes the requirements that must be met in order for a story to move from the backlog to development. In keeping with agile tradition, Ready is often defined as a story that can be acted on immediately.
Disciplined Agile (DA), is a process decision framework that puts individuals first and offers only lightweight guidance to help teams...
Dual-track agile is a type of agile development in which the cross-functional product team breaks its daily development work into two tracks: discovery and delivery.The discovery track focuses on quickly generating validated product ideas for the backlog, and the delivery track focuses on turning those ideas into software ready for the market.
The Dynamic Systems Development Method (DSDM) is an agile framework that addresses the entire project lifecycle and its impact on...
The Eisenhower Matrix is a productivity, prioritization, and time-management framework designed to help you prioritize a list of tasks or...
The engineering backlog lists and prioritizes the stories, epics, and/or initiatives that are to be worked on by the engineering team for a given sprint. Typical items in an engineering backlog include stories, bug fixes, and other engineering-related tasks.
This page will walk you through the basics of enterprise architecture planning, by answering the following questions: What is enterprise...
An epic, like a theme, is typically a group of features or stories with a common strategic goal. Note that an epic is one level of detail below a theme, considering a theme might be comprised of several related epics.
eXtreme Programming (XP) is an agile framework that emphasizes both the broader philosophy of agile—to produce higher-quality software to please...
Feature Driven Development (FDD) is an agile framework that, as its name suggests, organizes software development around making progress on...
The ICE Scoring Model is a relatively quick way to assign a numerical value to different potential projects or ideas...
In agile software development, an iteration is a set amount of time reserved for development. Typical iterations last 1-2 weeks,...
A kanban board is a type of workflow that is commonly used to manage initiatives in project management. Kanban boards can be found in a number of popular tools such as Trello, and some product teams prefer to display their roadmaps in a kanban style view.
Lean Software Development (LSD) is an agile framework based on optimizing development time and resources, eliminating waste, and ultimately delivering...
A Minimum Viable Feature (or MVF) is similar to a minimum viable product, but at the feature level. While a...
Pair programming is an agile software development practice in which two programmers team up at one workstation to maximize efficiency. With pair programming, one of the two programmers (the driver) writes the code while the other watches and reviews (the observer). The two programmers switch roles frequently.
Definition: A product backlog lists and prioritizes the task-level details required to execute on the strategic plan set forth in...
What Is the Product Development Process? The product development process encompasses all steps needed to take a product from concept...
The product owner bridges the gap between product strategy and development. They are usually responsible for the product backlog, organizing sprints, and are expected to be available to answer questions from developers as needed. In comparison to the strategy-focused role of the product manager, the product owner generally takes on more tactical duties.
What Is Product Requirements Management? Product requirements management is the ongoing process of overseeing the implementation of all requirements needed...
What is Rapid Application Development (RAD)? Rapid Application Development is an agile framework focused primarily on rapid prototyping of software...
Rapid experimentation is an agile approach to the product development process. With this approach, frequent experiments are deployed in an attempt to discover new, innovative ideas. Experiments can range in severity, from simple A/B tests to larger field experiments.
Rapid prototyping is an agile strategy used throughout the product development process. With this approach, 3-dimensional prototypes of a product or feature are created and tested in an attempt to optimize characteristics like shape, size, and overall usability.
A release demo is typically given by agile teams at the end of a sprint. These demos are used to...
A retrospective is a meeting held after a product ships to discuss what happened during the product development and release process, with the goal of improving things in the future based on those learnings and conversations.
The Scaled Agile Framework, or SAFe, methodology is an agile framework for development teams built on three pillars: Team, Program,...
In an agile context, Scrum is an approach to project management. Typically the Scrum agile framework favors moving projects forward...
A scrum master is a facilitator for an agile team working under the scrum methodology. The scrum master serves as a point person responsible for understanding the big development picture of each sprint. They are responsible for delegating tasks appropriately and ensuring the team is working on the right tasks at the right time. They also want to ensure the team is fully deployed and not idle. The role of scrum master often involves working closely with the product owner to translate epics, stories, and other items on the sprint list into actionable tasks for developers.
Scrum meeting is a catch-all term for the various different meetings practiced by agile scrum teams. Examples of scrum meetings...
What is an Agile Sprint? In agile methodology, a sprint is a period (e.g., 14 days) in which an agreed-upon...
What Is a Sprint Backlog? A sprint backlog is the set of items that a cross-functional product team selects from...
In the scrum methodology for agile, sprint goals are clear objectives set before the beginning of a sprint. They are...
What Is Sprint Planning? In the Scrum agile framework, a sprint planning meeting is an event that establishes the product...
A daily standup is a quick session where each member of the team shares what they accomplished yesterday, what they’ll...
A story point is a unit of measurement used by development teams to estimate the amount of effort required to...
A user story is a small, self-contained unit of development work designed to accomplish a specific goal within a product. A user story is usually written from the user’s perspective and follows the format: “As [a user persona], I want [to perform this action] so that [I can accomplish this goal].”
Velocity is a metric used to measure the speed of a development team’s delivery for a given cycle. Velocity is...