Agile Team Dynamics and Facilitation
Expert-defined terms from the Advanced Skill Certificate in Team Leadership for Software Development (United Kingdom) course at LearnUNI. Free to read, free to share, paired with a professional course.
Agile Manifesto #
Agile Manifesto
The Agile Manifesto is a set of four values and twelve principles that gu… #
It emphasizes individuals and interactions over processes, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
*Example* #
A team adopts the manifesto by prioritising frequent releases that deliver usable features rather than waiting for a large, monolithic release.
*Practical application* #
Use the manifesto as a reference during sprint retrospectives to evaluate whether the team’s behaviours align with the values.
*Challenges* #
Translating high‑level values into day‑to‑day actions can be ambiguous; teams may revert to “waterfall‑like” documentation habits when under pressure.
Agile Principles #
Agile Principles
These are the twelve guiding statements that expand the manifesto’s values, such… #
These are the twelve guiding statements that expand the manifesto’s values, such as delivering working software frequently, welcoming changing requirements, and maintaining a sustainable pace.
*Example* #
A product owner embraces changing priorities by re‑prioritising the backlog after each sprint.
*Practical application* #
Review each principle during sprint planning to ensure the team’s commitments reflect them.
*Challenges* #
Teams often struggle to balance “continuous delivery” with technical debt, leading to shortcuts that violate the principle of technical excellence.
Agile Team #
Agile Team
An Agile Team is a small, self‑organising group that possesses all the sk… #
The team collaborates closely, shares responsibility, and adapts its workflow continuously.
*Example* #
A team of developers, testers, UX designers, and a product owner works together without hand‑offs, completing a feature from concept to deployment within a sprint.
*Practical application* #
Encourage the team to collectively decide how to split work during sprint planning, fostering ownership.
*Challenges* #
Achieving true cross‑functionality can be difficult in organisations where specialist silos dominate, leading to bottlenecks.
Architecture Spike #
Architecture Spike
A time‑boxed investigation used to explore a technical approach or architectural… #
It produces a lightweight artefact—often a prototype or a set of findings—rather than production‑ready code.
*Example* #
The team allocates a half‑day spike to evaluate whether a microservices architecture can meet latency requirements.
*Practical application* #
Include spikes in the sprint backlog with clear acceptance criteria to avoid scope creep.
*Challenges* #
Spikes can be over‑used, draining capacity from feature work; also, the outcomes may be ambiguous if not well‑defined.
Backlog Grooming #
Backlog Grooming
The ongoing process of reviewing, clarifying, and prioritising items in the prod… #
It involves adding details, estimating effort, and removing obsolete items.
*Example* #
The product owner meets with the team weekly to split large epics into manageable user stories and assign story points.
*Practical application* #
Schedule a regular 60‑minute grooming session to keep the backlog actionable and aligned with business goals.
*Challenges* #
Teams may treat grooming as a “nice‑to‑have” activity, leading to poorly defined stories that cause rework during sprint planning.
Burn‑down Chart #
Burn‑down Chart
A visual tool that displays the remaining work (usually in story points) against… #
The chart helps the team monitor progress and predict whether the sprint goal will be met.
*Example* #
On day three of a two‑week sprint, the burn‑down shows a steep decline, indicating that the team is ahead of schedule.
*Practical application* #
Update the chart daily during the stand‑up to provide a shared reference point for the team’s pace.
*Challenges* #
Inaccurate estimates or scope changes can distort the chart, leading to false confidence or unnecessary alarm.
Burn‑up Chart #
Burn‑up Chart
Displays the amount of work completed over time, often against the total scope #
Unlike burn‑down, it makes scope changes visible, helping stakeholders understand progress despite added or removed items.
*Example* #
A release‑level burn‑up shows a gradual rise in completed story points while the total scope line shifts upward after a new feature is added.
*Practical application* #
Use the burn‑up in release reviews to discuss the impact of scope changes on delivery dates.
*Challenges* #
Frequent scope volatility can make the chart appear erratic, reducing its credibility with stakeholders.
Definition of Done (DoD) #
Definition of Done (DoD)
*Example* #
The DoD for a web feature includes passing all automated tests, code review approval, and successful deployment to a staging environment.
*Practical application* #
Review the DoD during sprint retrospectives to refine it as the team matures.
*Challenges* #
Overly strict DoD can slow delivery; overly lax DoD can result in low‑quality increments that accumulate technical debt.
Definition of Ready (DoR) #
Definition of Ready (DoR)
A set of criteria that a backlog item must meet before it can be taken into a sp… #
The DoR ensures that the team has enough information, size, and clarity to start work without excessive interruptions.
*Example* #
A story meets DoR when it has clear acceptance criteria, is sized using story points, and has no unresolved dependencies.
*Practical application* #
Use DoR as a gate during sprint planning; items that fail the gate are deferred to the next grooming session.
*Challenges* #
Teams may set the DoR too high, causing delays, or too low, leading to rework and blockers mid‑sprint.
Daily Stand‑up #
Daily Stand‑up
A short, time‑boxed (usually 15 minutes) meeting where each team member answers… #
The purpose is to synchronise effort and surface blockers early.
*Example* #
During the stand‑up, a developer mentions a blocked API dependency, prompting the Scrum Master to raise the issue immediately.
*Practical application* #
Keep the stand‑up focused on progress and impediments; avoid problem‑solving discussions that belong to separate meetings.
*Challenges* #
Teams can drift into status‑reporting for managers rather than collaborative coordination, reducing the meeting’s effectiveness.
Decision‑making Matrix #
Decision‑making Matrix
A visual tool that maps decisions to responsible roles, clarifying who is accoun… #
It helps prevent ambiguity and ensures transparent ownership.
*Example* #
The matrix shows that the product owner is accountable for feature prioritisation, while the architecture lead is consulted on technical feasibility.
*Practical application* #
Introduce the matrix during sprint planning to clarify decision rights for backlog items.
*Challenges* #
Over‑engineering the matrix can create bureaucracy; under‑defining roles can lead to duplicated effort or conflict.
Definition of Value (DoV) #
Definition of Value (DoV)
A concise statement that articulates the expected benefit of a backlog item, oft… #
It aids the product owner in ordering work based on tangible outcomes.
*Example* #
The DoV for a security feature might be “reduce breach risk by 30 % and avoid potential regulatory fines of £200k.”
*Practical application* #
Capture DoV alongside each user story to facilitate data‑driven prioritisation.
*Challenges* #
Estimating value can be speculative; inaccurate values may misguide the team’s focus.
Definition of Vision #
Definition of Vision
A high‑level description of the future state the product aims to achieve, provid… #
It is typically concise, inspirational, and aligned with organisational goals.
*Example* #
“Empower small businesses to manage inventory online with a single, intuitive dashboard.”
*Practical application* #
Revisit the vision at the start of each release planning session to keep the team aligned with long‑term objectives.
*Challenges* #
Vague visions can lead to divergent interpretations; overly detailed visions can stifle creativity.
Definition of Work‑in‑Progress (WIP) Limit #
Definition of Work‑in‑Progress (WIP) Limit
A constraint that caps the number of items allowed in a given workflow stage at… #
WIP limits help reduce multitasking, expose bottlenecks, and improve flow.
*Example* #
The team sets a WIP limit of three items for the “In Development” column on the Kanban board.
*Practical application* #
Adjust limits based on cycle‑time metrics to optimise throughput.
*Challenges* #
Teams may resist limits, fearing reduced flexibility; improperly set limits can cause idle time or backlog pile‑up.
Definition of Sprint Goal #
Definition of Sprint Goal
A concise, measurable objective that the team commits to achieving during a spri… #
The goal provides focus and a shared purpose beyond the sum of individual backlog items.
*Example* #
“Implement the checkout flow and achieve a 95 % automated test coverage for the payment module.”
*Practical application* #
Review the sprint goal daily during stand‑ups to keep the team oriented toward the intended outcome.
*Challenges* #
Vague goals can dilute focus; overly ambitious goals may lead to unfinished work and reduced morale.
Definition of Story Points #
Definition of Story Points
A unitless measure used to express the relative effort required to implement a u… #
Story points capture complexity, risk, and amount of work, enabling teams to forecast capacity.
*Example* #
A simple login page is estimated at 2 points, while a multi‑currency payment integration is 13 points.
*Practical application* #
Use Planning Poker to reach consensus on point values, fostering shared understanding.
*Challenges* #
Teams may compare points across projects, leading to inconsistent sizing; anchoring bias can skew estimates.
Definition of Technical Debt #
Definition of Technical Debt
The implied cost of additional rework caused by choosing an expedient solution n… #
Technical debt accumulates when shortcuts are taken, reducing future productivity.
*Example* #
Skipping unit tests to meet a deadline creates debt that must be paid later through additional testing effort.
*Practical application* #
Allocate a fixed percentage of each sprint to debt reduction, making it visible in the backlog.
*Challenges* #
Stakeholders may view debt work as “non‑functional” and deprioritise it, causing long‑term maintainability issues.
Definition of User Story #
Definition of User Story
A short, simple description of a product feature from the perspective of an end‑… #
” It captures functional requirements in a conversational style.
*Example* #
“As a shopper, I want to filter products by price so that I can find items within my budget quickly.”
*Practical application* #
Write user stories collaboratively during backlog grooming to ensure shared understanding.
*Challenges* #
Over‑granular stories can lead to excessive overhead; overly large stories (epics) need to be broken down for effective sprint planning.
Definition of Velocity #
Definition of Velocity
The average number of story points a team completes per sprint, measured over se… #
Velocity provides a baseline for future sprint capacity and helps set realistic expectations.
*Example* #
Over the last five sprints, a team’s velocity averaged 42 points, guiding the next sprint’s forecast.
*Practical application* #
Use velocity to size the sprint backlog, adjusting for known holidays or team member availability.
*Challenges* #
Velocity should not be treated as a performance metric; fluctuations due to scope changes or team composition can mislead planning if not contextualised.
Definition of Work‑Item Type #
Definition of Work‑Item Type
Categories used to classify backlog items, each with distinct workflows and prio… #
Common types include “Feature,” “Bug,” “Technical Debt,” and “Spike.”
*Example* #
In Jira, a “Bug” automatically triggers a higher‑priority queue than a “Feature.”
*Practical application* #
Define clear criteria for each type to help the product owner triage and the team plan work efficiently.
*Challenges* #
Mis‑labelled items can cause confusion during sprint planning and affect metrics such as lead time.
Definition of Work‑Item Prioritisation #
Definition of Work‑Item Prioritisation
The process of ordering backlog items based on factors such as value, risk, effo… #
Prioritisation ensures the team delivers the most important work first.
*Example* #
Using WSJF, a team calculates the score for each feature and orders them accordingly.
*Practical application* #
Conduct regular prioritisation workshops with stakeholders to keep the backlog aligned with evolving business needs.
*Challenges* #
Conflicting stakeholder interests can lead to deadlock; over‑reliance on a single metric may ignore qualitative factors.
Definition of WIP (Work‑in‑Progress) Limit #
Definition of WIP (Work‑in‑Progress) Limit
A constraint that caps the number of items allowed in a particular workflow stag… #
A constraint that caps the number of items allowed in a particular workflow stage at any given moment, preventing overload and encouraging smooth flow.
*Example* #
The “Testing” column is limited to four items; once full, developers must wait before pushing new code.
*Practical application* #
Monitor the board daily; if a column consistently hits its limit, investigate the bottleneck.
*Challenges* #
Teams may circumvent limits by creating workarounds, undermining the intended benefits of flow control.
Definition of Epic #
Definition of Epic
A large body of work that can be broken down into multiple user stories #
Epics represent significant business objectives that span several sprints or releases.
*Example* #
“Create a mobile app for the e‑commerce platform” is an epic that includes stories for login, browsing, cart, and checkout.
*Practical application* #
Use epics to organise the product backlog and align them with strategic themes on the roadmap.
*Challenges* #
Epics can become vague “catch‑all” items if not regularly refined into actionable stories.
Definition of Feature #
Definition of Feature
A distinct piece of functionality delivering value to the end user, often repres… #
Features are typically tracked in the backlog and may map to release goals.
*Example* #
The “Search” feature includes stories for keyword search, filters, and result ranking.
*Practical application* #
Group related stories under a feature to maintain traceability from requirement to delivery.
*Challenges* #
Over‑granular features can cause unnecessary coordination; under‑granular features may hide complexity, leading to surprise during implementation.
Definition of Facilitation #
Definition of Facilitation
The skill of guiding a group toward a productive outcome while remaining neutral… #
A facilitator creates an environment where collaboration flourishes.
*Example* #
During a retrospective, the facilitator uses a “Start‑Stop‑Continue” exercise to elicit feedback from all team members.
*Practical application* #
Apply facilitation techniques such as timeboxing, parking lot, and round‑robin to keep meetings focused.
*Challenges* #
Facilitators can inadvertently dominate discussions or fail to address conflict, reducing the group’s sense of ownership.
Definition of Icebreaker #
Definition of Icebreaker
A short, engaging activity used at the start of a meeting or workshop to create… #
A short, engaging activity used at the start of a meeting or workshop to create a relaxed atmosphere, encourage participation, and build rapport among participants.
*Example* #
“Two Truths and a Lie” helps new team members learn about each other before a sprint planning session.
*Practical application* #
Choose an icebreaker relevant to the group size and session purpose; keep it under five minutes.
*Challenges* #
Inappropriate or overly elaborate icebreakers can waste time or make participants uncomfortable.
Definition of Impact Mapping #
Definition of Impact Mapping
A visual technique that links product features to business goals, actors, and im… #
The map consists of four layers: Goal, Actors, Impacts, and Deliverables.
*Example* #
The goal “Increase subscription conversions” leads to actor “Visitor,” impact “Clicks the trial button,” and deliverable “Add prominent CTA.”
*Practical application* #
Conduct an impact‑mapping session during release planning to ensure alignment with strategic objectives.
*Challenges* #
Teams may oversimplify the map, ignoring secondary actors or indirect impacts, resulting in sub‑optimal prioritisation.
Definition of Increment #
Definition of Increment
The sum of all completed product backlog items at the end of a sprint, integrate… #
It represents a usable, tested piece of the product.
*Example* #
After sprint 4, the increment includes a functional search feature, tested API endpoints, and updated documentation.
*Practical application* #
Demonstrate the increment in the sprint review to gather stakeholder feedback.
*Challenges* #
If the DoD is not consistently applied, the increment may contain hidden defects, reducing confidence in the product’s stability.
Definition of Iteration #
Definition of Iteration
A fixed‑length period (commonly two to four weeks) during which a cross‑function… #
Iterations promote regular feedback and adaptation.
*Example* #
A two‑week iteration starts on Monday and ends on the following Friday, concluding with a review and retrospective.
*Practical application* #
Use a consistent iteration cadence to establish rhythm and predictability for the team and stakeholders.
*Challenges* #
Changing iteration length mid‑project can disrupt cadence and affect velocity calculations.
Definition of Kaizen #
Definition of Kaizen
A Japanese term meaning “change for the better,” representing a philosophy of on… #
In agile, Kaizen is realised through regular retrospectives and small experiments.
*Example* #
After a retrospective, the team decides to adopt pair programming for complex modules, improving code quality.
*Practical application* #
Encourage the team to propose one small improvement per sprint and track its impact.
*Challenges* #
Without visible results, teams may lose motivation to pursue Kaizen, reverting to old habits.
Definition of Kanban #
Definition of Kanban
A visual workflow management method that uses a board with columns representing… #
Kanban is often used in conjunction with Scrum to enhance delivery.
*Example* #
A Kanban board shows columns “To Do,” “In Progress,” “Code Review,” and “Done,” each with a WIP limit of three.
*Practical application* #
Implement cumulative flow diagrams to monitor lead time and identify process improvements.
*Challenges* #
Teams may misuse the board as a status report for managers, neglecting its purpose as a flow‑optimisation tool.
Definition of Lead Time #
Definition of Lead Time
The elapsed time from the moment a request is made (e #
g., a user story added to the backlog) until the product increment is delivered to the customer. Lead time measures overall responsiveness.
*Example* #
A feature’s lead time is 15 days from backlog entry to production release.
*Practical application* #
Track lead time to identify delays in early stages such as analysis or design.
*Challenges* #
High variability in lead time can obscure root causes, requiring deeper analysis of each workflow stage.
Definition of Lean #
Definition of Lean
A set of principles focused on delivering maximum customer value while minimisin… #
Lean encourages continuous flow, pull‑based scheduling, and respect for people. In software, lean aligns with agile by emphasizing rapid feedback and iterative delivery.
*Example* #
A team adopts lean by eliminating unnecessary documentation that does not add customer value.
*Practical application* #
Conduct value‑stream mapping workshops to identify and remove non‑value‑adding activities.
*Challenges* #
Misinterpreting “waste” can lead to cutting essential activities such as testing, compromising quality.
Definition of Pair Programming #
Definition of Pair Programming
An agile development technique where two developers work together at one worksta… #
Roles switch frequently to share knowledge and improve code quality.
*Example* #
During a complex algorithm implementation, two developers rotate driver/observer every 20 minutes.
*Practical application* #
Use pair programming for onboarding new team members to accelerate knowledge transfer.
*Challenges* #
Some developers may feel uncomfortable sharing a keyboard, and perceived productivity loss can cause resistance.
Definition of Parking Lot #
Definition of Parking Lot
A visual list of topics that arise during a meeting but are not immediately addr… #
The parking lot ensures focus while preserving valuable input.
*Example* #
During sprint planning, a discussion about a future integration is added to the parking lot for later analysis.
*Practical application* #
Review the parking lot at the end of the meeting or schedule a follow‑up session to address deferred items.
*Challenges* #
If the parking lot is neglected, important topics may be forgotten, leading to incomplete decisions.
Definition of Peer Review #
Definition of Peer Review
A systematic examination of work products by colleagues to detect defects, impro… #
Peer reviews can be formal (checklists) or informal (pair programming).
*Example* #
A developer submits a pull request, and three peers review the changes, providing feedback on naming conventions and test coverage.
*Practical application* #
Integrate peer review into the CI pipeline to enforce mandatory approvals before merge.
*Challenges* #
Overly critical reviews can discourage contributors; insufficient time allocated for reviews can reduce effectiveness.
Definition of Product Backlog #
Definition of Product Backlog
An ordered list of all desired work for the product, maintained by the product o… #
Items range from features and enhancements to bugs and technical debt, each with a description, priority, and estimate.
*Example* #
The backlog contains 120 items, with the top 15 ready for the next sprint.
*Practical application* #
Keep the backlog visible to the whole team using a shared tool, updating it continuously based on feedback.
*Challenges* #
Large, unmanaged backlogs become unwieldy, making it difficult to locate high‑priority items.
Definition of Product Owner #
Definition of Product Owner
The role responsible for maximising product value by managing the product backlo… #
The product owner acts as the voice of the customer and ensures the team works on the most valuable features.
*Example* #
The product owner collaborates with marketing to align upcoming releases with campaign timelines.
*Practical application* #
Conduct regular stakeholder interviews to keep the backlog aligned with market needs.
*Challenges* #
Balancing competing stakeholder demands and resisting scope creep while maintaining a clear vision.
Definition of Pull System #
Definition of Pull System
A workflow approach where work is only started when there is capacity downstream… #
Items are “pulled” from the backlog into the next stage as space becomes available.
*Example* #
Developers pull the next story from “Ready” only after completing a current task, respecting the WIP limit.
*Practical application* #
Implement a “ready‑to‑start” column with explicit entry criteria to support the pull mechanism.
*Challenges* #
In environments with strict deadlines, teams may feel pressured to “push” work, undermining the pull principle.
Definition of Retrospective #
Definition of Retrospective
A regular meeting held at the end of a sprint where the team reflects on what we… #
The retrospective aims to generate actionable improvement items for the next sprint.
*Example* #
The team identifies “improve test automation coverage” as a focus for the upcoming iteration.
*Practical application* #
Use varied formats (e.g., “4‑Ls”, “Mad‑Sad‑Glad”) to keep retrospectives engaging.
*Challenges* #
If the same issues recur without resolution, the team may become cynical, reducing the ceremony’s effectiveness.
Definition of Scrum #
Definition of Scrum
A lightweight framework for managing complex product development, consisting of… #
Scrum promotes iterative progress through time‑boxed sprints, daily stand‑ups, and regular inspection and adaptation.
*Example* #
A Scrum team delivers a potentially shippable increment every two weeks, incorporating stakeholder feedback after each sprint review.
*Practical application* #
Adopt the three‑pillar model (Transparency, Inspection, Adaptation) to guide daily practices.
*Challenges* #
Misinterpreting Scrum as a methodology rather than a framework can lead to “Scrum‑but” antipatterns, where essential events are skipped or altered.
Definition of Scrum Master #
Definition of Scrum Master
The servant‑leader responsible for ensuring the Scrum process is understood and… #
The Scrum Master coaches the team, removes impediments, and shields the team from external disruptions.
*Example* #
The Scrum Master negotiates with a downstream team to resolve a blocking API dependency.
*Practical application* #
Conduct regular coaching sessions to strengthen self‑organisation and adherence to the DoD.
*Challenges* #
Balancing the role of coach versus manager can be difficult, especially in organisations with hierarchical cultures.
Definition of Self‑organization #
Definition of Self‑organization
The ability of a team to determine the best way to accomplish its work without e… #
Self‑organising teams decide how to allocate tasks, manage workflow, and improve processes.
*Example* #
The team collectively decides to adopt a new testing framework after evaluating its benefits.
*Practical application* #
Encourage the team to set its own sprint goals and define its own Definition of Done.
*Challenges* #
Lack of clear boundaries can lead to decision‑fatigue; teams may need guidance to avoid paralysis.
Definition of Servant Leadership #
Definition of Servant Leadership
A leadership philosophy where the leader’s primary purpose is to serve the team,… #
Servant leaders listen actively, share power, and support development.
*Example* #
A manager allocates budget for team training after hearing a request during a retrospective.
*Practical application* #
Practice “listening first” in meetings, summarising concerns before offering solutions.
*Challenges* #
In traditional command‑and‑control cultures, servant leadership may be misunderstood as a lack of authority.
Definition of Sprint #
Definition of Sprint
A fixed‑duration development cycle, typically 1‑4 weeks, during which a Scrum te… #
The sprint begins with planning and ends with a review and retrospective.
*Example* #
A two‑week sprint starts on Monday, with a sprint goal to implement the user profile feature.
*Practical application* #
Maintain a consistent sprint length to stabilise velocity and facilitate forecasting.
*Challenges* #
Mid‑sprint scope changes can disrupt flow and reduce the team’s ability to meet the sprint goal.
Definition of Sprint Backlog #
Definition of Sprint Backlog
The set of product backlog items selected for the sprint, plus a plan for delive… #
It is owned by the development team and evolves daily.
*Example* #
The sprint backlog contains five user stories and three technical tasks, each broken into subtasks on the task board.
*Practical application* #
Update the sprint backlog during the daily stand‑up to reflect completed work and emerging impediments.
*Challenges* #
Over‑commitment can lead to unfinished work, while under‑commitment may waste capacity.
Definition of Sprint Goal #
Definition of Sprint Goal
*Example* #
“Enable users to reset their password securely.”
*Practical application* #
Refer to the sprint goal during daily stand‑ups to keep the team aligned on priorities.
*Challenges* #
Vague or overly broad goals can dilute focus, leading to scattered effort across unrelated stories.
Definition of Sprint Planning #
Definition of Sprint Planning
A collaborative meeting at the start of each sprint where the product owner pres… #
The outcome is a sprint backlog and a sprint goal.
*Example* #
The team uses historical velocity and team availability to decide it can commit to eight story points.
*Practical application* #
Use a “capacity calculator