![]() ![]() ![]() “The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.” - Sutherland and Schwaber July 2011 The second Scrum Guide - from July 2011 - starts with the retro section with: Second edition of Scrum Guide - July 2011 It then proceeds with explaining HOW a Sprint Retrospective should be conducted (what went well, what could make things better) and proceeds to explain what could be a topic for the retro (team composition, meeting arrangements, tools, Definition of “Done”, methods of communication, processes used).Īt the end the team should have defined actionable items for improvement to be implemented in the next Sprint. “The purpose of the Retrospective is to inspect how the last Sprint went in regards to people, relationships, process and tools. The first Scrum Guide then explains WHY the Sprint Retrospective exists: This little nuance shows how the role of the Scrum Master has changed towards a coaching/supporting role. The section about the Sprint Retrospective starts exactly the same as described in Schwaber’s 2003 paper, except for the fact that it isn’t the Scrum Master holding the Sprint Retrospective, but the Scrum Team. Since that moment the latest version of the Scrum Guide is Scrum’s single source of truth. Ken Schwaber and Jeff Sutherland published the first version of the Scrum Guide in 2010. In fact: this whole sentence still is there. The world enjoyable still is there in the 2017 Scrum Guide. The paper emphasises both effectiveness and enjoyable. “…to revise, within the Scrum process framework and practices, its development process to make it more effective and enjoyable for the next Sprint.” - Ken Schwaber 2003 The Scrum Master (called ScrumMaster) encourages the team: “After the Sprint Review and prior to the next Sprint Planning meeting, the ScrumMaster holds a Sprint Retrospective meeting with the Team.” - Ken Schwaber 2003 The paper “ What is Scrum?” (2003) mentions the retrospective in Scrum context for the first time: Hence it got introduced soon after Agile came to existence. This must have triggered the creators of Scrum to add this reflection moment to the Scrum framework. “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly” - Manifesto for Agile Software Development It also became one of the principles of the Manifesto for Agile Software Development in 2001: Birth of Retrospective in the Agile worldĪccording to the Agile Alliance - Agile Glossary it is Alistair Cockburn who first described the act of reflection after working on increments:ġ997: in “Surviving Object-Oriented Projects“, Alistair Cockburn describes several projects (dating as far back as 1993) informally using the practice, but does not give it a label he summarizes it as “Work in increments, focus after each” - Agile Alliance - Agile Glossary ![]() The retrospective however does not exist yet. The book “Agile Software Development with Scrum” introduces many things, among others the Scrum Master and the Scrum Values. This paper doesn’t discuss any kind of retrospective. This paper is fully focused on how Scrum is about delivering products in complex environments. With the OOPSLA paper in 1995, Sutherland and Schwaber introduced their own adaptation of Scrum. The more I learn about the nuances of this 1986 paper, the more impressed I am with how much of what would become Scrum was already in place. Here Takeuchi and Nonaka bring forward that a team should aim to improve itself, which is very much in line with what Scrum says nowadays. “Starting with the guidelines set forth by top-management, they begin to establish their own goals and keep on elevating them throughout the development process.” - Hirotaka Takeuchi and Ikujiro Nonaka 1986 However, it discusses “self-transcendence”: The paper that started the ball rolling - ‘ The New New Product Development Game’ - doesn’t discuss an event where teams inspect themselves to improve the way of working. The evolution of this event that is typical for many Agile approaches shows the cross-pollination between the approaches very well. With this article, it is my goal to give you an overview of the evolution of the Sprint Retrospective throughout the years. Through this I wish to achieve transparency on why certain ideas about Scrum materialised and help raise understanding on the current definition of Scrum. With this series I aim to show you how radically Scrum has changed over the years. By contrast, some other parts of Scrum have continued evolving. Since 1995, many elements of Scrum have not changed. They based it on “ The New New Product Development Game“ (1986) by Hirotaka Takeuchi and Ikujiro Nonaka. Jeff Sutherland and Ken Schwaber presented it to the world at OOPSLA in 1995. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |