Burndown Chart
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 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 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.
A project management technique that identifies the longest sequence of dependent tasks and calculates the shortest possible project duration. Essential for optimizing project timelines and ensuring timely delivery of digital products.
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.
The process of identifying, assessing, and controlling dependencies between tasks or projects to minimize risks and ensure smooth project execution. Crucial for effective project management and delivery.
A scheduling term that indicates a delay in the project timeline that cannot be recovered. Important for identifying and addressing potential project delays, ensuring timely delivery of digital products.
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 sequence of phases through which a product or project passes from conception to completion. Essential for managing and tracking the progress of development projects.
Goals, Ideas, Steps, and Tasks (GIST) is an agile planning technique to break down projects into manageable parts. Essential for organizing and executing agile projects effectively.
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.
The process of managing multiple related projects in a coordinated way to achieve strategic business objectives. Crucial for ensuring alignment and efficiency across multiple projects to achieve broader goals.
A clear and concise list of criteria that a product or task must meet to be considered complete, ensuring alignment and understanding within a team. Essential for maintaining quality and consistency in agile project management.
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.
The organizational structure and dynamics of teams within a company, designed to enhance collaboration and delivery. Important for optimizing team performance and project outcomes.
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.
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.
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.
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 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 professional responsible for overseeing and coordinating multiple related projects to ensure they align with organizational goals and deliver strategic value. Essential for managing complex initiatives and ensuring successful delivery of business objectives.
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.
A cognitive bias where individuals underestimate the time, costs, and risks of future actions while overestimating the benefits. Important for realistic project planning and setting achievable goals for designers.
A principle that states tasks always take longer than expected, even when considering Hofstadter's Law itself. Important for setting realistic project timelines and managing expectations in digital product development.
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.
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.
A meeting held at the end of a project or development cycle, also known as a "post-mortem," to review what went well, what didn't, and how processes can be improved in the future. Crucial for continuous improvement and learning from past experiences to enhance future projects.
Must have, Should have, Could have, and Won't have (MoSCoW) is a method used to prioritize features or tasks. Crucial for effective project management and ensuring focus on essential features.
Cost of Delay (CoD) is a metric that quantifies the economic impact of delaying a project, feature, or task. Important for making informed decisions about project prioritization and resource allocation.
An agile framework for managing work with an emphasis on software development, characterized by sprints and iterative progress. Essential for improving productivity and delivering incremental value in development projects.
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 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 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 time-boxed period during which specific work must be completed and made ready for review, used in Agile project management. Crucial for managing workload and ensuring continuous delivery and improvement in Agile projects.
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.
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.
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 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.
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 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 prioritized list of tasks, features, and technical debt items that need to be addressed by the engineering team. Essential for managing and organizing work in software development projects.
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.
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.
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.
A systematic process for determining and addressing needs or gaps between current conditions and desired outcomes. Important for identifying user requirements and guiding the development of digital products that meet those needs.
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.
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 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 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 method used to create detailed narratives of potential future events to explore and understand possible outcomes and inform decision-making. Essential for strategic planning and anticipating the impact of different decisions or changes.
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.
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 product development approach where teams start with the desired customer experience and work backwards to determine what needs to be built to achieve that outcome. Essential for ensuring that product development is aligned with customer needs and expectations.
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 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.
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 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.
Goal-Question-Metrics (GQM) is a framework for defining and interpreting software metrics by identifying goals, formulating questions to determine if the goals are met, and applying metrics to answer those questions. This framework is essential for measuring and improving software quality and performance.
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.