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.
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.
Goal-Question-Metrics (GQM) is a framework for defining and interpreting software metrics by identifying goals, formulating questions to determine if the goals are met, and applying metrics to answer those questions. This framework is essential for measuring and improving software quality and performance.
Software Development Life Cycle (SDLC) is a process for planning, creating, testing, and deploying an information system. Essential for managing the complexities of software development and ensuring project success.
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.
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.
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.
In-product assistance provided within the context of a specific task or screen, tailored to the user's current needs. Important for enhancing user experience by providing timely and relevant assistance.
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 detailed description of a system's behavior as it responds to a request from one of its stakeholders, often used to capture functional requirements. Essential for understanding and documenting how users will interact with a system to achieve their 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.
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 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.
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 dark pattern where the user is required to do something in order to access certain functionality or information. Designers must avoid compulsory actions and provide optional choices to respect user autonomy.
Drivers, Approvers, Contributors, and Informed (DACI) is a responsibility assignment framework that clarifies roles and responsibilities. Essential for making clear and effective decisions in collaborative environments.
The design of products, devices, services, or environments for people with disabilities or specific needs. Crucial for creating inclusive products that can be used by everyone, including those with disabilities.
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.
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.
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.
A heuristic where individuals evenly distribute resources across all options, regardless of their specific needs or potential. Useful for understanding and designing around simplistic decision-making strategies.
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.
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.
Elements in a design that draw the viewer's attention and create a visual hierarchy. Essential for guiding user attention and improving the effectiveness of visual communication.
Walk the Wall (WTW) is a practice where team members physically move along a wall displaying their project's progress, discussing and updating tasks. Essential for fostering team collaboration and ensuring transparency in project status.
The process of identifying and assessing the influence and interest of various stakeholders in a project, to prioritize engagement and communication strategies. Crucial for effectively managing stakeholder relationships and ensuring project success.
Statement of Work (SOW) is a formal document that outlines the scope, objectives, deliverables, and timelines for a project. Essential for defining project expectations and ensuring all parties have a clear understanding of their responsibilities.
A Project Management Office (PMO) is a centralized unit within an organization that oversees and standardizes project management practices. Essential for ensuring consistency, efficiency, and alignment with strategic goals across projects.