Disciplined Agile
A process decision toolkit that allows organizations to tailor their agile practices to their specific needs, promoting agility and continuous improvement. Crucial for optimizing agile practices to fit organizational contexts.
A process decision toolkit that allows organizations to tailor their agile practices to their specific needs, promoting agility and continuous improvement. Crucial for optimizing agile practices to fit organizational contexts.
Large-Scale Scrum (LeSS) is a framework for scaling agile product development to multiple teams working on a single product. It provides a minimalist, large-scale agile approach that maintains the simplicity and effectiveness of Scrum while addressing the challenges of coordination and integration in multi-team environments.
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.
A management framework that organizes employees into small, cross-functional teams (tribes) to enhance agility, collaboration, and innovation. Important for fostering a collaborative and agile work environment.
A declaration of the values and principles essential for agile software development. Foundational for understanding the ethos of agile methodologies.
The core principles that underpin agile methodologies, focusing on collaboration, flexibility, and customer satisfaction. Crucial for guiding agile practices and ensuring effective project delivery.
The process of transitioning an organization to agile methodologies, including changes in culture, processes, and practices. Essential for organizations seeking to adopt agile practices for improved efficiency and responsiveness.
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 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.
SAFe is a framework designed to scale agile practices across large organizations by integrating agile and lean principles. It is widely used but criticized for its rigidity, bureaucratic structure, and potential to stifle true agile culture.
An Agile project management framework that uses iterative cycles, called sprints, to deliver incremental improvements and adapt to changing requirements. Crucial for managing projects in a flexible and iterative manner, ensuring continuous improvement and responsiveness.
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.
Enterprise Architecture (EA) is a strategic framework used to align an organization's business strategy with its IT infrastructure. Crucial for optimizing processes, improving agility, and ensuring that technology supports business goals.
A prioritization framework used to assess and compare the value a feature will deliver to users against the complexity and cost of implementing it. Crucial for making informed decisions about feature prioritization and resource allocation.
Observe, Orient, Decide, and Act (OODA) is a decision-making framework often used in strategic planning and rapid response situations. Crucial for agile decision-making and strategic planning in dynamic environments.
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 relative estimation technique used in Agile project management to quickly assess the size and complexity of tasks by assigning them T-shirt sizes (e.g., small, medium, large). Crucial for efficient project planning and workload management.
The core values outlined in the Agile Manifesto, including individuals and interactions, working software, customer collaboration, and responding to change. Fundamental for guiding agile practices and fostering an agile mindset.
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.
The ability of an organization to adapt quickly to market changes and external forces while maintaining a focus on delivering value. Essential for fostering an adaptable and resilient design and development process.
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.
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.
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.
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.
Objectives and Key Results (OKR) is a goal-setting framework for defining and tracking objectives and their outcomes. Essential for aligning organizational goals, improving focus and engagement, and driving measurable results across teams and individuals.
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 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.
Program Increment (PI) Planning is a cadence-based event that serves as the heartbeat of the Agile Release Train, aligning teams on goals and priorities for the next increment. Crucial for aligning teams, setting goals, and planning work.
Weighted Shortest Job First (WSJF) is a prioritization method used in agile and lean methodologies to maximize value by comparing the cost of delay to the duration of tasks. Essential for effectively prioritizing work to ensure the highest value tasks are completed first.
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.
Culture, Automation, Lean, Measurement, and Sharing (CALMS) is a framework for guiding the implementation of DevOps practices. Important for fostering a DevOps culture and improving collaboration, efficiency, and continuous improvement in product design teams.
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.
The process of reviewing, prioritizing, and updating items in the backlog to ensure they are ready for development. Crucial for maintaining an organized and prioritized list of tasks to improve project efficiency.
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.
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 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 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.
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.
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.
Product Strategy is a framework that outlines how a product will achieve its business goals and satisfy customer needs. Crucial for guiding product development, prioritizing features, and aligning the team around a clear vision.
Product-Oriented Delivery (POD) is a methodology that focuses on organizing teams around products rather than projects. This approach is essential for enhancing product focus, agility, and cross-functional collaboration.
A cross-functional team that is given the autonomy, resources, and authority to make decisions and take ownership of the product's success, focusing on solving user problems and achieving business outcomes. Important for fostering innovation, accountability, and agility, leading to more effective product development and higher user satisfaction.
Minimum Marketable Feature (MMF) is the smallest set of functionality that delivers significant value to users and can be marketed effectively. Crucial for prioritizing development efforts and releasing valuable product increments quickly, balancing user needs with business objectives.
A framework that outlines how a product is developed, managed, and delivered, including roles, processes, and tools used throughout its lifecycle. Crucial for ensuring efficient and effective product management and development.
A mindset and approach that embodies the entrepreneurial spirit, passion for improvement, and deep sense of ownership typically associated with a company's founders. Essential for maintaining agility, innovation, and customer-centricity as organizations grow and mature.
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 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.
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.
A framework for discovering and validating the right market for a product, building the right product features, and validating the business model. Important for ensuring that products meet market needs and customer expectations.
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.
A group of individuals with similar skills or expertise, spread across different squads, who come together to share knowledge and best practices. Crucial for maintaining technical excellence and fostering professional development within specific disciplines.
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.
Minimum Viable Feature (MVF) is the smallest possible version of a feature that delivers value to users and allows for meaningful feedback collection. Crucial for rapid iteration in product development, enabling teams to validate ideas quickly and efficiently while minimizing resource investment.
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.
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 team that supports other teams by providing specialized expertise and tools to improve their performance. Crucial for enhancing overall team effectiveness and efficiency.
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 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 strategic management template for developing new business models or documenting existing ones, detailing elements like value proposition, infrastructure, and customers. Important for understanding and designing business strategies that align with product and user experience goals.
An environment closer to production where final testing and validation occur. Crucial for ensuring that products are ready for production deployment.