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.
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.
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.
The core principles that underpin agile methodologies, focusing on collaboration, flexibility, and customer satisfaction. Crucial for guiding agile practices and ensuring effective project delivery.
A declaration of the values and principles essential for agile software development. Foundational for understanding the ethos of agile methodologies.
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.
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.
Feature Adoption Rate (FAR) is the percentage of users who adopt a new feature within a specified time period after its release. This metric is important for measuring the success and impact of new product features.
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.
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.
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 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 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.
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.
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 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.
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 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.
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 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 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 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.
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 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.
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.
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.
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 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.
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.
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 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 small, cross-functional team of 6-12 people focused on delivering a specific product feature or component. Essential for agile development, allowing for rapid iteration and close collaboration among team members.
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.
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 visual workflow management method used to visualize work, limit work-in-progress, and maximize efficiency. Crucial for improving workflow and productivity in various processes.
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.
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.
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.
Minimum Viable Product (MVP) is a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development. Essential for validating product ideas quickly and cost-effectively, allowing teams to learn about customer needs without fully developing the product.
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 team structure focused on delivering value streams, often organized around a specific business capability or customer need. Crucial for enhancing delivery efficiency and aligning with business goals.
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.
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 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.
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.
The organizational structure and dynamics of teams within a company, designed to enhance collaboration and delivery. Important for optimizing team performance and project outcomes.
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.
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.
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.
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.
Business Rules Engine (BRE) is a software system that executes one or more business rules in a runtime production environment. Crucial for automating decision-making processes and ensuring consistency and compliance in digital products.
The process of making a new feature available to users, often involving coordination between development, marketing, and support teams. Essential for managing the rollout and communication of new features to users.
A team that supports other teams by providing specialized expertise and tools to improve their performance. Crucial for enhancing overall team effectiveness and efficiency.
Minimum Viable Experience (MVE) is the simplest version of a product that delivers a complete and satisfying user experience while meeting core user needs. Essential for rapidly validating product concepts and user experience designs while ensuring that even early versions of a product provide value and a positive impression to users.
A software development practice where code changes are automatically deployed to production without manual intervention. Important for maintaining a high level of productivity and quality in software development.
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.