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.
The abilities and knowledge required to effectively plan, execute, and close projects, including leadership, communication, time management, and risk management. Essential for ensuring successful project outcomes and achieving business objectives.
Walk the Wall (WTW) is a practice where team members physically move along a wall displaying their project's progress, discussing and updating tasks. Essential for fostering team collaboration and ensuring transparency in project status.
Statement of Work (SOW) is a formal document that outlines the scope, objectives, deliverables, and timelines for a project. Essential for defining project expectations and ensuring all parties have a clear understanding of their responsibilities.
The systematic identification, analysis, planning, and implementation of actions designed to engage and influence stakeholders in a project. Crucial for maintaining positive relationships and ensuring stakeholder support throughout the project lifecycle.
Numeronym for the word "Communications" (C + 12 letters + S). Essential for effective collaboration and information exchange.
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.
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.
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.
Responsible, Accountable, Consulted, and Informed (RACI) is a responsibility assignment framework that clarifies roles and responsibilities in a projec. Crucial for ensuring clear communication and accountability in project management.
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.
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.
Detailed, Estimated, Emergent, and Prioritized (DEEP) is an agile project management framework for a well-maintained product backlog. Important for maintaining a clear and actionable backlog in agile methodologies.
Software Development Life Cycle (SDLC) is a process for planning, creating, testing, and deploying an information system. Essential for managing the complexities of software development and ensuring project success.
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 professional responsible for planning, executing, and closing projects, ensuring they are completed on time, within scope, and on budget. Crucial for managing project activities and ensuring successful delivery of project goals.
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.
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 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.
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.
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 set of practices and principles that guide agile methodologies, such as Scrum and Kanban, to improve project management and product development. Important for structuring agile practices and ensuring effective project delivery.
Joint Application Development (JAD) is a collaborative approach to gathering requirements and designing solutions in software development projects. It facilitates rapid decision-making and consensus-building by bringing together key stakeholders, including users, developers, and project managers, in structured workshop sessions.
Drivers, Approvers, Contributors, and Informed (DACI) is a responsibility assignment framework that clarifies roles and responsibilities. Essential for making clear and effective decisions in collaborative environments.
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 visual tool in agile project management that displays tasks to be done, in progress, and completed, often using columns and cards. Crucial for visualizing workflow and managing tasks efficiently.
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 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.
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.
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 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.
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 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 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.
Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes in a workflow, using standardized symbols and notations. Essential for creating clear, standardized diagrams that facilitate understanding and communication of business processes in digital product design.
Work that is not performed in real-time, allowing team members to collaborate without needing to be online simultaneously. Crucial for increasing flexibility and productivity in remote and distributed teams.
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.
Model-Based Systems Engineering (MBSE) is a methodology that uses visual modeling to support system requirements, design, analysis, and validation activities throughout the development lifecycle. Essential for managing complex systems, improving communication among stakeholders, and enhancing the overall quality and efficiency of systems engineering processes.
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".
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.
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.
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.
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 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 structured framework for organizing information, defining the relationships between concepts within a specific domain to enable better understanding, sharing, and reuse of knowledge. Important for creating clear and consistent data models, improving communication, and enhancing the efficiency of information retrieval and management.
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 simplified, informal language used to describe the logic and steps of an algorithm or program, without syntax of actual programming languages. Useful for planning and communicating algorithms and program structures before implementation in digital product development.
An approach to design where content is prioritized and designed before other elements like layout and visual design. Crucial for ensuring that the design supports and enhances the content.
A framework used in graphic and web design to organize content in a structured and consistent manner. Essential for creating balanced and readable layouts.
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 development responsible for defining the product vision, prioritizing the product backlog, and ensuring the development team delivers value to users. Essential for guiding product development and ensuring alignment with user needs and business goals.
The process of working together with others to generate creative ideas and solutions, leveraging diverse perspectives and skills. Essential for producing innovative and well-rounded design solutions.
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.
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.
Agile Release Train (ART) is a long-lived team of Agile teams that, along with other stakeholders, incrementally develops, delivers, and operates one or more solutions in a value stream. Important for coordinating Agile development and delivery at scale.
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.