Continuous improvement is one of the main values of Agile and retrospectives should play an essential role in supporting this process. In his short and free book “Agile Retrospective Kickstarter”, Alexey Krivitisky provides some exercises that should help Scrum teams to get the most out of their retrospective meetings.
The basic rules of Agile project management frameworks like Scrum are deceptively simple. Drawing from his experience as an Agile coach, Jeff Campbell offers in his book “Actionable Agile Tools” some lightweight practices and tools that could help you to implement successfully an Agile approach.
The retrospective is one of 12 principles outlined in the Agile Manifesto. If this is easy to do this for collocated Scrum teams, how can you achieve good results if you have remote members. In this blog post, Robert Matheson provides a valuable collaborative retrospective technique that can be used for distributed Scrum teams.
People often say that retrospectives are useless, boring and take too long. This means that they are not done right! The difference between a good and a bad retrospective is the structure and the facilitation.
Sprint retrospectives are the most discussed form of retrospectives in Scrum. You can however the same self-analysis and continuous improvement technique to other items of Agile project management. In this article, Madhavi Ledalla discusses release retrospectives.
The first value of the Agile Manifesto is to prefer “Individuals and interactions over processes and tools”. But how can you know if your individuals and your teams like your current Agile approach. In his article, Henrik Kniberg present a simple tool to assess the health of your Scrum teams.
This article examines the Agile myth that constant process improvement is imperative. It discusses the fact that if you need to continuously observe your process, you should wait for the pauses between iteration to perform process improvement.