A cognitive bias where individuals or organizations continue to invest in a failing project or decision due to the amount of resources already committed. Important for designers to recognize and mitigate their own risks of continuing unsuccessful initiatives.
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.
Adaptive Software Development (ASD) is a software development methodology that focuses on continuous adaptation to changing requirements and environments. Essential for managing changing requirements and ensuring agile project delivery.
The practicality of implementing a solution based on technical constraints and capabilities. Crucial for evaluating the viability of design and development projects.
A detailed strategy outlining the timeline, milestones, and deliverables for a product release, ensuring that all activities are aligned and completed on schedule. Essential for coordinating efforts and ensuring a successful product launch.
The risk that the product cannot be built as envisioned due to technical limitations, resource constraints, or other practical challenges. Important for confirming that the product can be realistically developed and deployed with the available technology and resources.
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.
An analysis comparing the costs and benefits of a decision or project to determine its feasibility and value. Important for making informed business and design decisions.
A team structure within an organization focused on managing and integrating complex subsystems. Important for ensuring seamless integration and functionality of complex projects.
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 short, daily meeting (separate from Standup) for the development team to sync on progress and plan for the day, part of the Scrum agile framework. Crucial for maintaining team alignment and momentum in agile projects.
Also known as Parkinson's Law of Triviality, is the tendency to spend excessive time on trivial details while neglecting more important issues. Crucial for improving project management and team efficiency.
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 product development methodology that emphasizes shaping work before starting it, fixing time and team size but leaving scope flexible to ensure high-quality outcomes. Crucial for managing product development efficiently and delivering high-quality results within constraints.
A psychological state where individuals feel as though the success and well-being of a project or task is their personal responsibility, akin to having an "owner's mentality.". Essential for fostering accountability, motivation, and proactive engagement within a product design team.
The organizational structure and dynamics of teams within a company, designed to enhance collaboration and delivery. Important for optimizing team performance and project outcomes.
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.
The potential for a project or solution to be economically sustainable and profitable. Important for ensuring that design and development efforts align with business goals and market demands.
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.
Software Requirements Specification (SRS) is a detailed document that outlines the functional and non-functional requirements of a software system. Crucial for ensuring clear communication and understanding between stakeholders and the development team.
The comprehensive process of planning, executing, and overseeing all activities related to the introduction of a new product to the market. Crucial for coordinating efforts to ensure a successful product launch and achieving market impact.
Return on Investment (ROI) is a performance measure used to evaluate the efficiency or profitability of an investment or compare the efficiency of different investments. Crucial for assessing the financial effectiveness of business decisions, projects, or initiatives.
Products are individual items or services designed to meet specific customer needs, while programs are collections of related projects and products managed together to achieve broader strategic goals. Essential for understanding the different scopes and objectives involved, helping to manage and align efforts effectively within an organization.
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 team that supports other teams by providing specialized expertise and tools to improve their performance. Crucial for enhancing overall team effectiveness and efficiency.
A group of people who share a common interest or profession and engage in collective learning through regular interactions, sharing knowledge, and developing expertise together. Essential for fostering collaboration, continuous learning, and the dissemination of best practices within a specific field or discipline.
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".
A set of criteria that a user story or task must meet before being accepted into the development cycle, ensuring it is actionable and clear. Essential for ensuring that tasks are well-defined and ready for development.
A document that provides a high-level overview of a product, including its objectives, target market, key features, and requirements, used to guide development efforts. Essential for ensuring that all stakeholders have a clear and consistent understanding of the product.
The process of collecting and documenting the needs and expectations of stakeholders for a new or modified product or system. Essential for ensuring that the final product meets user needs and business objectives.
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.
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.
The ability to use learned knowledge and experience, often increasing with age and accumulated learning. Important for understanding how expertise and knowledge accumulation impact design and decision-making.
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.
A strategic plan that outlines the goals, milestones, and steps needed to deliver a product that achieves desired outcomes incrementally, providing a clear path forward. Essential for guiding product development and ensuring alignment with strategic objectives.
A detailed schedule outlining the key milestones and activities leading up to and following the launch of a new product. Important for ensuring timely execution of all tasks related to the product launch.
A professional responsible for overseeing the planning and execution of a product launch, ensuring alignment with strategic goals and successful market entry. Essential for managing the complexities of launching a new product and coordinating cross-functional teams.
A cognitive bias where individuals with low ability at a task overestimate their ability, while experts underestimate their competence. Crucial for designers to create educational content and user interfaces that accommodate varying levels of user expertise.
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.
The series of stages a product goes through from initial concept to market release, including planning, design, development, testing, and launch. Essential for understanding the full lifecycle of product creation and bringing products to market efficiently.
A skill set that combines deep knowledge in a single area (the vertical stroke) with a broad understanding across multiple disciplines (the horizontal stroke). Valuable for fostering versatility and collaboration within teams, enhancing problem-solving and innovation.
A strategic approach where multiple potential solutions are tested to identify the most promising one. Crucial for innovation and reducing risk in decision-making.
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.
The process of bringing a product from development to market, ensuring it meets quality standards and customer needs. Crucial for the successful launch and adoption of a product.
A visual tool that maps out opportunities and the corresponding solutions, helping teams identify and prioritize where to focus their efforts. Crucial for strategic planning and ensuring alignment between problems and solutions.
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 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.
The tendency to overestimate how much our future preferences and behaviors will align with our current preferences and behaviors. Important for understanding user behavior and designing experiences that account for changes over time.
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 regular meeting in Agile project management where team members discuss progress, plan work, and identify any obstacles, typically held daily. Crucial for maintaining communication, transparency, and accountability within Agile teams.
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 brief daily meeting in Agile project management where team members share updates on their progress, plans for the day, and any obstacles they face. Essential for maintaining communication, transparency, and coordination within Agile teams.
Node Package Manager (NPM) is a package manager for JavaScript, enabling developers to share and reuse code modules in their projects. Crucial for managing dependencies and streamlining development workflows in JavaScript applications.
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 short, time-boxed period used in Agile development to research a concept or explore a new technology. Important for reducing uncertainty and risk in development.
The core principles that underpin agile methodologies, focusing on collaboration, flexibility, and customer satisfaction. Crucial for guiding agile practices and ensuring effective project delivery.
A methodology that promotes iterative development, collaboration, and flexibility to adapt to changing requirements. Crucial for product managers and development teams to deliver high-quality products efficiently.
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.
Specific, Measurable, Achievable, Relevant, and Time-bound (SMART) Goals are a framework for setting and achieving clear objectives. Essential for setting clear and actionable objectives in personal and professional contexts.
An overarching idea or theme that guides the design process, providing direction and coherence to the final product. Essential for ensuring that all design elements align with a central vision and purpose.