Use: If you have a specific topic you wish to address this is a good technique.

We want to be the best ruby on rails development team possible for our customers. Retrospective day to finish off our 2 week sprint. About the Tool. A factor can be people, resources, attitudes, traditions, regulations, values, needs, desires, etc.

PLA Force Structure: A 20-Year Retrospective By Dennis J. Blasko The force structure of any military consists of numbers of personnel and equipment, types of equipment, command and control mechanisms which define organizational structure, and the composition of units. Force Field Analysis is a great way of identifying the factors that 1) support the topic (or drive the change forward), and 2) oppose the topic (or prohibit the change from happening). Lewin originally used it in his work as a social psychologist. Jump to: navigation, search.

Give them 5-7 minutes to list all contributing factors, drivers and actions that make up the topic. Include the following details: Sails or engines – these represent the things that are pushing the team forward towards their goals; Anchors – these represent the things that are impeding the team from reaching their goals ; Explain the metaphors to the team and encourage them to place stickies with their ideas for each of … Today we wanted to focus on quality - as a team we are feeling the pain with our methods of writing tests and ensuring quality. ‍ Derby, E., & Larsen, D. (2012).

Force Field Analysis. Break the room into groups of 3-4 people each. Sailboat Retrospective. Vary your methods. The 4Ls retrospective will serve as feedback for the process.

Each week we order lunch in and hold a company wide agile retrospective. Organize anything, together.

The format of the retrospective today was: What if we. From Agile Retrospective Resource Wiki. Draw a boat on a white board. 1) Force Field Analysis: This technique was originally used in a change management context (and also in risk management), but it can be adapted for retrospectives. Then, identifies the following: Driving forces (“forces of change”), which affects the desired state positively. It frames problems in terms of factors or pressures that support the status quo (restraining forces) and those pressures that support change in the desired direction (driving forces). It feels like its more effort than writing the feature which really means that quality isn’t baked in enough yet. Plus/Delta: this technique will address what went well and what should we change? SailBoat. In one glance, know what's being worked on, who's working on what, and where something is in a process. Force Field Analysis; 1 Word Retrospective; Retrospective Dialogue Sheets; Retrospective of Retrospectives; Walk the Board; Retrospectives with Lego; Perfection Game; Anonymous Retrospectives; Big Retrospectives; Multiple Customers; Fishbowl Conversation; Agile Self-assessment Game; Retrospective Exercises Repository; 12 retrospective exercises Force-field analysis: Looking at the forces that drive or block movement toward a goal, then deciding which forces to strengthen or weaken forces to make the goal more attainable; 5 whys: When you’re faced with a problem, repeatedly asking why it happened until you get to the true source Agile Retrospective Using Force Field Analysis.

Agile, Integrum; 1 Comment; At Integrum we always are striving to improve our team. Force field retrospective.

Cluster or discard duplicates. Force Field Analysis is one such technique and, in this article and in the video, below, we'll explore what it is and how you can use it.

Click here to view a transcript of this video.

Go around the room. Here, the team defines a desired state they want to achieve. Start, stop, and continue technique.

The team can then move on to identify what actions it can take to reinforce the driving factors and to lessen the impact of the prohibiting factors. During this time we reflect on how we can improve.

If you’re not analyzing how to improve, (5 Whys, force-field analysis, impact mapping, or fish-boning), you might be jumping to solutions too quickly.

Force Field Analysis was created by Kurt Lewin in the 1940s. Force Field Analysis is a general tool for systematically analyzing the factors found in complex problems. Also good for whole department/company retrospectives Length of time: Approximately 60 minutes but variable Short Description: A plan designed around the force field analysis technique Materials: Whiteboard, pens, …

Each group reads 1 of their sticky notes and puts it up inside the force field until no group has any items left. Trello is a collaboration tool that organizes your projects into boards.

If the retrospective doesn’t make you feel excited about an experiment, maybe you shouldn’t try it in the next iteration.