Thread by @DevonBurriss

Scrum clergy member (SCM): "Sinner, why are you not hold a scheduled retrospective after every sprint?"
Agile Atheist (AA): "Who says we do sprints"
SCM: "So when do you release working software?"
AA: "As often as possible"
Thread 1/n

SCM: "But then when do you refine your stories?"
AA: "Whenever we get new information"
2/n

SCM: "And what about your retrospective?"
AA: "Which 1?"
SCM: "The one you should have every sprint if you actually did them!"
AA: "We schedule 1when we feel the need which isn't very often since we retro every standup, every story refinement, every architectural discussion"
3/n

If your process is only agile if you can get feedback quickly, improve steadily, and respond to change quickly. If not it is just another process getting in the way. Scrum is just a starting point but too often it becomes a crutch that turns into a couch
4/n

A place to sit and be comfortable while rubber stamping what you do as #Agile
There is a reason the retrospective is important in agile practices. It allows reflection and improvement actions. Why relegate it to a stale 1hr meeting once a sprint?
5/n

A big thank to @huizendveld for this insight a while back. The retrospective is the machine of change in a truly #Agile team. It is a mindset change that when brought to a team can do amazing things.
This wasn't a rant against SCRUM. It was a reminder of what is important.
6/6