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.
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.
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.
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.
Feature Driven Development (FDD) is an agile methodology focused on designing and building features based on client-valued functionality. Essential for delivering client-valued features efficiently and effectively.
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 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.
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.
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.
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 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 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 broader, more informal community of interest that spans across the entire organization, focusing on shared topics such as agile practices or UX design. Valuable for cross-functional learning, knowledge sharing, and promoting a unified approach to common challenges.
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.
An approach that applies Agile principles to IT operations, emphasizing iterative development, collaboration, and continuous improvement. Essential for enhancing flexibility, responsiveness, and collaboration in product design and development processes.
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 set of practices that combines software development (Dev) and IT operations (Ops) to shorten the development lifecycle and deliver high-quality software continuously. Crucial for improving the speed, efficiency, and quality of software development and deployment.
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.
Test-Driven Development (TDD) is a software development methodology where tests are written before the code that needs to pass them. Essential for ensuring high code quality and reducing bugs.
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 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.
An agile methodology that separates product discovery and product delivery into parallel tracks to ensure continuous learning and delivery. Essential for balancing innovation and execution in agile product development.
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 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.
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 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.
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 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.
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 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 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.
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.
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.
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 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 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.
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 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.
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 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 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 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 practice of performing testing activities earlier in the software development lifecycle to identify and address issues sooner. Essential for improving software quality, reducing defects, and accelerating development cycles in digital product design.
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 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.
A simple description of a feature from the perspective of the user, typically used in Agile development to capture requirements and guide development. Crucial for ensuring that development efforts are aligned with user needs and priorities.
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 common solution to a recurring problem that is ineffective and counterproductive, often resulting in negative consequences. Important for recognizing and avoiding poor design practices and improving overall design quality.
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.
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 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 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 set of shared values, practices, and goals that characterize a startup company. Important for fostering innovation, agility, and a collaborative environment within product design teams.
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 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.
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.