Story Points
A unit of measure used in Agile project management to estimate the relative effort required to complete a user story or task. Crucial for planning and managing workload within Agile teams.
A unit of measure used in Agile project management to estimate the relative effort required to complete a user story or task. Crucial for planning and managing workload within Agile teams.
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 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.
The practicality of implementing a solution based on technical constraints and capabilities. Crucial for evaluating the viability of design and development projects.
The risk that the product cannot be built as envisioned due to technical limitations, resource constraints, or other practical challenges. Important for confirming that the product can be realistically developed and deployed with the available technology and resources.
A senior technical role responsible for guiding the development team and ensuring the technical quality of projects. Important for maintaining technical standards and mentoring team members.
Adaptive Software Development (ASD) is a software development methodology that focuses on continuous adaptation to changing requirements and environments. Essential for managing changing requirements and ensuring agile project delivery.
A detailed strategy outlining the timeline, milestones, and deliverables for a product release, ensuring that all activities are aligned and completed on schedule. Essential for coordinating efforts and ensuring a successful product launch.
A short, daily meeting (separate from Standup) for the development team to sync on progress and plan for the day, part of the Scrum agile framework. Crucial for maintaining team alignment and momentum in agile projects.
Also known as Parkinson's Law of Triviality, is the tendency to spend excessive time on trivial details while neglecting more important issues. Crucial for improving project management and team efficiency.
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 meeting at the end of a sprint where the development team presents their completed work to stakeholders. Crucial for gathering feedback and demonstrating progress.
An analysis comparing the costs and benefits of a decision or project to determine its feasibility and value. Important for making informed business and design decisions.
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 organizational structure and dynamics of teams within a company, designed to enhance collaboration and delivery. Important for optimizing team performance and project outcomes.
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 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 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.
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 structure within an organization focused on managing and integrating complex subsystems. Important for ensuring seamless integration and functionality of complex projects.
Return on Investment (ROI) is a performance measure used to evaluate the efficiency or profitability of an investment or compare the efficiency of different investments. Crucial for assessing the financial effectiveness of business decisions, projects, or initiatives.
Products are individual items or services designed to meet specific customer needs, while programs are collections of related projects and products managed together to achieve broader strategic goals. Essential for understanding the different scopes and objectives involved, helping to manage and align efforts effectively within an organization.
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".
The comprehensive process of planning, executing, and overseeing all activities related to the introduction of a new product to the market. Crucial for coordinating efforts to ensure a successful product launch and achieving market impact.
A Gestalt principle where the mind completes incomplete figures to form a whole, aiding in the perception of shapes and objects. Crucial for designing visual elements that are easily understood by users.
The process of collecting and documenting the needs and expectations of stakeholders for a new or modified product or system. Essential for ensuring that the final product meets user needs and business objectives.
An event where developers, designers, and other stakeholders collaborate intensively on software projects, typically within a short timeframe. Important for fostering innovation, team collaboration, and rapid prototyping of new ideas in digital product development.
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 prioritized list of features, enhancements, and fixes that are intended to be addressed in future product development cycles. Essential for managing and planning product development activities efficiently.
A set of criteria that a user story or task must meet before being accepted into the development cycle, ensuring it is actionable and clear. Essential for ensuring that tasks are well-defined and ready for development.
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.
A strategic plan that outlines the goals, milestones, and steps needed to deliver a product that achieves desired outcomes incrementally, providing a clear path forward. Essential for guiding product development and ensuring alignment with strategic objectives.
The evaluation of products based on their ability to influence and shape user behavior. Useful for assessing how well a product guides and influences user actions and decisions.
A detailed schedule outlining the key milestones and activities leading up to and following the launch of a new product. Important for ensuring timely execution of all tasks related to the product launch.
A professional responsible for overseeing the planning and execution of a product launch, ensuring alignment with strategic goals and successful market entry. Essential for managing the complexities of launching a new product and coordinating cross-functional teams.
The series of stages a product goes through from initial concept to market release, including planning, design, development, testing, and launch. Essential for understanding the full lifecycle of product creation and bringing products to market efficiently.
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.
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.
The application of behavioral science principles to design products that influence user behavior in a desired way. Crucial for creating products that effectively guide user behavior and improve outcomes.
A strategic approach where multiple potential solutions are tested to identify the most promising one. Crucial for innovation and reducing risk in decision-making.
Impact, Confidence, and Ease of implementation (ICE) is a prioritization framework used in product management to evaluate features. Essential for making informed and strategic decisions about feature development and prioritization.
The process of bringing a product from development to market, ensuring it meets quality standards and customer needs. Crucial for the successful launch and adoption of a product.
A prioritization technique where stakeholders use a limited budget to "buy" features they believe are most valuable, helping to prioritize the development roadmap. Useful for involving stakeholders in the decision-making process and aligning development priorities with business value.
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.
A skill set that combines deep knowledge in a single area (the vertical stroke) with a broad understanding across multiple disciplines (the horizontal stroke). Valuable for fostering versatility and collaboration within teams, enhancing problem-solving and innovation.
The tendency to overestimate how much our future preferences and behaviors will align with our current preferences and behaviors. Important for understanding user behavior and designing experiences that account for changes over time.
A strategy used to determine the proportion of various SMEs needed to support a pipeline of work. Important for optimizing resource allocation, enhancing efficiency, and ensuring teams have the appropriate support based on design demand and complexity.
A brief daily meeting in Agile project management where team members share updates on their progress, plans for the day, and any obstacles they face. Essential for maintaining communication, transparency, and coordination within Agile teams.
Node Package Manager (NPM) is a package manager for JavaScript, enabling developers to share and reuse code modules in their projects. Crucial for managing dependencies and streamlining development workflows in JavaScript applications.
A visual workflow management method used to visualize work, limit work-in-progress, and maximize efficiency. Crucial for improving workflow and productivity in various processes.
A methodology that promotes iterative development, collaboration, and flexibility to adapt to changing requirements. Crucial for product managers and development teams to deliver high-quality products efficiently.
A list of tasks and deliverables that a team commits to completing during a sprint, providing a clear focus and scope for the sprint's duration. Essential for organizing and prioritizing work within an Agile sprint.
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.
A short, time-boxed period used in Agile development to research a concept or explore a new technology. Important for reducing uncertainty and risk in development.
A regular meeting in Agile project management where team members discuss progress, plan work, and identify any obstacles, typically held daily. Crucial for maintaining communication, transparency, and accountability within Agile teams.
The core principles that underpin agile methodologies, focusing on collaboration, flexibility, and customer satisfaction. Crucial for guiding agile practices and ensuring effective project delivery.
A collection of multiple squads working in the same domain or on related projects, typically consisting of 40-150 people. Important for ensuring alignment and coordination across related squads, fostering a larger community with shared goals.
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 strategic planning technique that uses visual maps to align activities with business goals and user needs. Essential for ensuring that development efforts are aligned with strategic objectives.
An overarching idea or theme that guides the design process, providing direction and coherence to the final product. Essential for ensuring that all design elements align with a central vision and purpose.