![]() This book has been propelling the practice of retrospectives far beyond the boundaries of software engineering.Ī simple definition of the Agile retrospective In 2006, Esther Derby and Diana Larsen joined in and published the excellent Agile Retrospectives: Making Good Teams Great. The retrospective is spreading and helps thousands of teams engage in a game of self-inspection and self-adaptation. ![]() Simultaneously, the adoption of Agile methods such as eXtreme Programming or Scrum is gaining in intensity. Still in 2001, Norman made a significant contribution to the popularization of retrospectives with the publication of Project Retrospectives: A Handbook for Team Reviews. Kerth, a former professor at the University of Portland and one of the pioneers of agility. Manifesto for Agile Software Developmentįrom there, the Agile movement is put into motion for good. ' At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.' In 2001, Cockburn further developed his concept and even gave the first name to this famous-to-come team meeting, 'reflection workshop.' In the process, he contributes to the Agile Manifesto's birth (of which he is a co-signatory). In his book, Surviving Object-Oriented Projects, Cockburn informally described how working incrementally and regrouping after each increment could help project development. Let's all meet halfway and treat ourselves to Daft Punk's title Around the world.Īlistair Cockburn, meanwhile, was probably quite busy that year. Radio stations repeatedly air Wannabe by the Spice Girls, while #TeamNotoriousBIG only swears by this hit called Hypnotize. Origins and popularization of the Agile retrospective What is an action plan, and how do you build it? How often should we have retrospectives? What’s the ideal length? What are we talking about in a retrospective? How is a retrospective different from a regular team meeting? What kind of team should do retrospectives? Then we will see how you could implement them into your team's routine. In this article, we will try to understand why retrospectives have become so popular. If you're asking yourself these questions… you've come to the right place. We sometimes hear about ' Sprint Retrospective', ' iteration retrospective', ' team retrospective' or even ' Agile retrospective'.Īll right, but what is it really about? What's the point of having retrospectives? What format should I use? How often should I do "retros" with my team? Does it work as well in a remote work context? ![]() The retrospective can have many different names.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |