Dynamic Systems Development Method (DSDM) is an agile project delivery framework focused on delivering business value early and continuously. Essential for ensuring that projects align with business goals and user needs through iterative processes.
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.
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 practice of quickly testing and iterating on ideas to validate assumptions and learn from user feedback in a short time frame. Essential for agile development and making data-driven decisions efficiently.
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.
A team structure focused on delivering value streams, often organized around a specific business capability or customer need. Crucial for enhancing delivery efficiency and aligning with business goals.
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.
The set of shared values, practices, and goals that characterize a startup company. Important for fostering innovation, agility, and a collaborative environment within product design teams.
A small, cross-functional team of 6-12 people focused on delivering a specific product feature or component. Essential for agile development, allowing for rapid iteration and close collaboration among team members.
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.
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 team responsible for delivering specific features or enhancements, typically working on predefined requirements and focusing on the implementation of assigned features. Important for executing well-defined tasks and ensuring timely delivery of specific functionalities within a product.
Observe, Orient, Decide, and Act (OODA) is a decision-making framework often used in strategic planning and rapid response situations. Crucial for agile decision-making and strategic planning in dynamic environments.
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.
The organizational structure and dynamics of teams within a company, designed to enhance collaboration and delivery. Important for optimizing team performance and project outcomes.
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 set of practices that combines software development (Dev) and IT operations (Ops) to shorten the development lifecycle and deliver high-quality software continuously. Crucial for improving the speed, efficiency, and quality of software development and deployment.
The process of identifying, assessing, and controlling dependencies between tasks or projects to minimize risks and ensure smooth project execution. Crucial for effective project management and delivery.
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.
Test-Driven Development (TDD) is a software development methodology where tests are written before the code that needs to pass them. Essential for ensuring high code quality and reducing bugs.
A team that supports other teams by providing specialized expertise and tools to improve their performance. Crucial for enhancing overall team effectiveness and efficiency.
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.
The use of software tools to run tests on code automatically, ensuring functionality and identifying defects without manual intervention. Crucial for maintaining high code quality and efficiency in the development process.
A quick and cost-effective usability testing method where feedback is gathered from users in informal settings, often in public places. Useful for gaining rapid insights into user behavior and improving designs iteratively.
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.
An informal usability testing method where random passersby are asked to try out a product or feature and provide feedback. Essential for quickly identifying usability issues with minimal resources.
A software development practice where code changes are automatically deployed to production without manual intervention. Important for maintaining a high level of productivity and quality in software development.
A strategic management template for developing new business models or documenting existing ones, detailing elements like value proposition, infrastructure, and customers. Important for understanding and designing business strategies that align with product and user experience goals.
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.
Application Lifecycle Management (ALM) is the process of managing an application's development, maintenance, and eventual retirement throughout its lifecycle. Important for ensuring the sustainability and effectiveness of digital products over time.
A framework that outlines how a product is developed, managed, and delivered, including roles, processes, and tools used throughout its lifecycle. Crucial for ensuring efficient and effective product management and development.
The process of making small, continuous improvements to products, services, or processes over time. Important for sustaining growth and maintaining competitiveness through ongoing improvements.
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 group of individuals with similar skills or expertise, spread across different squads, who come together to share knowledge and best practices. Crucial for maintaining technical excellence and fostering professional development within specific disciplines.
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.
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.
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.
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.
A testing phase where a product is released to a limited audience outside the development team to identify issues and gather feedback before the final release. Essential for refining a product based on real user feedback and ensuring it meets user needs.
A user experience design methodology focused on rapid iteration, collaboration, and learning through experimentation. Essential for creating user-centered designs efficiently and effectively.
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.
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.
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.
An ongoing process of learning about user needs and validating assumptions through continuous research and experimentation. Crucial for staying responsive to user needs and improving products iteratively.
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.
A structured routine for continuous improvement based on a scientific approach to problem-solving and process optimization. Crucial for fostering a culture of continuous improvement and innovation within product design teams.
A type of testing conducted to determine if the requirements of a specification are met, often the final step before delivery to the customer. Important for ensuring that a product meets the defined criteria and is ready for release.
A system where outputs are fed back into the process as inputs, allowing for continuous improvement based on user responses. Crucial for iterative development and continuous improvement in design and product management.
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.
The process of making a new feature available to users, often involving coordination between development, marketing, and support teams. Essential for managing the rollout and communication of new features to users.
A technique used in software development to enable or disable features in a production environment without deploying new code, allowing for controlled feature rollouts. Essential for managing feature releases and testing in live environments.
A team focused on designing and improving the user experience across products and services. Essential for ensuring cohesive and high-quality user experiences.
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.
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.
An event where developers, designers, and other stakeholders collaborate intensively on software projects, typically within a short timeframe. Important for fostering innovation, team collaboration, and rapid prototyping of new ideas in digital product development.
A testing method where the internal structure of the system is not known to the tester, focusing solely on input and output. Essential for validating the functionality of digital products from an end-user perspective.
The process of changing the corporate image of an organization, including its name, logo, visual identity, and messaging, to better align with its strategic goals. Important for revitalizing a brand and aligning it with current market positioning and business objectives.
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.
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.
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.