If you are following an Agile approach to project management like Scrum, you should have adopted a continuous improvement practice. Retrospectives are the name of the meeting when the Scrum team makes a pause to think on how to improve its current. Fun Retrospectives is a book that should help you to animate these meetings.
If the Agile Manifesto prefers responding to change over following a plan, it is not against planning. In this article, Raju Kidambi explains why it is important to use Scrum during the pre-project planning phase.
“Value” is the beacon, watchword, end game, justification, and mantra for Agile practitioners. You make product decisions in Scrum at every turn throughout discovery and delivery, balancing multiple perspectives.
After having heard a lot of time that Scrum is dead, Andrew Kallman and Ted Kallman explain why this is not the case. They start by writing that there is “nothing magical about Lean, or for that matter, Agile or any project methodology”. Based on job posting statistics, there is still a strong demand and interest for both traditional and Agile leaders.
In a typical Scrum project, the ScrumMaster might have to fill many different roles simultaneously. He can be a technical expert, an evangelist, a mentor and a coach.
One of values of the Manifesto for Agile Software Development is that you should prefer “responding to change over following a plan”. This introduces a lot of uncertainty in Scrum projects. In his book “Executable Specifications with Scrum”, Mario Cardinal explains that to manage this uncertainty, you have to build your project on a stable platform.