Which ITIL Guiding Principles Are Applied in Agile Sprints with Stakeholder Demos?
A software development team is working on a new feature using two-week sprints. After each sprint, they demo the feature to stakeholders and incorporate feedback into the next sprint. Which TWO ITIL guiding principles are being applied?
Quick Answer
The answer is Progress iteratively with feedback and Collaborate and promote visibility. These two ITIL guiding principles are applied in agile sprints with stakeholder demos because the two-week sprint cycle embodies iterative progress, where each increment is refined based on direct feedback, while the demo itself ensures stakeholders are actively involved and the team’s work is transparent. On the ITIL 4 Foundation exam, this scenario tests your ability to map real-world agile practices to the guiding principles, often appearing as a scenario-based question where you must distinguish between principles like “Focus on value” (which is about outcomes, not process) and “Keep it simple” (which is about minimizing complexity). A common trap is selecting “Focus on value” because the demo shows value, but the key is that the feedback loop and stakeholder collaboration are the explicit mechanisms at play. To remember this, think of the agile mantra “inspect and adapt” for iterative feedback, and “show and tell” for collaboration and visibility.
⚠ Common exam trap
Candidates often confuse 'Progress iteratively with feedback' (which focuses on incremental delivery with feedback loops) with 'Start where you are' (which requires assessing the current state), especially when the team is building something new rather than improving an existing process.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Progress iteratively with feedback and Collaborate and promote visibility
The scenario explicitly describes two-week sprints where the team demos the feature to stakeholders and incorporates feedback into the next sprint. This directly applies the 'Progress iteratively with feedback' principle by using short, iterative cycles with continuous feedback loops, and the 'Collaborate and promote visibility' principle by involving stakeholders in demos and making progress visible. The other options either miss the iterative feedback loop or introduce principles not demonstrated in the given workflow.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Focus on value and Start where you are
Why it's wrong here
Sprint demos and feedback loops embody Collaborate and Iterate, not Focus on value or Start where you are. Those two principles concern defining value from the consumer's perspective and reusing existing services rather than building anew, so they miss the iterative, feedback-driven mechanism the stem describes.
- ✗
Keep it simple and practical and Optimise and automate
Why it's wrong here
Sprints with demos and feedback demonstrate Progress iteratively with feedback and Collaborate and promote visibility, not simplification or automation. Keep it simple and practical and Optimise and automate apply when eliminating unnecessary steps or automating manual work, which the scenario does not describe.
- ✓
Progress iteratively with feedback and Collaborate and promote visibility
Why this is correct
Two-week sprints with stakeholder demos after each cycle embody "progress iteratively with feedback": work advances in small increments, and feedback shapes the next iteration. "Collaborate and promote visibility" is satisfied because stakeholders engage directly and see progress through regular demonstrations, ensuring shared understanding across the team and its audience.
- ✗
Think and work holistically and Focus on value
Why it's wrong here
The scenario shows iterative delivery with stakeholder feedback, which maps to Collaborate and promote visibility and Progress iteratively with feedback. Thinking holistically concerns integrating parts into a whole, and focus on value concerns understanding what stakeholders truly value, neither of which the sprint demo feedback loop demonstrates.
Go deeper
Related to this question
About these practice questions
This ITIL4F question is part of Courseiva's 805-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on ITIL4F
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A team is designing a new service. They ensure that they have regular feedback sessions with users after each release and plan their work in two-week sprints. Which ITIL 4 guiding principle is being applied?
medium- A.Collaborate and promote visibility
- B.Keep it simple and practical
- ✓ C.Progress iteratively with feedback
- D.Start where you are
Why C: The team is applying the 'Progress iteratively with feedback' guiding principle. By organizing work into two-week sprints and holding regular feedback sessions after each release, they are breaking the service design into manageable iterations and using user feedback to guide subsequent improvements. This aligns with the ITIL 4 principle that emphasizes incremental delivery and continuous learning through feedback loops.
Variation 2. A development team releases a new feature every six months. They want to adopt Agile principles. Which ITIL guiding principle is most relevant to increasing release frequency?
medium- A.Optimize and automate
- ✓ B.Progress iteratively with feedback
- C.Focus on value
- D.Keep it simple and practical
Why B: The principle 'Progress iteratively with feedback' directly supports increasing release frequency by breaking down the six-month release cycle into smaller, incremental deliveries. Each iteration incorporates feedback from stakeholders and users, allowing the team to adapt and release features more frequently, which is a core Agile practice.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This ITIL4F practice question is part of Courseiva's free PeopleCert certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ITIL4F exam.