![]() Keeping it out is part of creating a safe environment. I don’t think swearing has any place in a retrospective. But, on the other hand, it was nice he could vent and get that out of his system knowing that it wouldn’t be repeated verbatim to the DevOps group. In a recent retrospective, a programmer vented about how long it was taking the “damn DevOps group” to deploy. That means getting everyone to agree that what happens or is said in a retrospective, stays in the retrospective.Īttend enough retrospectives and you’ll see tempers flare occasionally and you’ll hear things that shouldn’t be repeated. ![]() ![]() People won’t speak up in retrospectives unless they feel safe in doing so. These include doing the following: Create a Safe EnvironmentĬreate a safe environment. There are definitely some steps you can take to increase honesty and trust among your team members. Rather we need to focus on getting people to be more honest and open during them. But the solution is not to abandon retrospectives. If people aren’t going, to be honest in a retrospective, the argument goes, they’re a waste of time. One of the most common complaints about retrospectives is that people fail to bring up real issues or admit to their problems. Problem #1: People Aren’t Honest or Trustworthy In this article, I’ll describe the four most common problems I’ve seen with retrospectives, and I’ll offer advice on overcoming each problem. Teams often struggle to get their retrospectives just right. Unfortunately, not all retrospectives are perfect. This search for continual improvements is the purpose of the iteration retrospective. No matter how good an agile team is today, its team members feel compelled to seek ways to become even better in the future. An essential part of agile is continuous improvement.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |