Sprint retrospectives are often skipped, compressed, or organized in a way that doesn't provide good feedback. This is unfortunate, as a well-planned retrospective is a great way to improve how you work. Good retrospectives enable engagement and safety, distill and prioritize ideas, and create concrete action items.

More mature organizations are usually very process-disciplined, especially when teams are distributed. However, it’s dangerous to become overly reliant on process. People can become too complacent, accepting a process just to avoid having to make decisions. Here are some ways to keep your processes fresh and valuable.

While lots of organizations are making good progress with DevOps, there are others that have fallen prey to common DevOps antipatterns. Signs usually include a slowdown or stopping of progress toward a fully collaborative organization operating at a high velocity. Here are four DevOps antipatterns to watch out for.