Weighted Shortest Job First (WSJF) is a prioritization method used in agile and lean methodologies to maximize value by comparing the cost of delay to the duration of tasks. Essential for effectively prioritizing work to ensure the highest value tasks are completed first.
A visual technique used in Agile development to arrange user stories in a way that helps teams understand the user journey and prioritize work effectively. Crucial for ensuring that development efforts are aligned with user needs and priorities throughout the project.
The process of transitioning an organization to agile methodologies, including changes in culture, processes, and practices. Essential for organizations seeking to adopt agile practices for improved efficiency and responsiveness.
A technique used in agile project management where tasks are estimated using the Fibonacci sequence to reflect the uncertainty and complexity of work. Essential for accurate and realistic task estimation in agile methodologies.
Must have, Should have, Could have, and Won't have (MoSCoW) is a method used to prioritize features or tasks. Crucial for effective project management and ensuring focus on essential features.
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.
SAFe is a framework designed to scale agile practices across large organizations by integrating agile and lean principles. It is widely used but criticized for its rigidity, bureaucratic structure, and potential to stifle true agile culture.
A prioritized list of work items or tasks that need to be completed, commonly used in agile project management. Essential for managing tasks and ensuring that development teams focus on the most important work items.
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.
The process of reviewing, prioritizing, and updating items in the backlog to ensure they are ready for development. Crucial for maintaining an organized and prioritized list of tasks to improve project efficiency.
A role in Agile development responsible for defining the product vision, prioritizing the product backlog, and ensuring the development team delivers value to users. Essential for guiding product development and ensuring alignment with user needs and business goals.
A prioritized list of features, enhancements, and fixes that are intended to be addressed in future product development cycles. Essential for managing and planning product development activities efficiently.
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.
A prioritization framework used to assess and compare the value a feature will deliver to users against the complexity and cost of implementing it. Crucial for making informed decisions about feature prioritization and resource allocation.
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.
A visual exercise that helps product teams understand and prioritize features by organizing user stories into a cohesive narrative that aligns with user journeys and goals. Essential for planning and prioritizing product features and ensuring alignment with user needs.
A prioritization technique where stakeholders use a limited budget to "buy" features they believe are most valuable, helping to prioritize the development roadmap. Useful for involving stakeholders in the decision-making process and aligning development priorities with business value.
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.
Program Increment (PI) Planning is a cadence-based event that serves as the heartbeat of the Agile Release Train, aligning teams on goals and priorities for the next increment. Crucial for aligning teams, setting goals, and planning work.
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.
The core values outlined in the Agile Manifesto, including individuals and interactions, working software, customer collaboration, and responding to change. Fundamental for guiding agile practices and fostering an agile mindset.
The ability of an organization to adapt quickly to market changes and external forces while maintaining a focus on delivering value. Essential for fostering an adaptable and resilient design and development process.
A unit of measure used in Agile project management to estimate the relative effort required to complete a user story or task. Crucial for planning and managing workload within Agile teams.
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.
Impact, Confidence, and Ease of implementation (ICE) is a prioritization framework used in product management to evaluate features. Essential for making informed and strategic decisions about feature development and prioritization.
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 prioritization framework used in product management to evaluate features based on Reach, Impact, Confidence, and Effort. Crucial for making informed decisions about which product features to prioritize and develop.
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.
An agile methodology focused on delivering value to the customer through principles such as eliminating waste, amplifying learning, and delivering as fast as possible. Crucial for improving efficiency and effectiveness in software development processes.
A simple description of a feature from the perspective of the user, typically used in Agile development to capture requirements and guide development. Crucial for ensuring that development efforts are aligned with user needs and priorities.
A visual tool in agile project management that displays tasks to be done, in progress, and completed, often using columns and cards. Crucial for visualizing workflow and managing tasks efficiently.
A prioritized list of ideas and potential features for future product development, embodying a collective vision for innovation and improvement. Essential for managing creative input and maintaining an innovation pipeline that aligns with the team's entrepreneurial spirit and shared commitment to product excellence.
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 term used to describe an organization focused on continuously shipping new features, often at the expense of quality, user experience, or business value. Crucial for recognizing and addressing the pitfalls of prioritizing quantity over quality in feature development.
Cost of Delay (CoD) is a metric that quantifies the economic impact of delaying a project, feature, or task. Important for making informed decisions about project prioritization and resource allocation.
eXtreme Programming (XP) is an agile software development methodology focused on customer satisfaction and continuous improvement. It enhances software quality and responsiveness to changing requirements through frequent releases of functional software.
Product-Oriented Delivery (POD) is a methodology that focuses on organizing teams around products rather than projects. This approach is essential for enhancing product focus, agility, and cross-functional collaboration.
A visual workflow management method used to visualize work, limit work-in-progress, and maximize efficiency. Crucial for improving workflow and productivity in various processes.
A practice of performing testing activities earlier in the software development lifecycle to identify and address issues sooner. Essential for improving software quality, reducing defects, and accelerating development cycles in digital product design.
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.
Product Strategy is a framework that outlines how a product will achieve its business goals and satisfy customer needs. Crucial for guiding product development, prioritizing features, and aligning the team around a clear vision.
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.
The systematic process of capturing, evaluating, and implementing ideas to drive innovation, reflecting a collective commitment to continuous improvement and product excellence. Essential for harnessing team creativity and maintaining the entrepreneurial spirit that characterizes successful product development.
A strategic planning tool that focuses on outcomes and objectives rather than specific features, allowing for flexibility in achieving goals. Important for maintaining strategic focus and adaptability in product development.
A design philosophy that emphasizes core design principles over rigid adherence to standardized processes. Essential for maintaining creativity and innovation in large-scale, process-driven environments.
A focus on the results or benefits of a project rather than the activities or deliverables produced. Crucial for ensuring that efforts are aligned with achieving meaningful results.
A method where a document or proposal is limited to one page and created within one hour to ensure clarity and focus. Crucial for efficient communication and decision-making.
Market Requirements Document (MRD) is a comprehensive document that outlines the market's needs, target audience, and business objectives for a product. It serves as a crucial tool for aligning product development efforts with market demands and business goals, ensuring that the final product meets customer needs and achieves market success.
The implied cost of additional rework caused by choosing an easy or limited solution now instead of using a better approach that would take longer. Essential for understanding and managing the long-term impacts of short-term technical decisions.
A consensus-building technique where participants show their level of agreement or support by raising zero to five fingers. Useful for quickly gauging team agreement and making collaborative decisions in product design and development meetings.
The process of quickly creating a preliminary version of a product to test and validate ideas before full-scale development. Important for validating design concepts and gathering user feedback early.
Feature Adoption Rate (FAR) is the percentage of users who adopt a new feature within a specified time period after its release. This metric is important for measuring the success and impact of new product features.
Product Requirements is a document that outlines the essential features, functionalities, and constraints of a product. Crucial for guiding the development process and ensuring all stakeholders have a shared understanding of the product's goals.
A team focused on designing and improving the user experience across products and services. Essential for ensuring cohesive and high-quality user experiences.
Customer Advisory Board (CAB) is a group of key customers who provide feedback and insights to a company to help guide its strategic decisions. This group is crucial for aligning products and services with customer needs and expectations.
Net Promoter Score (NPS) is a metric used to measure customer loyalty and satisfaction based on their likelihood to recommend a product or service to others. Crucial for gauging overall customer sentiment and predicting business growth through customer advocacy.
Application Release Automation (ARA) is the process of automating the release of applications, ensuring consistency and reducing errors. Crucial for accelerating the delivery of software updates and maintaining high-quality digital products.
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.