Dual-Track Agile
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.
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 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.
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.
A preliminary version of a project or system used to test and validate its feasibility before full-scale implementation. Crucial for identifying potential issues and making necessary adjustments to improve the final product.
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 collection of multiple squads working in the same domain or on related projects, typically consisting of 40-150 people. Important for ensuring alignment and coordination across related squads, fostering a larger community with shared goals.
A strategic planning tool that outlines the future direction of a project or product using Kanban principles, emphasizing continuous delivery and improvement. Important for aligning team efforts and maintaining focus on long-term goals.
Digital Asset Management (DAM) is a system that stores, organizes, and manages digital assets, such as images, videos, and documents. Essential for maintaining and leveraging digital content efficiently in product design and marketing.
A strategy used to determine the proportion of various SMEs needed to support a pipeline of work. Important for optimizing resource allocation, enhancing efficiency, and ensuring teams have the appropriate support based on design demand and complexity.
A lightweight, flexible approach to software development that emphasizes team communication and continuous improvement. Useful for tailoring agile practices to fit the specific needs of the development team.
A project or venture that starts from scratch, with no constraints imposed by prior work, enabling innovation and flexibility in development. Essential for recognizing opportunities for innovation and fresh development in business initiatives.
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 senior technical role responsible for guiding the development team and ensuring the technical quality of projects. Important for maintaining technical standards and mentoring team members.
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 document that defines the functionality, behavior, and features of a system or component. Important for providing clear requirements and expectations for product design and development teams, ensuring alignment and successful project outcomes.
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.
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 principle in lean management aimed at reducing non-value-added activities to improve efficiency. Important for optimizing processes and resource use.
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.
The process of setting short-term objectives and determining the actions needed to achieve them. Critical for aligning daily operations with strategic goals.
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.
Specific conditions that must be met for a product or feature to be considered complete and satisfactory. Essential for product managers and developers to ensure clarity and alignment on what constitutes "done".
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.
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.
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 repository for team members to submit and collect innovative ideas, reflecting a commitment to fostering creativity and shared ownership of product development. Crucial for maintaining an open culture of innovation and capturing diverse perspectives that contribute to the product's evolution and success.
Domain-Driven Design (DDD) is an approach to software development that focuses on modeling the business domain and its logic. Essential for aligning software development with business needs and creating maintainable systems.
Behavior-Driven Development (BDD) is a software development approach where applications are specified and designed by describing their behavior. Important for ensuring clear communication and shared understanding between developers and stakeholders.
A software development practice where code changes are automatically prepared for a release to production. Crucial for ensuring rapid and reliable deployment of updates.
A methodology that focuses on minimizing waste and maximizing value in business processes. Essential for improving efficiency, productivity, and customer satisfaction by eliminating non-value-adding activities.
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.
New Product Development (NPD) is the complete process of bringing a new product to market, from idea generation to commercialization. Essential for companies to innovate, stay competitive, and meet evolving customer needs through a structured approach to creating and launching new offerings.
A strategic planning technique that uses visual maps to align activities with business goals and user needs. Essential for ensuring that development efforts are aligned with strategic objectives.
Model-Based Systems Engineering (MBSE) is a methodology that uses visual modeling to support system requirements, design, analysis, and validation activities throughout the development lifecycle. Essential for managing complex systems, improving communication among stakeholders, and enhancing the overall quality and efficiency of systems engineering processes.
A series of numbers where each number is the sum of the two preceding ones, creating a pattern found in nature and various fields. Useful for understanding natural growth patterns, efficient estimation techniques, and its relationship to the aesthetically pleasing Golden Ratio.
Proof of Concept (PoC) is a demonstration, usually in the form of a prototype or pilot project, to verify that a concept or theory has practical potential. Crucial for validating ideas, demonstrating feasibility, and securing support for further development in product design and innovation processes.
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.
Product Development is the process of bringing a new product to market or improving an existing one. Crucial for innovation, meeting customer needs, and maintaining a competitive edge.
Model-View-Controller (MVC) is an architectural pattern that separates an application into three main logical components: the Model (data), the View (user interface), and the Controller (processes that handle input). Essential for creating modular, maintainable, and scalable software applications by promoting separation of concerns.
A cross-functional team focused on solving customer problems and achieving business outcomes, with a strong emphasis on discovery, experimentation, and continuous improvement. Crucial for creating valuable and innovative products that meet user needs and drive business success through iterative development and close collaboration with stakeholders.