Sprint Demo
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.
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.
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 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 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.
Crit (Design Critique) is a structured feedback session where designers present their work and receive constructive feedback from peers. Essential for refining design quality through collaborative input.
A method where a document or proposal is limited to one page and created within one hour to ensure clarity and focus. Crucial for efficient communication and decision-making.
A cognitive bias where individuals better remember the most recent information they have encountered, influencing decision-making and memory recall. Important for designing user experiences that leverage or mitigate the impact of recent information.
The tendency to believe that large or significant events must have large or significant causes. Important for understanding cognitive biases in decision-making and designing systems that present accurate causal relationships.
The area within a market where unmet needs or problems present potential for new products or services. Essential for identifying new business opportunities.
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.
The practice of promoting and defending the value of design within an organization or community. Crucial for ensuring that design considerations are prioritized and integrated into decision-making processes.
The representation of data through graphical elements like charts, graphs, and maps to facilitate understanding and insights. Essential for making complex data accessible and actionable for users.