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 collection of reusable components, guided by clear standards, that can be assembled to build any number of applications, ensuring consistency and efficiency. Crucial for maintaining design consistency and efficiency across products.
Goals, Ideas, Steps, and Tasks (GIST) is an agile planning technique to break down projects into manageable parts. Essential for organizing and executing agile projects effectively.
A software development practice where code changes are frequently integrated into a shared repository, with each change being verified by automated tests. Essential for catching errors early and improving the quality of software.
A programming paradigm that uses objects and classes to structure software design, promoting reusability and scalability. Crucial for developing maintainable and scalable software systems.
A type of bar chart that represents a project schedule, showing the start and finish dates of elements within the project. Important for planning and visualizing project timelines and dependencies.
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.
Situation-Complication-Resolution (SCR) is a communication and problem-solving framework used to structure information clearly and logically. Crucial for effectively conveying complex ideas and solutions in business and design contexts.
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.
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 decision-making strategy where individuals allocate resources proportionally to the probability of an outcome occurring, rather than optimizing the most likely outcome. Important for understanding decision-making behaviors and designing systems that guide better resource allocation.
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.
The study of the relationships between people, practices, values, and technologies within an information environment. Helps in understanding and designing systems that are sustainable and adaptive to human and environmental changes.
A method used in AI and machine learning to ensure prompts and inputs are designed to produce the desired outcomes. Essential for improving the accuracy and relevance of AI responses.
Short, exploratory design activities or exercises that encourage creative thinking and experimentation. Important for fostering creativity and innovation in the design process.
A brainstorming technique that involves listing all possible attributes of a product or problem to generate new ideas and solutions. Useful for generating creative solutions and improving product features.
SAFe is a framework designed to scale agile practices across large organizations by integrating agile and lean principles. It is widely used but criticized for its rigidity, bureaucratic structure, and potential to stifle true agile culture.
Conversations with key stakeholders to gather insights, expectations, and feedback, ensuring their needs are understood and considered in the project. Essential for aligning project goals with stakeholder needs and obtaining valuable input for decision-making.
The practice of designing products, services, and environments with a focus on the overall user experience. Essential for creating holistic and meaningful interactions.
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.
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.
A document that outlines the objectives, scope, deliverables, and timeline of a project, providing clear direction and expectations for all stakeholders. Crucial for ensuring clear communication and alignment among project stakeholders.
A cognitive bias where people assume others share the same beliefs, values, or preferences as themselves. Important for helping designers avoid projecting their own biases and assumptions onto users during research and design.
A cognitive bias where individuals overestimate how well their thoughts, feelings, and emotions are understood by others. Crucial for designing communication and user interfaces that account for and mitigate this bias.
Artificial Superintelligence (ASI) is a hypothetical AI that surpasses human intelligence and capability in all areas. Important for understanding the potential future impacts and ethical considerations of AI development.
Guidelines and principles designed to ensure that AI systems are developed and used in a manner that is ethical and responsible. Crucial for building trust and ensuring the responsible use of AI technologies.
The Project Management Body of Knowledge (PMBOK) is a comprehensive set of guidelines, best practices, and standards for project management. Essential for ensuring consistency and excellence in managing projects across various industries.
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.
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.
The process of generating a broad set of ideas on a given topic, with no attempt to judge or evaluate them initially. Crucial for creative problem-solving and developing innovative solutions in product design and development.
A time-boxed period in which Agile teams deliver incremental value in the form of working, tested software and systems. Essential for aligning teams, managing dependencies, and ensuring continuous delivery.
The study of how people interact with their environment and products, aiming to improve comfort, efficiency, and safety. Crucial for designing user-friendly and safe products and workspaces.
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 role responsible for ensuring that products and services are delivered efficiently, on time, and within budget. Crucial for managing project timelines, resources, and stakeholder expectations.
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.
The ability to influence others' behavior by offering positive incentives or rewards, commonly used in organizational and social contexts. Crucial for understanding dynamics of motivation and influence in team and organizational settings.
The practice of drawing inspiration from sources outside of one's field to generate creative ideas. Useful for fostering creativity and innovation in design and product development.
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.
A high-level description of the future state of a product, outlining its purpose, target audience, and key differentiators. Essential for providing direction and inspiration for product development efforts.
A visual tool for organizing information, typically starting with a central concept and branching out to related ideas and details. Essential for brainstorming, planning, and organizing complex information.
A creative thinking technique where the typical process is reversed to generate new ideas by considering the opposite of conventional assumptions. Useful for fostering innovation and challenging existing assumptions in problem-solving.
A visual tool used to map out the components and features of a product, showing how they relate to each other and to the overall product vision. Useful for visualizing and planning product development, ensuring all elements are aligned with the product vision.
A meeting held at the end of a project or development cycle, also known as a "post-mortem," to review what went well, what didn't, and how processes can be improved in the future. Crucial for continuous improvement and learning from past experiences to enhance future projects.
Numeronym for the word "Documentation" (D + 11 letters + N), creating detailed records and instructions to support the development, use, and maintenance of systems or products. Crucial for ensuring users and developers understand and properly use the system or product.
Detailed descriptions of a product's features, functionality, and technical requirements, used to guide development and ensure all stakeholders are aligned. Essential for ensuring that the product development process is clear and aligned with business and user needs.
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 principle that states tasks always take longer than expected, even when considering Hofstadter's Law itself. Important for setting realistic project timelines and managing expectations in digital product development.
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.
A marketing strategy that involves releasing a product to a limited audience to evaluate its market performance before a full-scale launch. Important for assessing market response, identifying potential issues, and refining digital products before a wider release.
Large-Scale Scrum (LeSS) is a framework for scaling agile product development to multiple teams working on a single product. It provides a minimalist, large-scale agile approach that maintains the simplicity and effectiveness of Scrum while addressing the challenges of coordination and integration in multi-team environments.
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 cognitive bias where individuals favor others who are perceived to be similar to themselves, affecting judgments and decision-making. Crucial for understanding biases in team dynamics and decision-making processes among designers.
An environment closer to production where final testing and validation occur. Crucial for ensuring that products are ready for production deployment.
A graphical representation showing the amount of work remaining versus time, used in agile project management to track progress. Crucial for managing project progress and ensuring timely completion of tasks.
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.
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 cognitive bias where people judge the likelihood of an event based on its relative size rather than absolute probability. Important for understanding user decision-making biases and designing systems that present information accurately.
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.
The tendency to favor people who are similar to oneself in terms of background, beliefs, or interests. Important for recognizing and mitigating bias in user research and team dynamics.
The belief in one's ability to create change through creativity, often leading to more innovative and effective problem-solving. Essential for fostering a mindset of innovation and creativity in design.