Agile Project Management Stakeholder Management
Expert-defined terms from the Professional Certificate in Agile Project Management course at Greenwich School of Business and Finance. Free to read, free to share, paired with a professional course.
Agile Project Management #
Agile Project Management
Agile Project Management is an iterative approach to managing projects that focu… #
It involves breaking down project tasks into small, manageable chunks called iterations or sprints, allowing for continuous feedback and adaptation throughout the project lifecycle. Agile Project Management emphasizes collaboration, flexibility, and customer satisfaction. Common methodologies used in Agile Project Management include Scrum, Kanban, and Extreme Programming (XP).
Stakeholder Management #
Stakeholder Management
Stakeholder Management is the process of identifying, analyzing, and engaging wi… #
Effective stakeholder management is crucial for project success as it helps ensure that stakeholder expectations are understood and managed appropriately. Stakeholders can include project sponsors, team members, customers, end-users, regulators, suppliers, and other key individuals or groups. The goal of stakeholder management is to build positive relationships, manage expectations, and address any concerns or conflicts that may arise during the project.
Agile Manifesto #
Agile Manifesto
The Agile Manifesto is a set of guiding principles for Agile Project Management… #
The Agile Manifesto was created by a group of software developers in 2001 to promote a more flexible, adaptive approach to project management.
Scrum #
Scrum
Scrum is a popular Agile Project Management framework that is used to manage com… #
It is based on iterative and incremental development practices, with a focus on delivering working software in short, fixed periods called sprints. Scrum teams are self-organizing and cross-functional, with roles including the Scrum Master, Product Owner, and Development Team. Scrum ceremonies include Sprint Planning, Daily Standups, Sprint Reviews, and Retrospectives.
Kanban #
Kanban
Kanban is a visual Agile Project Management method that helps teams manage work… #
Kanban boards are used to visualize tasks and their status, with columns representing different stages of the project. Teams can limit the number of tasks in progress at any given time, helping to identify bottlenecks and improve overall productivity. Kanban is based on the principles of continuous improvement and flow.
Extreme Programming (XP) #
Extreme Programming (XP)
Extreme Programming (XP) is an Agile Project Management methodology that focuses… #
XP emphasizes collaboration, feedback, and simplicity, with a strong emphasis on delivering high-quality software quickly. XP teams work closely with customers to prioritize requirements and adapt to changing needs throughout the project.
Product Owner #
Product Owner
The Product Owner is a key role in Agile Project Management responsible for defi… #
The Product Owner acts as the voice of the customer, representing their interests and needs throughout the project. Product Owners work closely with the Scrum Master and Development Team to ensure that the product meets the customer's expectations.
Scrum Master #
Scrum Master
The Scrum Master is a key role in Agile Project Management responsible for facil… #
The Scrum Master acts as a servant-leader, helping the team understand and adopt Agile practices, facilitating communication and collaboration, and coaching team members to improve their performance. Scrum Masters work closely with the Product Owner and Development Team to ensure that project goals are met.
Development Team #
Development Team
The Development Team is a cross #
functional group of individuals in Agile Project Management responsible for delivering the product increment during each sprint. Development Team members may have a variety of skills and expertise, including developers, testers, designers, and analysts. The Development Team is self-organizing, with the autonomy to decide how best to accomplish the work and meet the sprint goals. Development Team members collaborate closely with the Product Owner and Scrum Master to deliver high-quality software.
Sprint #
Sprint
A Sprint is a time #
boxed iteration in Agile Project Management, typically lasting 1-4 weeks, during which a development team works to deliver a potentially shippable product increment. Sprints enable teams to focus on a set of prioritized tasks and goals, with the aim of delivering working software at the end of each sprint. Sprints begin with Sprint Planning, followed by Daily Standups, development work, and end with a Sprint Review and Retrospective to reflect on the sprint outcomes and plan for the next iteration.
Sprint Planning #
Sprint Planning
Sprint Planning is a Scrum ceremony in Agile Project Management where the Scrum… #
Sprint Planning typically consists of two parts: Part 1 involves the Product Owner presenting the prioritized product backlog items and the team discussing the scope and goal of the sprint. Part 2 involves the Development Team breaking down the selected user stories into tasks and estimating the effort required to complete them.
Daily Standup #
Daily Standup
The Daily Standup, also known as the Daily Scrum, is a brief, time #
boxed meeting in Agile Project Management where the Scrum Team comes together to discuss progress, plan for the day, and identify any obstacles or impediments. Daily Standups are typically held at the same time and place each day, with team members standing to keep the meeting short and focused. Each team member answers three questions during the Daily Standup: What did I do yesterday? What will I do today? Are there any impediments blocking my progress?
Sprint Review #
Sprint Review
The Sprint Review is a Scrum ceremony in Agile Project Management where the Scru… #
The Sprint Review is an opportunity for the team to demonstrate the product increment, gather input from stakeholders, and discuss any changes or adjustments that may be needed. The Sprint Review helps ensure that the product meets customer expectations and allows for continuous improvement based on stakeholder feedback.
Retrospective #
Retrospective
The Retrospective is a Scrum ceremony in Agile Project Management where the Scru… #
The Retrospective is an opportunity for the team to review their processes, communication, and collaboration, with the goal of continuously improving their performance. The Retrospective helps teams learn from their experiences, address challenges, and adapt their approach to work more effectively in future sprints.
Backlog #
Backlog
The Backlog is a prioritized list of tasks, features, or user stories in Agile P… #
There are two main types of backlogs: the Product Backlog, which contains all the requirements for the product, and the Sprint Backlog, which contains the tasks to be completed during a specific sprint. Backlogs are dynamic and can be adjusted based on changing priorities, stakeholder feedback, and team capacity.
User Story #
User Story
A User Story is a concise, written description of a feature or functionality fro… #
User Stories typically follow a simple template: "As a [role], I want [feature], so that [benefit]." User Stories help teams understand the user's needs, prioritize work, and deliver value to customers. User Stories are often written on index cards or sticky notes and can be organized on a physical or digital board for visibility and tracking.
Velocity #
Velocity
Velocity is a measure of the amount of work completed by a development team duri… #
It is typically expressed as the number of story points or tasks completed per sprint. Velocity helps teams estimate how much work they can accomplish in future sprints, plan for capacity, and track progress over time. Velocity is calculated by summing the story points or tasks completed in previous sprints and dividing by the number of sprints.
Increment #
Increment
An Increment is the sum of all the completed and potentially shippable product b… #
The Increment represents the work done by the development team during the sprint and is a key outcome of each iteration. Increments should be tested, integrated, and meet the team's definition of done to be considered potentially shippable. The Increment is reviewed during the Sprint Review and may be released to customers if it meets the acceptance criteria.
Definition of Done (DoD) #
Definition of Done (DoD)
The Definition of Done (DoD) is a set of criteria or requirements that must be m… #
The DoD is agreed upon by the Scrum Team and typically includes quality standards, testing requirements, documentation, and any other necessary criteria for a task to be considered done. The DoD ensures that all work completed by the team meets a consistent level of quality and can be delivered to customers.
Product Backlog #
Product Backlog
The Product Backlog is a prioritized list of all the features, tasks, and requir… #
The Product Backlog is owned by the Product Owner and is continually refined and updated based on stakeholder feedback, changing priorities, and team capacity. Items in the Product Backlog are typically described as user stories, epics, or tasks and are estimated in terms of effort or complexity. The Product Backlog serves as a roadmap for the project and guides the team's work throughout the development process.
Sprint Backlog #
Sprint Backlog
The Sprint Backlog is a list of tasks, user stories, or features selected from t… #
The Sprint Backlog is created during Sprint Planning and is owned by the Development Team. It represents the work that the team commits to completing within the sprint and is updated throughout the iteration as tasks are completed, added, or changed. The Sprint Backlog helps the team track progress, prioritize work, and meet the sprint goal.
Impediment #
Impediment
An Impediment is anything that hinders or obstructs the progress of the developm… #
Impediments can include technical challenges, dependencies, communication issues, resource constraints, or any other obstacles that prevent the team from completing their work effectively. It is the role of the Scrum Master to identify and remove impediments to enable the team to be as productive as possible. Addressing impediments promptly helps the team stay on track, meet sprint goals, and deliver value to customers.
Agile Coach #
Agile Coach
An Agile Coach is a mentor, facilitator, and advocate for Agile practices in Agi… #
Agile Coaches work with teams, organizations, and individuals to help them adopt Agile methodologies, improve their processes, and achieve better results. Agile Coaches provide guidance, training, and support to help teams embrace Agile values and principles, overcome challenges, and continuously improve their performance. Agile Coaches may have certifications such as Certified Scrum Master (CSM) or Certified Scrum Product Owner (CSPO).
Agile Transformation #
Agile Transformation
Agile Transformation is the process of transitioning an organization from tradit… #
Agile Transformation involves a shift in mindset, culture, and processes to become more flexible, collaborative, and responsive to change. It requires buy-in from leadership, training for teams, and ongoing support to successfully implement Agile methodologies across the organization. Agile Transformation aims to improve productivity, innovation, and customer satisfaction by embracing Agile principles and practices.
Agile Release Planning #
Agile Release Planning
Agile Release Planning is the process of creating a high #
level roadmap for delivering a product increment over multiple sprints in Agile Project Management. Agile Release Planning involves collaborating with stakeholders to define the product vision, prioritize features, estimate work effort, and create a release schedule. The goal of Agile Release Planning is to align the team around a common vision, set expectations, and create a plan for delivering value to customers incrementally. Agile Release Planning helps teams track progress, manage dependencies, and adapt to changing priorities.
Agile Metrics #
Agile Metrics
Agile Metrics are key performance indicators used to measure the progress, quali… #
Agile Metrics help teams track velocity, cycle time, burndown charts, defect rates, customer satisfaction, and other factors that impact project success. By analyzing Agile Metrics, teams can identify areas for improvement, make data-driven decisions, and demonstrate the value of Agile practices to stakeholders. Common Agile Metrics include velocity, lead time, throughput, and cumulative flow.
Agile Risk Management #
Agile Risk Management
Agile Risk Management is the process of identifying, assessing, and mitigating r… #
Agile Risk Management involves continuously monitoring project risks, adapting to changing conditions, and taking proactive measures to minimize potential negative impacts. Agile Risk Management emphasizes collaboration, transparency, and early identification of risks to ensure that projects remain on track and deliver value to customers. Agile Risk Management is integrated into the project lifecycle and informs decision-making at all levels of the organization.
Agile Estimation #
Agile Estimation
Agile Estimation is the process of sizing and estimating work effort in Agile Pr… #
Agile Estimation involves assigning relative effort estimates, such as story points or t-shirt sizes, to user stories, tasks, or features based on their complexity, risk, and uncertainty. Agile Estimation helps teams prioritize work, plan sprints, and track progress more accurately. By using Agile Estimation techniques, teams can improve their forecasting, reduce uncertainty, and deliver value to customers more consistently.
Agile Retrospective #
Agile Retrospective
The Agile Retrospective is a meeting held at the end of each sprint in Agile Pro… #
The Agile Retrospective is a key practice in Agile Project Management that promotes continuous learning, collaboration, and process improvement. During the Retrospective, team members discuss what went well, what could be improved, and how they can work more effectively in future sprints.
Agile Governance #
Agile Governance
Agile Governance is the framework, processes, and structures that organizations… #
Agile Governance ensures that projects align with strategic objectives, comply with regulations, and deliver value to stakeholders. Agile Governance involves establishing clear roles and responsibilities, defining decision-making processes, and implementing feedback mechanisms to monitor and evaluate project performance. Agile Governance helps organizations balance flexibility and control to achieve project success in an Agile environment.
Agile Requirements #
Agile Requirements
Agile Requirements are the features, functionality, and constraints that define… #
Agile Requirements are captured in the form of user stories, epics, acceptance criteria, and other artifacts that help teams understand and prioritize work. Agile Requirements are dynamic and can evolve based on stakeholder feedback, changing priorities, and team capacity. By focusing on Agile Requirements, teams can deliver value to customers more effectively and adapt to changing needs throughout the project.
Agile Tools #
Agile Tools
Agile Tools are software applications, platforms, and resources that teams use t… #
Agile Tools help teams collaborate, communicate, and visualize work, facilitating transparency, efficiency, and productivity. Common Agile Tools include project management software, version control systems, collaboration platforms, and testing tools. By leveraging Agile Tools, teams can streamline their processes, improve communication, and deliver high-quality software more effectively in an Agile environment.
Agile Culture #
Agile Culture
Agile Culture refers to the values, beliefs, and behaviors that promote collabor… #
Agile Culture emphasizes trust, transparency, flexibility, and a focus on delivering value to customers. Agile Culture encourages teams to embrace change, take risks, and learn from their experiences to drive success. By fostering an Agile Culture, organizations can create a supportive environment that enables teams to thrive, adapt, and deliver results in a dynamic and fast-paced world.
Agile Leadership #
Agile Leadership
Agile Leadership is a style of leadership that empowers teams, fosters collabora… #
Agile Leaders are servant-leaders who focus on developing people, removing obstacles, and creating a culture of continuous improvement. Agile Leaders inspire and motivate teams to embrace change, take ownership of their work, and deliver value to customers. Agile Leadership requires a shift from traditional command-and-control approaches to a more adaptive, inclusive, and supportive mindset.
Agile Communication #
Agile Communication
Agile Communication is the practice of sharing information, feedback, and update… #
Agile Communication involves regular meetings, standups, retrospectives, and other channels for team members to collaborate, discuss progress, and address challenges. Agile Communication promotes alignment, clarity, and collaboration among team members, stakeholders, and customers. By fostering open and honest communication, teams can build trust, resolve issues, and deliver value more efficiently in an Agile environment.
Agile Collaboration #
Agile Collaboration
Agile Collaboration is the practice of working together, sharing knowledge, and… #
Agile Collaboration involves cross-functional teams, self-organizing structures, and a culture of cooperation and mutual respect. Agile Collaboration encourages teams to share responsibilities, skills, and ideas to deliver high-quality products and services. By promoting Agile Collaboration, organizations can increase innovation, productivity, and customer satisfaction in an Agile environment.
Agile Testing #
Agile Testing
Agile Testing is the practice of verifying and validating software continuously… #
Agile Testing involves testing early and often, automating test cases, and collaborating closely with developers to ensure that quality is built into the product. Agile Testing focuses on delivering working software, identifying defects quickly, and adapting to changing requirements. By emphasizing Agile Testing, teams can improve product quality, reduce rework, and deliver value to customers more efficiently in an Agile environment.
Agile Retrospective Techniques #
Agile Retrospective Techniques
Agile Retrospective Techniques are structured activities and methods used to fac… #
Agile Retrospective Techniques help teams identify what went well, what could be improved, and how they can work more effectively in future sprints. Common Agile Retrospective Techniques include Start, Stop, Continue; Mad, Sad, Glad; 4Ls (Liked, Learned, Lacked, Longed for); and Sailboat Retrospective. By using Agile Retrospective Techniques, teams can foster collaboration, innovation, and continuous improvement.
Agile Transformation Challenges #
Agile Transformation Challenges
Agile Transformation Challenges are obstacles, barriers, and resistance that org… #
Agile Transformation Challenges can include cultural resistance, lack of leadership support, limited resources, unclear goals, and difficulty changing established processes. Overcoming Agile Transformation Challenges requires a holistic approach that includes training, coaching, communication, and ongoing support to help teams adapt to Agile methodologies successfully. By addressing Agile Transformation Challenges, organizations can realize the benefits of Agile practices and drive project success.
Agile Portfolio Management #
Agile Portfolio Management
Agile Portfolio Management is the process of prioritizing, planning, and oversee… #
Agile Portfolio Management is the process of prioritizing, planning, and overseeing a