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 Program Evaluation and Review Technique (PERT) chart is a project management tool used to schedule, organize, and coordinate tasks within a project, representing the project timeline and dependencies graphically. Essential for planning and managing complex projects efficiently.
Enterprise Project Management (EPM) is a comprehensive approach to managing projects across an entire organization. Essential for coordinating complex, cross-functional projects and achieving organizational objectives.
Also known as feature creep, the continuous addition of new features to a product, often beyond the original scope, leading to project delays and resource strain. Important for managing project scope and ensuring timely delivery.
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 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.
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 Project Management Office (PMO) is a centralized unit within an organization that oversees and standardizes project management practices. Essential for ensuring consistency, efficiency, and alignment with strategic goals across projects.
A prioritized list of work items or tasks that need to be completed, commonly used in agile project management. Essential for managing tasks and ensuring that development teams focus on the most important work items.
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.
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.
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.
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.
The process of handling changes to software, hardware, or documentation in a systematic way. Critical for maintaining consistency and ensuring system integrity.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
The process of performing a series of seemingly unrelated and often tedious tasks that are necessary to solve a larger problem. Important for recognizing and managing the indirect tasks that contribute to achieving the main objectives in digital product design.
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.
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.
A programming paradigm that uses objects and classes to structure software design, promoting reusability and scalability. Crucial for developing maintainable and scalable software systems.
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 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.
A central location where data is stored and managed. Important for ensuring data consistency, accessibility, and integrity in digital products.
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 team structure within an organization focused on managing and integrating complex subsystems. Important for ensuring seamless integration and functionality of complex projects.
A distributed version control system for tracking changes in source code during software development. Essential for collaborative development and managing codebase evolution in digital product design.
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.
A software development practice where code changes are automatically prepared for a release to production. Crucial for ensuring rapid and reliable deployment of updates.
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.
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.
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.
The process of overseeing and coordinating the development, testing, and deployment of software releases to ensure they are delivered efficiently and effectively. Essential for managing software development cycles and ensuring successful product releases.
An agile methodology focused on delivering value to the customer through principles such as eliminating waste, amplifying learning, and delivering as fast as possible. Crucial for improving efficiency and effectiveness in software development processes.
A measure used in Agile project management to quantify the amount of work a team can complete in a given sprint, typically measured in story points. Crucial for planning and forecasting in Agile projects and understanding team capacity.
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.
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.
Domain-Driven Design (DDD) is an approach to software development that focuses on modeling the business domain and its logic. Essential for aligning software development with business needs and creating maintainable systems.
eXtreme Programming (XP) is an agile software development methodology focused on customer satisfaction and continuous improvement. It enhances software quality and responsiveness to changing requirements through frequent releases of functional software.
A time management tool that helps prioritize tasks based on their urgency and importance, dividing them into four quadrants. Essential for designing productivity tools and strategies.
The implied cost of additional rework caused by choosing an easy or limited solution now instead of using a better approach that would take longer. Essential for understanding and managing the long-term impacts of short-term technical decisions.
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 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 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 project or venture that starts from scratch, with no constraints imposed by prior work, enabling innovation and flexibility in development. Essential for recognizing opportunities for innovation and fresh development in business initiatives.
Rapid Application Development (RAD) is a software development methodology that emphasizes quick prototyping and iterative delivery. Essential for reducing development time and adapting to changing requirements.
The high-level structure of a software application, defining its components and their interactions. Essential for designing robust, scalable, and maintainable digital products.