Discover published sets by community

Allocating a fixed, maximum unit of time for an activity, and then completing the activity within that time frame.

An iterative and incremental software development process that is model driven for designing and building features.

A graphical representation of work left to do versus time.

A software development process that relies on the repetition of a very short development cycle: requirements are turned into very specific test cases, then the software is improved to pass the new tests.

A formal proclamation of four fundamental values and 12 principles to guide an iterative and people-centric approach to software development.

A role in Scrum responsible for defining features of the product and deciding on release dates and content.

An approach that emphasizes optimizing efficiency and minimizing waste in the development of a product.

A planning process that acknowledges the unpredictability of the development process and evolves as the project's environment changes.

The process of adding new user stories to the backlog, re-prioritizing existing stories as needed, and fixing errors or inconsistencies.

A time-boxed period of development where work is performed on a set of backlog items that the team commits to completing.

A facilitator for an Agile development team, responsible for managing the process for how information is exchanged.

A meeting at the end of the project phase to discuss what was successful during the project phase, what could be improved, and how to incorporate the learnings for future project phases.

A long-lived team of Agile teams, which, along with other stakeholders, incrementally develops, delivers, and where applicable operates, one or more solutions in a value stream.

A time-boxed period during which a specific work has to be completed and made ready for review.

The process of creating a document that formally authorizes a project or a project phase.

A daily short meeting for the development team to sync up, usually held standing up to keep it short and to the point.

A clear and concise list of criteria that must be met before a product increment is considered complete.

A software development practice where developers regularly merge their code changes into a central repository, after which automated builds and tests are run.

The process of restructuring existing computer code without changing its external behavior, which improves nonfunctional attributes of the software.

A measure of the amount of work a team can tackle during a single sprint and is the key metric in Scrum.

A large body of work that can be broken down into a number of smaller tasks (user stories).

A tool used in Agile software development to capture a description of a software feature from an end-user perspective.

Constraints set to limit the amount of work that can be in progress at one time, thereby encouraging focus and reducing work-in-progress inventory.

A development technique in which a new product or website is developed with sufficient features to satisfy early adopters.

An individual who is experienced in implementing Agile projects and can share that experience with a project team.

A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

A visual system for managing work as it moves through a process, visualizing the flow of work, often used to promote continuous improvement.

A meeting where the development team selects what work items to develop during the upcoming iteration.

A prioritized list of features, enhancements, and bug fixes required to bring a product to life, often subject to continuous revision.