Decision Making in Agile Projects
Expert-defined terms from the Professional Certificate in Decision Making in Project Governance course at London School of Business and Administration. Free to read, free to share, paired with a globally recognised certification pathway.
Agile Projects Decision Making Glossary #
Agile Projects Decision Making Glossary
Agile Projects Decision Making #
The process of making choices and selecting courses of action in Agile projects to achieve project goals efficiently and effectively while adapting to changing circumstances.
Decision Making #
The cognitive process of selecting a course of action from multiple alternatives based on available information and preferences.
Agile #
A project management methodology that emphasizes flexibility, collaboration, and incremental development to deliver value to customers.
Projects #
Temporary endeavors with a defined beginning and end, undertaken to create a unique product, service, or result.
Professional Certificate #
A credential awarded upon completion of a program that signifies expertise and proficiency in a specific field.
Project Governance #
The framework that ensures projects are effectively managed, controlled, and executed to achieve organizational objectives.
Terms #
Acceptance Criteria #
Conditions that a product or deliverable must satisfy to be accepted by the customer or stakeholders.
Backlog #
A prioritized list of requirements or tasks that need to be completed in a project.
Burn Down Chart #
A graphical representation of work completed versus work remaining in a sprint or project.
Change Control Board (CCB) #
A group responsible for reviewing and approving changes to a project.
Collaboration #
Working together with others to achieve a common goal.
Continuous Integration #
The practice of frequently integrating code changes into a shared repository.
Customer #
The individual or group for whom a product or service is being developed.
Deliverable #
A tangible or intangible product or service that is produced as part of a project.
Empirical Process Control #
A control method based on observation, experimentation, and adaptation.
Epic #
A large body of work that can be broken down into smaller, more manageable tasks.
Incremental Development #
The iterative process of building and delivering a product in small increments.
Iteration #
A time-boxed period in Agile projects during which a set of tasks or requirements are completed.
Kanban #
A visual management tool used to track work in progress and optimize workflow.
Lean #
A methodology focused on maximizing customer value while minimizing waste.
Minimum Viable Product (MVP) #
The version of a product with the minimum features to satisfy early customers and collect feedback.
Product Owner #
The individual responsible for defining and prioritizing product requirements.
Retrospective #
A meeting held at the end of a sprint to review what went well and what could be improved.
Sprint #
A time-boxed period in Agile projects, usually lasting 1-4 weeks, during which a set of tasks are completed.
Scrum #
An Agile framework that emphasizes teamwork, accountability, and iterative progress.
Scrum Master #
The individual responsible for facilitating the Scrum process and removing obstacles.
Stakeholder #
An individual or group who has an interest in or is affected by the outcome of a project.
Story Points #
An estimation technique used in Agile projects to assign relative sizes to tasks.
Velocity #
The rate at which a team completes work in an Agile project, usually measured in story points.
Waterfall #
A traditional project management methodology that follows a linear approach to project delivery.
WIP Limit #
Work in Progress Limit; a constraint on the number of tasks that can be in progress at any given time.
Value Stream Mapping #
A visual representation of the steps involved in delivering a product or service to the customer.
Challenges #
Uncertainty #
Agile projects often involve a high degree of uncertainty due to changing requirements and unknown variables.
Time Constraints #
Balancing the need to deliver value quickly with the quality of the product can be challenging in Agile projects.
Scope Creep #
The tendency for project scope to expand beyond the original requirements, leading to delays and increased costs.
Resource Allocation #
Allocating resources effectively to meet project deadlines and deliver value to customers is a common challenge in Agile projects.
Communication #
Ensuring clear and effective communication among team members, stakeholders, and customers can be a challenge in Agile projects.
Risk Management #
Identifying and mitigating risks to project success is critical in Agile projects, where changes are frequent.
Dependencies #
Managing dependencies between tasks, teams, and external factors can be complex in Agile projects.
Examples #
Example 1 #
In an Agile software development project, the product owner decides to prioritize a feature based on customer feedback collected during a sprint review meeting.
Example 2 #
During a retrospective meeting, the team identifies a communication breakdown as a key issue that affected the progress of the project in the previous sprint.
Example 3 #
The Scrum Master facilitates a daily stand-up meeting where team members discuss their progress, challenges, and plans for the day.
Example 4 #
The project manager uses a burn down chart to track the team's progress and identify any potential delays in completing the sprint.
Practical Applications #
Application 1 #
Prioritizing the backlog based on customer feedback and business value to ensure the most important features are delivered first.
Application 2 #
Conducting regular retrospectives to identify areas for improvement and implement changes to enhance team performance.
Application 3 #
Using story points to estimate task complexity and allocate resources effectively to meet project deadlines.
Application 4 #
Implementing WIP limits to optimize workflow and reduce bottlenecks in the development process.
Application 5 #
Collaborating with stakeholders and customers throughout the project to ensure their needs are met and expectations are managed.
Conclusion #
Decision making in Agile projects is a critical aspect of project governance that requires effective communication, collaboration, and adaptability to achieve project success. By understanding the key terms, concepts, and challenges associated with decision making in Agile projects, project managers and team members can make informed choices and deliver value to customers in a dynamic and fast-paced environment.