Related Posts
Looks like the office is in Ascendas, Taramani.
Additional Posts in Product Management
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
Looks like the office is in Ascendas, Taramani.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site

Scan your QR code to download
Fishbowl app on your mobile

The best approach is to have a team page/Confluence page and document what went well and didn't. Then, the product manager reviews and adds any items in the backlog if any of them are related to the product (tech debt, etc). If it is process or people related, everyone discusses together what the "solution" is and add it to Team Norms. Every team should have a team norms document that should be constantly referred to and updated frequently based on team feedback
What sort of tools do you have available? For example, my team uses Azure DevOps. There is a retro tool that allows us to assign tasks for action items and we diligently review them each retro. Keep it simple to start. Start an xls to track it sprint over sprint. Do you have a scrum master?
Our teams typically uses fig jam, and they’re run by project managers or operations. We don’t do any assignment of tasks so they kind of just get lost and I feel like we talk about the same things all the time. In addition, these only happen at the end of projects and not sprint to sprint like I’m used to.
But I like the idea of assigning ownership. But I feel like even when that happens we forget to follow back up because we’re not having retros on a regular cadence.
Concrete action items assigned out during the meeting and a designated person and agreed upon timelines to follow up. Otherwise nothing happens.
havent seen proper retros in like 6-7 years.... most of the companies I have worked at over that time actively ignored problems in the development cycle... a good indicator that layoffs are likely in the future, something I should have paid attention to
Agreed. The golden days of tech are over.
We are very intentional about implementing feedback. We also use the Azure Devops retro board.
We use mural board to keep track of the action items.
There are many tools to manage the product process. Fig Jam is more of a collab/white board tool. Get a tool that assigns tasks and reminders like Jira, Trello, Microsoft Project, etc.
We use the whiteboard function within Confluence, but you could really use any tool. Our development cycle is every two weeks. Before we go into our Sprint retro, we review some of the action items and follow-up. During the retro, we typically assign the action items. I would suggest reviewing it based on what works for your company. I think every month or quarterly would be good, but it depends on what type of retro. Is it for projects, team retro, etc?