Engineering Backlog
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 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 approach to design that actively involves all stakeholders (e.g., employees, partners, customers) in the design process. Crucial for creating designs that truly meet user needs and expectations.
A method of creating and testing user interfaces using hand-drawn sketches and mockups on paper. Essential for early-stage design validation and gathering user feedback.
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.
The process of testing product ideas and assumptions with real customers to ensure they meet market needs. Essential for reducing risk and ensuring product-market fit.
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.
A framework for discovering and validating the right market for a product, building the right product features, and validating the business model. Important for ensuring that products meet market needs and customer expectations.
Large Language Model (LLM) is an advanced artificial intelligence system trained on vast amounts of text data to understand and generate human-like text. Essential for natural language processing tasks, content generation, and enhancing human-computer interactions across various applications in product design and development.
A usability evaluation method where evaluators walk through tasks to identify potential user difficulties. Essential for improving user interfaces and ensuring usability.
A demonstration of the new features and functionalities of a product release, typically used to showcase progress and gather feedback before the official launch. Crucial for validating product features and gathering stakeholder feedback before a full release.
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.
The process of designing, developing, and managing tools and techniques for measuring performance and collecting data. Essential for monitoring and improving system performance and user experience.
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 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 clear and concise statement that defines the purpose and goals of a product, guiding its development and strategic direction. Crucial for aligning product development efforts with organizational vision and goals.
Research conducted to assess the effectiveness, usability, and impact of a design or product. Essential for validating design decisions and improving user experiences.
A usability testing method where users interact with a system they believe to be autonomous, but which is actually operated by a human. Essential for testing concepts and interactions before full development.
A design philosophy that views constraints as opportunities for creativity and innovation, rather than limitations. Crucial for fostering a mindset that turns limitations into design strengths.
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 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 usability testing method where participants verbalize their thoughts while interacting with a product. Essential for understanding user thought processes and identifying usability issues.
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.
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.
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 preliminary testing method to check whether the most crucial functions of a software application work, without going into finer details. Important for identifying major issues early in the development process and ensuring the stability of digital products.
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.
A user-centered design process that involves understanding users' needs and workflows through field research and applying these insights to design. Essential for creating designs that are deeply informed by user contexts and behaviors.
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 type of software testing that ensures that recent changes have not adversely affected existing features. Essential for maintaining software quality and reliability.
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.
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.
Integrated Development Environment (IDE) is a software suite that combines tools like code editors, debuggers, and compilers. Essential for improving developer productivity and ensuring efficient and error-free coding practices.
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 method of comparing two versions of a webpage or app to see which performs better in terms of user engagement or conversions. Crucial for designers and product managers to test variations and optimize user experience and performance.
Feature Driven Development (FDD) is an agile methodology focused on designing and building features based on client-valued functionality. Essential for delivering client-valued features efficiently and effectively.
The process of creating and developing new products, focusing on form, function, usability, and aesthetics to meet user needs. Crucial for developing products that are both functional and appealing to users.
The process of understanding user behaviors, needs, and motivations through various qualitative and quantitative methods. Essential for designing user-centered products and ensuring they meet actual user needs.
A design process model that outlines four phases: Discover, Define, Develop, and Deliver, promoting both divergent and convergent thinking. Crucial for structuring the design process and fostering both creativity and precision.
A technique used to evaluate a product or system by testing it with real users to identify any usability issues and gather qualitative and quantitative data on their interactions. Crucial for identifying and resolving usability issues to improve user satisfaction and performance.
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.
Joint Application Development (JAD) is a collaborative approach to gathering requirements and designing solutions in software development projects. It facilitates rapid decision-making and consensus-building by bringing together key stakeholders, including users, developers, and project managers, in structured workshop sessions.
Interaction Design (IxD) focuses on creating engaging interfaces with well-thought-out behaviors. Crucial for ensuring intuitive and effective user interactions.
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.