I know this sounds a bit Pollyanna, and certainly setting a positive tone is one big reason for this guideline. More importantly, though, you must start with successes to ensure they get discussed. This leads us to take our successes for granted, assuming that things went well because we did a great job. Businesses do the same thing. Instead, we should be looking for ways to learn from our lucky breaks and design ways to be successful that we can manage directly.
To make sure that happens, and to avoid the special unicorn trap, you must dedicate time to inspecting your successes first. In the software community, we see a lot of emphasis on ensuring the retrospective is about sharing insights and learning, and not about placing blame, venting, or working out your interpersonal issues. If your group might be prone to playing the blame game, study up on blameless retrospectives.
Also, consider sharing the Retrospective Prime Directive at the beginning of the meeting. Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.
At the end of a project everyone knows so much more. Naturally we will discover decisions and actions we wish we could do over. This is wisdom to be celebrated, not judgement used to embarrass.
At the end of the meeting, you need to walk out with some concrete actions to take. For a meaningful result, make sure the action plans coming out of your meeting are realistic, and that the people responsible for the changes can actually implement them.
The change can be big if the person responsible has the time and authority to put it in action. But if not, get creative and go for the quick win that the team can control. Another tip on this one: if you and your team only have enough influence to make tiny changes, retrospect more often.
Those tiny changes will compound over time. Bonus : if you can get a neutral facilitator and a dedicated note taker, awesome. That lets you focus on contributing your insights as an equal, and frees you from having to serve the group. First, welcome people. For shorter projects or for mid-project retrospectives, you can ask the group to discuss the facts. What did you set out to achieve? What was your plan to achieve this? How did this change as you progressed?
For example, see the Peaks and Valleys exercise. This is one way to create a shared timeline. It takes longer, but it makes for a better conversation and a stronger shared experience.
This is the bulk of the meeting, where you talk about what you learned that you will hand off to other teams or use to change what you do going forward. There are lots of ways to ask for this feedback. Before you decide how to collect answers, though, you need to figure out exactly which questions to ask. What worked really well during this project? What should we make sure we do again in the future? Here are some other questions you might ask, depending on what your team needs to pull out of the conversation.
Turn each prioritized idea into an action plan. Get specific. Document who will do what by when, and when the team can check back to see results. Then start closing the meeting. As a final step before you leave, or in a follow-up email, get feedback on your meeting. Google Scholar. Salo, J. Ronkainen and J. Warsta Agile software development methods: Review and Analysis. Agresti, W. New paradigms for software development. Alatalo, T.
Oinas-Kukkonen, V. Kurkela and M. Siponen Ambler, S. Agile modeling. Anderson, A. Beattie, K. Beck, D. Bryant, M. DeArment, M. Fowler, M. Fronczak, R. Garzaniti, D.
Gore, B. Hacker, C. Handrickson, R. Jeffries, D. Joppie, D. Kim, P. Kowalsky, D. Mueller, T. Murasky, R. Nutter, A.
Pantea and D. Thomas Distributed Computing October : Aoyama, M. IEEE Software CrossRef Google Scholar. Agile Software Process Model. IEEE Software 15 6 : Aydin, M. Harmsen Making a method work for a project situation in the context of CMM. Basili, V. Lanubile Baskerville, R. Levine, J. Pries-Heje, B. Ramesh and S. Slaughter IEEE Computer 34 5 : Balancing quality and agility in Internet speed software development.
Pries-Heje Racing the E-bomb: How the Internet is redefining information systems development methodology. Realigning research and practice in IS development.
Fitzgerald, N. Russo and J. New York, Kluwer: Short cycle time systems development. Info Systems J. Travis and D. Truex Systems without method: The impact of new technologies on information systems development projects. Transactions on the impact of computer supported technologies in information systems development. Kendall, K. Lyytinen and J. Amsterdam, Elsevier Science Publications: Bayer, S.
Highsmith American Programmer 7 6 : Beck, K. IEEE Computer: Extreme programming explained: Embrace change. Reading, MA. Fowler Planning extreme programming. New York, Addison-Wesley. Extreme programming explained: embrace change 2nd. Boehm, B. IEEE Computer Computer 35 1 : Capiluppi, A.
Fernandez-Ramil, J. Higman, H. Sharp, and N. Smith The last step of the 4 Ls retrospective involves discussing what was longed for. The 4Ls retrospective is a phenomenal tool that you can use when you need to gather data on both positives and negative elements at the end of a project.
And even when working with non-distributed teams, it can be difficult to get everyone together at the same time and even share the important information that was discovered during the activity.
Luckily, online project management software like Instagntt solves all of these problems and provides a platform that everyone can use. Instagantt is an online Gantt chart software for project management that helps teams all around the world plan, coordinate, schedule, and execute their projects, from beginning to end.
And this includes performing and documenting 4Ls retrospectives. Teams can rely on Instagantt to create professional-looking Gantt charts in a matter of minutes and to manage their work efficiently by being able to visualize relevant project-related information such as deadlines, resources, and budget, and to keep tasks, conversations, and documents in a single, centralized location.
What Is the 4Ls Retrospective? Benefits of the 4Ls Retrospective Unlike other agile techniques, the 4Ls require no special training or equipment to perform. The 4Ls retrospective focuses on four areas: Liked — What did the team like about this project? With space to list what the team liked, learned, lacked, and longed for the four Ls , this template is a simplified version of a traditional Agile retrospective.
Divide the team into smaller groups to brainstorm ideas for each category, and then bring the team back together to share their thoughts, discuss different perspectives regarding the four Ls, and make a plan for moving forward. This is another visual template to guide your retrospective. Fill out each category as a team to get an idea of what went well and what you could improve during the next sprint or project.
This is another variation on a traditional Agile or Scrum retrospective. The chart provides space to list what the team liked, missed, and learned; what to change for the next sprint or project; and any team appreciations of note.
A project charter is a document that outlines the scope, deliverables, and goals of a project. You can use a project charter as a roadmap of your efforts. It can also double as a business case, should you need to present to stakeholders.
This project charter template provides space to detail all critical project information, including a description; background; the goals and deliverables, roles and responsibilities, budget, and risks; and more. Excel Word Smartsheet. A SWOT analysis is a planning tool that allows you to assess the strengths, weaknesses, opportunities, and threats in any given project.
This basic SWOT analysis template provides you with a two-by-two matrix in order to fill out each category, so you can plan ahead for any potential risks and ensure timely project execution.
Performing a thorough risk assessment at the outset of any project or sprint can help you plan for and mitigate potential threats. Use this risk assessment matrix template to measure the likelihood and severity of each risk you identify.
The template is color-coded to give you an at-a-glance view of project health and viability. In any Scrum project, there are three main roles: product owner, Scrum master, and Scrum team.
0コメント