![]() Outcomes: What were the results of each action item and initiative? Did they have a positive or negative impact on your business goals?.Completion: Were action items and initiatives completed? If not, what kept the task owner from completing them?.While looking back at these items, here are three things to keep in mind: Often, this will include action items that came out of a previous retrospective, but more importantly the initiatives your team was working on. Look back at what your team accomplished and what they missed the boat on. As long as your icebreaker gets people talking and the gears turning, it’ll help kickstart the retrospective. Find a quick icebreaker - like a collaborative game - and run it at the beginning of your retrospective. Just like a car engine needs to warm up in the winter, your team needs time to get into the right mindset. It’s pretty tough to start a retrospective cold. Now that you know what a retrospective is and why you should run one, here’s a simple framework for doing so. Without retrospectives, your team might start falling into bad habits that make collaboration tougher or cause them to miss opportunities. This cycle continues so that you’re always improving. The goal is to come out of the retrospective session with action items that can be applied to the next project, sprint, or quarter. Together, they reflect on what went well, what went not-so-well, and how they can improve. Marketers can look back on their projects once they’re complete, a board of executives can examine how they impacted their company, and so on.Ī retrospective session can take many forms but generally involves the team gathering around a whiteboard (digital or otherwise) and sharing ideas. But other teams can benefit from these too. In the context of the Agile methodology, software teams typically perform a retrospective after a sprint. What is a retrospective?ĭefined broadly, a retrospective allows your team to look back at what they’ve accomplished - as well as the tasks that slipped through the cracks. Read on to learn more about the retrospective and find out how you can run a great one every time. Retrospectives are the best way for your team to look back at a quarter, a sprint, or any important milestone and figure out what went down. That’s why you need to get in the habit of running a regular retrospective. But without a designated period for careful thought and reflection, your team will be continuously putting out fires instead of getting better at preventing them. When you’re right in the middle of the action, it feels like you barely have time to breathe, let alone figure out what’s going on. ![]() “What the hell just happened?” That question can rear its ugly head at the end of a particularly busy period for your team. Published in Project management on, last updated. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |