The process of identifying, assessing, and mitigating potential threats that could impact the success of a digital product, including usability issues, technical failures, and user data security. Essential for maintaining product reliability, user satisfaction, and data protection, while minimizing the impact of potential design and development challenges.
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 hybrid Agile project management framework that combines elements of Scrum and Kanban to improve flexibility and workflow management. Useful for teams seeking to blend the structured approach of Scrum with the visual workflow of Kanban.
Plan-Do-Check-Act (PDCA) is an iterative four-step management method used for continuous improvement of processes and products. Essential for quality control and operational efficiency.
Numeronym for the word "Communications" (C + 12 letters + S). Essential for effective collaboration and information exchange.
An ongoing effort to improve products, services, or processes over time through incremental and breakthrough improvements. Crucial for fostering a culture of constant enhancement and adaptation.
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.
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.
Plan, Do, Check, and Act (PDCA) is a four-step management method used for continuous improvement of processes and products. Essential for implementing and maintaining continuous improvement in business and design processes.
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.
An organizational environment that encourages and supports creative thinking, risk-taking, and the pursuit of new ideas. Essential for fostering continuous improvement and breakthrough advancements.
Application Lifecycle Management (ALM) is the process of managing an application's development, maintenance, and eventual retirement throughout its lifecycle. Important for ensuring the sustainability and effectiveness of digital products over time.
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.
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.
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 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.
An agile methodology that separates product discovery and product delivery into parallel tracks to ensure continuous learning and delivery. Essential for balancing innovation and execution in agile product development.
A software development practice where code changes are automatically deployed to production without manual intervention. Important for maintaining a high level of productivity and quality in software development.
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 team that supports other teams by providing specialized expertise and tools to improve their performance. Crucial for enhancing overall team effectiveness and efficiency.
An environment closer to production where final testing and validation occur. Crucial for ensuring that products are ready for production deployment.
A team structure focused on delivering value streams, often organized around a specific business capability or customer need. Crucial for enhancing delivery efficiency and aligning with business goals.
Minimum Viable Experience (MVE) is the simplest version of a product that delivers a complete and satisfying user experience while meeting core user needs. Essential for rapidly validating product concepts and user experience designs while ensuring that even early versions of a product provide value and a positive impression to users.
ARIA attributes that describe the current state of an element, such as whether it is selected or expanded. Crucial for providing context and improving navigation for users with disabilities.
Redundant, outdated, or unnecessary code or design elements that accumulate over time in a system. Important for identifying and removing to maintain clean, efficient, and maintainable systems and interfaces.
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.
A strategic planning tool that outlines the future direction of a project or product using Kanban principles, emphasizing continuous delivery and improvement. Important for aligning team efforts and maintaining focus on long-term goals.
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.
Perceivable, Operable, Understandable, and Robust (POUR) are the four main principles of web accessibility. These principles are essential for creating inclusive digital experiences that can be accessed and used by people with a wide range of abilities and disabilities.
A quick and cost-effective usability testing method where feedback is gathered from users in informal settings, often in public places. Useful for gaining rapid insights into user behavior and improving designs iteratively.
An estimation technique used in Agile software development where team members assign story points to tasks through consensus-based discussion. Essential for collaborative and accurate project planning and estimation.
The process of anticipating, detecting, and resolving errors in software or systems to ensure smooth operation. Important for creating reliable and user-friendly software applications.
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".
Web Accessibility Initiative รป Accessible Rich Internet Applications (WAI-ARIA) is a set of guidelines for making web content and applications accessible. Essential for ensuring web accessibility and inclusivity for people with disabilities.
Accessible Rich Internet Applications (ARIA) is a set of attributes that enhance the accessibility of web content for people with disabilities. Essential for making web applications more usable and inclusive.
3-Tiered Architecture is a software design pattern that separates an application into three layers: presentation, logic, and data. Crucial for improving scalability, maintainability, and flexibility in software development.
A strategic approach where decisions and direction are set by top-level management and flow down through the organization, often aligned with overarching business goals. Crucial for ensuring strategic alignment and coherence across all levels of an organization.
A performance testing method that evaluates the system's behavior and stability over an extended period under a high load. Essential for identifying memory leaks and ensuring the reliability and performance of digital products under prolonged use.
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.
The process of evaluating the impact and success of a feature after its release, based on predefined metrics and user feedback. Crucial for understanding the effectiveness of features and informing future development.
A usability inspection method where experts review a user interface against a set of heuristics to identify usability issues. Crucial for identifying usability problems early in the design process.
A semi-fictional representation of an ideal customer based on market research and real data about existing customers. Essential for targeting design and marketing efforts to meet the needs and preferences of specific user groups.
A practice of performing testing activities in the production environment to monitor and validate the behavior and performance of software in real-world conditions. Crucial for ensuring the stability, reliability, and user satisfaction of digital products in a live environment.
A cognitive bias where individuals underestimate their own abilities and performance relative to others, believing they are worse than average. Important for understanding self-perception biases among designers and designing systems that support accurate self-assessment.
Areas of unmet demand in a market where opportunities for growth and development exist. Essential for identifying new business opportunities.
A framework that incorporates privacy considerations into the design and development of products and services from the outset. Crucial for ensuring user privacy and compliance with data protection regulations.
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.
Business-to-Business (B2B), a business model where products or services are sold from one business to another. Crucial for understanding business markets and developing inter-business strategies.
A prioritization method that assigns different weights to criteria based on their importance, helping to make informed decisions and prioritize tasks effectively. Crucial for making objective and balanced decisions in project management and product development.
A visual representation of the user or customer journey, highlighting key interactions, emotions, and pain points. Essential for identifying opportunities to improve user or customer experiences.
A research method that focuses on understanding phenomena through in-depth exploration of human behavior, opinions, and experiences, often using interviews or observations. Essential for gaining deep insights into user needs and behaviors to inform design and development.
A cognitive bias where individuals overestimate their own abilities, qualities, or performance relative to others. Important for understanding user self-perception and designing systems that account for inflated self-assessments.
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.
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.
A role responsible for overseeing multiple product managers and ensuring alignment and collaboration across different product lines within an organization. Crucial for coordinating efforts and driving strategic product development.
The design of user interfaces for machines and software, such as computers, mobile devices, and other electronic devices, with the focus on maximizing usability and the user experience. Essential for ensuring that digital products are intuitive and easy to use.
A preliminary version of a project or system used to test and validate its feasibility before full-scale implementation. Crucial for identifying potential issues and making necessary adjustments to improve the final product.
A large body of work that can be broken down into smaller tasks or user stories, used in agile project management to organize work. Essential for managing and organizing large projects in agile development.
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.
Web Accessibility Initiative (WAI) is a program developed by W3C to improve web accessibility. Essential for creating guidelines and resources to help make the web accessible to people with disabilities.