You're welcome Venkatraman! You can do that in any document (Google Doc, Microsoft Word etc). And if your entire team is in-office, you can leave the retrospective outcomes written on large stick notes on the wall where the team sits so that every time they walk by, they are reminded of the actions from the last retrospective. I hope that helps.
hi Ling, this content is so helpful. Please help me. how do you summarize all the retrospective meetings? and what if the result of the voting is actually not a good idea? And what is suggestion for a website or an apps to use while online meeting to facilitate them in terms on voting so we could avoid anchoring idea? thank you very. hopefully you answer this :)
Hi Atreiyu 👋 thank you for your questions! (1) I summarize my retros in Google docs. I don't copy over each idea but rather, summarize the top 3-5 most voted ideas under a category. Most importantly, the actions and owners of those actions are documented. (2) As for the result of the retro isn't a good idea - how would you know? If you have concerns about it during the retro, then you sound use probing questions so that the team can understand that though valid, the idea may not work. If an idea isn't great because the team tried it after the retro then a quick meeting together to figure out next steps/alternatives can work. (3) retrium is a great paid tool. I personally uses Google Jamboard and get each team member to use the brush tool to draw a circle or checkmark to vote. You can't really tell who is voting for what in jamboard doing it this way. I hope this helps! Thanks for checking out my video Atreiyu!
You used the word anchoring twice here, how would you define that word ? So I can understand how it fits in your explanation. This is probably my 20-30th time watching this video. It’s better than most out there. Lol
Hey! Thank you for watching 20 to 30 times! LOL. If I'm missing something and could answer your questions in a separate video, let me know. :) Anchoring in this context means sharing an idea before others had the chance to think through it inadventently influence their ideas. For example, say a team is estimating a task. Before everyone had decided the number of days it will take, someone prematurely called out "3 days". If that team has low psychological safety, it's likely the rest of the team will think it's 3 days as well because they may start to second-guess themselves. Not anchoring is a way to ensure the team does their thinking at the same time so that it will generate acccurate feedback on how a project went. I hope that makes sense! -Ling
It's up to the group. If it is a big group, names is helpful to recall who wrote what. If it's a group about 10, I don't usually ask them to write down their names as the participants remember what they wrote.
1 is this only used by scrum teams ? 2 and the facilitator in this case would be the scrum master holding this meeting ? 3 does the PO attend this? What do they do during this?
Hi there! 1 - can be used by scrum teams or non-scrum teams. 2 - Facilitator can be the scrum master, manager, lead or any team member. Unless there's low psy safety with this team then it's preferred to have a team member, scrum master or someone with no perceived direct authority to the team. 3 - I've seen PO attend this. If the retro topic is about project delivery then I usually encourage the PO to attend. They can be as an observer or participant. If the retro topic is technical, for example, how to handle tech debts then PO likely won't need to attend. I hope this helps!
@@coachlingabson 1. How will the PO know if it will be a technical meeting or not to then determine whether he should attend 2. Does this also apply to the scrum master? Seeing as the SM Doesnt need to have a technical background
That was helpful Ling. A question : You said in next iteration, we can followup on ADD section items. Then what about the action items (the last column). Are they mean the same?
Hi Arun, usually at the next retro, I would check in with the team on the status of their action items. If anything isn't complete, I would quickly ask the assignee when they think it would be completed to note down for the team/myself to follow up at the next retro. The Add column isn't the same. Add column is where the team has placed ideas they would like to add and those items may not necessarily have made it to the Action column (due to voting). If there were many items in the Add column in the previous retro, I sometimes will get the team to dot vot remaining Add column items, discuss and figure out what we need to action on. I hope that makes sense!
Is there anyway you can redo this video with actual examples of what the team has voted to keep, drop or add. It almost sounds like you can provide fresh content after every retrospective meeting that you hold so we would be able to see real world examples which would be very beneficial to my learning. I’ll take real world examples over theory any time. :)
That's a lovely idea however, I'm not running retrospectives anymore as I focus more on leadership coaching. As well, even if I did, the content of the retrospectives is private to the group so I won't be able to share it without their permission. I find the best learning is to run a session with a team. Imperfection is perfection. Good luck!
Very on-point with no tangents. Great job.
Thank you Mardouk!
Thanks for this! Super helpful ( I loved the post-it detail, by the way!)
Thanks Mar! I'm glad it was super helpful for you!. :)
Very informative....thanks so much !!
Thank you!! You help me a lot.
Best Retrospective video . Thank you
Awww.... thanks so much!! 😀
Great video, thank you
Great session indeed
Hello, Thank you a lot your Explanations are really helpful . Good Job!!!
You're welcome! I'm glad it's helpful!
Thank you!
This is great.
Hi ..Thank you for a nice session.. one question.. where to record or document the retrospective outcomes?
You're welcome Venkatraman! You can do that in any document (Google Doc, Microsoft Word etc). And if your entire team is in-office, you can leave the retrospective outcomes written on large stick notes on the wall where the team sits so that every time they walk by, they are reminded of the actions from the last retrospective. I hope that helps.
hi Ling, this content is so helpful. Please help me. how do you summarize all the retrospective meetings? and what if the result of the voting is actually not a good idea? And what is suggestion for a website or an apps to use while online meeting to facilitate them in terms on voting so we could avoid anchoring idea? thank you very. hopefully you answer this :)
Hi Atreiyu 👋 thank you for your questions!
(1) I summarize my retros in Google docs. I don't copy over each idea but rather, summarize the top 3-5 most voted ideas under a category. Most importantly, the actions and owners of those actions are documented.
(2) As for the result of the retro isn't a good idea - how would you know? If you have concerns about it during the retro, then you sound use probing questions so that the team can understand that though valid, the idea may not work.
If an idea isn't great because the team tried it after the retro then a quick meeting together to figure out next steps/alternatives can work.
(3) retrium is a great paid tool. I personally uses Google Jamboard and get each team member to use the brush tool to draw a circle or checkmark to vote. You can't really tell who is voting for what in jamboard doing it this way.
I hope this helps! Thanks for checking out my video Atreiyu!
Ling Abson thank you very much for the inspiring answer 👏🏻
You used the word anchoring twice here, how would you define that word ? So I can understand how it fits in your explanation. This is probably my 20-30th time watching this video. It’s better than most out there. Lol
Hey! Thank you for watching 20 to 30 times! LOL. If I'm missing something and could answer your questions in a separate video, let me know. :)
Anchoring in this context means sharing an idea before others had the chance to think through it inadventently influence their ideas.
For example, say a team is estimating a task. Before everyone had decided the number of days it will take, someone prematurely called out "3 days". If that team has low psychological safety, it's likely the rest of the team will think it's 3 days as well because they may start to second-guess themselves.
Not anchoring is a way to ensure the team does their thinking at the same time so that it will generate acccurate feedback on how a project went.
I hope that makes sense! -Ling
And nobodies names would be on these sticky notes correct ?
It's up to the group. If it is a big group, names is helpful to recall who wrote what. If it's a group about 10, I don't usually ask them to write down their names as the participants remember what they wrote.
Please do estimation video
Hi Ghrat, what's most challenging when doing estimation? Curious.
1 is this only used by scrum teams ?
2 and the facilitator in this case would be the scrum master holding this meeting ?
3 does the PO attend this? What do they do during this?
Hi there!
1 - can be used by scrum teams or non-scrum teams.
2 - Facilitator can be the scrum master, manager, lead or any team member. Unless there's low psy safety with this team then it's preferred to have a team member, scrum master or someone with no perceived direct authority to the team.
3 - I've seen PO attend this. If the retro topic is about project delivery then I usually encourage the PO to attend. They can be as an observer or participant. If the retro topic is technical, for example, how to handle tech debts then PO likely won't need to attend.
I hope this helps!
@@coachlingabson 1. How will the PO know if it will be a technical meeting or not to then determine whether he should attend
2. Does this also apply to the scrum master? Seeing as the SM Doesnt need to have a technical background
That was helpful Ling.
A question :
You said in next iteration, we can followup on ADD section items.
Then what about the action items (the last column).
Are they mean the same?
Hi Arun, usually at the next retro, I would check in with the team on the status of their action items. If anything isn't complete, I would quickly ask the assignee when they think it would be completed to note down for the team/myself to follow up at the next retro. The Add column isn't the same. Add column is where the team has placed ideas they would like to add and those items may not necessarily have made it to the Action column (due to voting). If there were many items in the Add column in the previous retro, I sometimes will get the team to dot vot remaining Add column items, discuss and figure out what we need to action on. I hope that makes sense!
Thanks Ling, for your time. And that answered me well.
Is there anyway you can redo this video with actual examples of what the team has voted to keep, drop or add. It almost sounds like you can provide fresh content after every retrospective meeting that you hold so we would be able to see real world examples which would be very beneficial to my learning. I’ll take real world examples over theory any time. :)
That's a lovely idea however, I'm not running retrospectives anymore as I focus more on leadership coaching. As well, even if I did, the content of the retrospectives is private to the group so I won't be able to share it without their permission. I find the best learning is to run a session with a team. Imperfection is perfection. Good luck!