Skip to content

View from the Potting Shed

Gareth J M Saunders

  • Home
  • About
  • Agile thinking
  • Personal productivity
  • Books
  • Contact
  • —
  • 195 metal CDs
  • Digital Shed45
  • Rename Divi Projects
Gareth has a goatee beard, is wearing glasses and a checked shirt. In the background is a PC monitor showing the website of the University of St Andrews

Hi, I’m Gareth J M Saunders — dad of three, priest, Scrum Master, writer and long-time productivity experimenter.

I help people and teams cut through overwhelm to live and work with more clarity and flow.

My approach blends agile principles with real-world compassion to make life and work calmer, more focused, and more human.

  • Agile (128)
  • Baldur's Gate (1)
  • Books (55)
  • Computer (525)
  • Cynefin (18)
  • Family (202)
  • Games (6)
  • General (931)
  • God Project (195)
  • Mahjong (15)
  • Meningitis (6)
  • Microsoft Money (4)
  • Music (295)
  • My albums of… (16)
  • Photon Connection (5)
  • Politics (10)
  • Productivity (72)
  • Psion (32)
  • Web (302)
October 2026
S M T W T F S
 123
45678910
11121314151617
18192021222324
25262728293031
« Sep    

Follow me

  • Bluesky
  • Facebook
  • GitHub
  • Goodreads
  • Instagram
  • LinkedIn
  • Scribd
  • Slideshare
  • SoundCloud
  • Threads

Privacy policy

Tag: empiricism

Scrum creates opportunities for feedback, but XP makes feedback technically possible

Scrum creates opportunities for feedback, but XP makes feedback technically possible

I was speaking with a friend recently who told me that his Scrum team had not held a Sprint Retrospective for several months.

I found myself wondering: at what point does a team stop practising Scrum and merely retain some of its vocabulary?

The Sprint Retrospective is one of Scrum’s formal opportunities for feedback. Remove it and the team loses a regular opportunity to inspect and adapt how it works.

Scrum is built around such feedback loops.

The Scrum Team frequently inspects its progress, its ways of working and the Increment it is creating. At the Sprint Review, stakeholders can examine what has been produced and influence what happens next.

Yet simply holding every Scrum event is not enough. Creating an opportunity for feedback is not the same as being able to respond to it.

Continue reading Scrum creates opportunities for feedback, but XP makes feedback technically possible
Posted on Monday 31 August 2026Monday 21 September 2026Categories AgileTags Agile engineering, automated testing, continuous integration, empiricism, Extreme Programming, feedback loops, pair programming, refactoring, Scrum, Scrum feedback, scrum teams, software quality, technical agility, XPLeave a comment on Scrum creates opportunities for feedback, but XP makes feedback technically possible
Privacy policy Proudly powered by WordPress

I use analytics cookies (Microsoft Clarity) to understand how the site is used and improve content.

Learn more