Sprint Backlog
A list of tasks and deliverables that a team commits to completing during a sprint, providing a clear focus and scope for the sprint's duration. Essential for organizing and prioritizing work within an Agile sprint.
A list of tasks and deliverables that a team commits to completing during a sprint, providing a clear focus and scope for the sprint's duration. Essential for organizing and prioritizing work within an Agile sprint.
A concise statement of what the team aims to achieve during a sprint, providing direction and a shared understanding of the sprint's purpose. Crucial for ensuring team alignment and focus on the most important outcomes during a sprint.
A meeting where the Agile team discusses and decides what tasks will be completed in the upcoming sprint, establishing a clear plan for the sprint's duration. Crucial for ensuring the team is aligned and has a clear understanding of the work to be done in the sprint.
A measure used in Agile project management to quantify the amount of work a team can complete in a given sprint, typically measured in story points. Crucial for planning and forecasting in Agile projects and understanding team capacity.
An Agile project management framework that uses iterative cycles, called sprints, to deliver incremental improvements and adapt to changing requirements. Crucial for managing projects in a flexible and iterative manner, ensuring continuous improvement and responsiveness.
An agile framework for managing work with an emphasis on software development, characterized by sprints and iterative progress. Essential for improving productivity and delivering incremental value in development projects.
A meeting at the end of a sprint where the development team presents their completed work to stakeholders. Crucial for gathering feedback and demonstrating progress.
A time-boxed period during which specific work must be completed and made ready for review, used in Agile project management. Crucial for managing workload and ensuring continuous delivery and improvement in Agile projects.
A time-constrained, intensive process that helps teams quickly design, prototype, and test ideas. Important for rapidly developing and validating design solutions.
A user experience design methodology focused on rapid iteration, collaboration, and learning through experimentation. Essential for creating user-centered designs efficiently and effectively.
A prioritized list of tasks, features, and technical debt items that need to be addressed by the engineering team. Essential for managing and organizing work in software development projects.
An agile methodology that separates product discovery and product delivery into parallel tracks to ensure continuous learning and delivery. Essential for balancing innovation and execution in agile product development.
A brainstorming technique where participants sketch eight ideas in eight minutes to generate a wide range of concepts quickly. Essential for fostering creativity and generating diverse ideas rapidly.
Walk the Wall (WTW) is a practice where team members physically move along a wall displaying their project's progress, discussing and updating tasks. Essential for fostering team collaboration and ensuring transparency in project status.
Minimum Viable Experience (MVE) is the simplest version of a product that delivers a complete and satisfying user experience while meeting core user needs. Essential for rapidly validating product concepts and user experience designs while ensuring that even early versions of a product provide value and a positive impression to users.
Minimum Marketable Feature (MMF) is the smallest set of functionality that delivers significant value to users and can be marketed effectively. Crucial for prioritizing development efforts and releasing valuable product increments quickly, balancing user needs with business objectives.
Large-Scale Scrum (LeSS) is a framework for scaling agile product development to multiple teams working on a single product. It provides a minimalist, large-scale agile approach that maintains the simplicity and effectiveness of Scrum while addressing the challenges of coordination and integration in multi-team environments.
A large body of work that can be broken down into smaller tasks or user stories, used in agile project management to organize work. Essential for managing and organizing large projects in agile development.
A collaborative tool used to visualize what a user thinks, feels, says, and does to better understand their experiences and needs. Essential for gaining deep insights into user behavior and guiding design decisions.
A cognitive process used to generate creative ideas by exploring many possible solutions, often contrasted with convergent thinking. Essential for fostering creativity and innovation in problem-solving and design.
The sequence of phases through which a product or project passes from conception to completion. Essential for managing and tracking the progress of development projects.
Detailed, Estimated, Emergent, and Prioritized (DEEP) is an agile project management framework for a well-maintained product backlog. Important for maintaining a clear and actionable backlog in agile methodologies.
Agile Release Train (ART) is a long-lived team of Agile teams that, along with other stakeholders, incrementally develops, delivers, and operates one or more solutions in a value stream. Important for coordinating Agile development and delivery at scale.
A relative estimation technique used in Agile project management to quickly assess the size and complexity of tasks by assigning them T-shirt sizes (e.g., small, medium, large). Crucial for efficient project planning and workload management.
Rapid Application Development (RAD) is a software development methodology that emphasizes quick prototyping and iterative delivery. Essential for reducing development time and adapting to changing requirements.
A time-boxed period in which Agile teams deliver incremental value in the form of working, tested software and systems. Essential for aligning teams, managing dependencies, and ensuring continuous delivery.
An estimation technique used in Agile software development where team members assign story points to tasks through consensus-based discussion. Essential for collaborative and accurate project planning and estimation.
Objectives and Key Results (OKR) is a goal-setting framework for defining and tracking objectives and their outcomes. Essential for aligning organizational goals, improving focus and engagement, and driving measurable results across teams and individuals.
Minimum Viable Feature (MVF) is the smallest possible version of a feature that delivers value to users and allows for meaningful feedback collection. Crucial for rapid iteration in product development, enabling teams to validate ideas quickly and efficiently while minimizing resource investment.