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.
Specific attributes used to enhance the accessibility of web content and applications by providing additional information to assistive technologies. Crucial for making dynamic web content more accessible to users with disabilities.
Any process or administrative barrier that unnecessarily complicates transactions and creates friction, discouraging beneficial behaviors. Important for identifying and eliminating unnecessary obstacles that hinder user experiences.
Software that acts as an intermediary between different systems or applications, enabling them to communicate and function together. Crucial for integrating various components and ensuring seamless interaction within digital products.
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 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 decision-making tool that helps prioritize tasks or projects based on specific criteria, such as impact and effort. Essential for effective project management and resource allocation.
Simple Knowledge Organization System (SKOS) is a standard for representing knowledge organization systems such as thesauri, classification schemes, and taxonomies. Essential for enabling interoperability and sharing of structured knowledge across different systems.
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.
Mutually Exclusive, Collectively Exhaustive (MECE) is a problem-solving framework ensuring that categories are mutually exclusive and collectively exhaustive, avoiding overlaps and gaps. Essential for structured thinking and comprehensive analysis in problem-solving.
The Principle of Growth is an information architecture guideline that plans for the future expansion and evolution of a system. Crucial for ensuring that information structures can scale and adapt over time.
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.
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.
The ability of an organization to adapt quickly to market changes and external forces while maintaining a focus on delivering value. Essential for fostering an adaptable and resilient design and development process.
An iterative design process that focuses on the users and their needs at every phase of the design process. Crucial for creating products that are effective, efficient, and satisfying for the end users.
A process decision toolkit that allows organizations to tailor their agile practices to their specific needs, promoting agility and continuous improvement. Crucial for optimizing agile practices to fit organizational contexts.
The Principle of Disclosure is an information architecture guideline that promotes revealing information progressively as users need it. Crucial for managing complexity and preventing information overload.
Application Programming Interface (API) is a set of tools and protocols that allow different software applications to communicate and interact with each other. Essential for integrating different systems and enabling functionality in digital products.
A cognitive bias where group members tend to discuss information that everyone already knows rather than sharing unique information, leading to less effective decision-making. Important for understanding group dynamics and improving the quality of collaborative decision-making among designers.
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 design language developed by Google that uses shadow, depth, and motion to create a realistic and intuitive user interface. Crucial for creating modern, consistent, and user-friendly interfaces.
The practice of promoting and representing the needs, interests, and rights of users in the design and development process. Important for ensuring that user needs and perspectives are prioritized in product design and development.
Product-Oriented Delivery (POD) is a methodology that focuses on organizing teams around products rather than projects. This approach is essential for enhancing product focus, agility, and cross-functional collaboration.
A preliminary testing phase conducted by internal staff to identify bugs before releasing the product to external testers or customers. Crucial for ensuring product quality and functionality before broader release.
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 server dedicated to automating the process of building and compiling code, running tests, and generating software artifacts. Crucial for ensuring continuous integration and maintaining the integrity of the codebase in digital product development.
A set of fundamental principles and guidelines that inform and shape marketing practices. Crucial for maintaining consistency and ensuring high-quality marketing outcomes.
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.
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.
Program Increment (PI) Planning is a cadence-based event that serves as the heartbeat of the Agile Release Train, aligning teams on goals and priorities for the next increment. Crucial for aligning teams, setting goals, and planning work.
A collection of pre-written code and tools that provide a foundation for building the front end of websites and applications, such as Bootstrap or React. Crucial for streamlining the development process and ensuring consistency.
The process of maintaining, updating, and improving a product or system after its initial deployment to ensure its continued functionality, performance, and relevance to users. Crucial for ensuring long-term user satisfaction, product reliability, and adaptation to changing user needs and technological advancements.
Balanced Scorecard (BSC) is a strategic planning and management system used to align business activities to the vision and strategy of the organization. Essential for aligning business activities with organizational strategy and improving performance.
The process of determining whether there is a need or demand for a product in the target market, often through testing and feedback. Crucial for ensuring that a product will meet market needs and be successful.
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.
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.
A strategic framework that designs user experiences to guide behavior and decisions towards desired outcomes. Crucial for creating effective and ethical influence in digital interfaces.
Providing clear, concise, and relevant navigation options to help users find what they need quickly. Crucial for improving user experience and efficiency in digital products.
The practice of planning and organizing people, infrastructure, communication, and material components of a service to improve its quality and the interaction between service providers and customers. Essential for creating effective and user-centered service experiences.
A specific viewport dimension at which a website's layout adjusts to provide an optimal viewing experience across different screen sizes. Crucial for responsive web design to ensure usability on various devices.
Numeronym for the word "Modularization" (M + 12 letters + N), dividing a system into separate, interchangeable modules that can be developed, tested, and maintained independently. Important for improving maintainability and scalability of systems.
A time-constrained, intensive process that helps teams quickly design, prototype, and test ideas. Important for rapidly developing and validating design solutions.
The process of tailoring a product or experience to meet the individual needs and preferences of users. Essential for enhancing user engagement and satisfaction by delivering relevant experiences.
A leadership philosophy where the leader prioritizes the needs of the team, empowering and supporting members to achieve their full potential and fostering a collaborative, inclusive environment. Important for building strong, motivated teams, enhancing collaboration, and promoting a culture of trust and respect within an organization.
Also known as "Maslow's Hammer," a cognitive bias where people rely too heavily on a familiar tool or method, often summarized as "if all you have is a hammer, everything looks like a nail.". Important for designers to recognize and avoid over-reliance on familiar methods in problem-solving and design.
A model of organizational change management that involves preparing for change (unfreeze), implementing change (change), and solidifying the new state (refreeze). Important for successfully implementing and sustaining changes in product design processes and organizational practices.
A reusable solution to common design problems that provides a standard way of addressing recurring issues in design. Essential for creating consistent and efficient design solutions.
Performance and Accountability Reporting (PAR) is a comprehensive document that outlines an organization's performance in achieving its goals and its accountability in managing resources. This report is essential for transparency, governance, and continuous improvement.
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.
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.
A brand architecture strategy where all products share a common brand name and identity. Essential for creating a cohesive brand image and leveraging brand equity across products.
Key Performance Indicators (KPIs) are quantifiable measures used to evaluate the success of an organization, employee, or project in meeting objectives for performance. Essential for tracking progress, making informed decisions, and aligning efforts with strategic goals across various business functions, including product design and development.
The practice of guiding and inspiring teams to create effective, user-centered design solutions that align with business goals. Crucial for fostering a culture of innovation, collaboration, and excellence in design practices within organizations.
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.
A declaration of the values and principles essential for agile software development. Foundational for understanding the ethos of agile methodologies.
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.
A role in Agile project management responsible for ensuring the team follows Agile practices, facilitating meetings, and removing obstacles to progress. Essential for supporting Agile teams and ensuring successful implementation of Scrum practices.
A brainstorming technique where participants write down their ideas independently before sharing them with the group. Crucial for generating a wide range of ideas and encouraging participation from all team members.
The initial meeting or phase where a new feature or initiative is introduced, discussed, and planned, involving all relevant stakeholders. Important for ensuring clear communication and alignment on new feature development.
User Acceptance Testing (UAT) is the final phase of the software testing process where actual users test the software to ensure it meets their requirements. Crucial for validating that the software functions correctly in real-world scenarios before its release.