TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Growing Our Team with Retrospectives

86 pointsby bjacokesabout 6 years ago

5 comments

himynameisdomabout 6 years ago
The effectiveness of a retro rests upon the empowerment of the entire team. If the team isn&#x27;t empowered to own their own success&#x2F;failure, then there is no point in doing a retro.<p>From my experience, business units need just as much coaching on agility as development teams. It&#x27;s hard to change culture, but it&#x27;s essential the BU gets out of the way (let the team own how they plan on delivering a solution) and facilitates empowerment of change for the team to thrive.<p>Again, from experience, the main driver of apprehension is middle management feeling the squeeze from making everything transparent. They&#x27;re use to being the routers (worst case, bottlenecks) of information and work, when in reality their role should be to empower the team with the resources they need to own their work. The shift in focus from delegation to facilitation is essential to the whole process, making retros more effective once realized. Empowerment builds in psychological safety for the team to sink their teeth into their own issues and solve those issues themselves.<p>Another main driver of apprehension is power within the team. If there are only 1 or 2 main members of the team that dictate the pace of the conversation, that crowds out the rest of the team from buying in and&#x2F;or providing their insights. The entire team needs to be empowered to own their success, not just a handful of members.
评论 #19733938 未加载
maxxxxxabout 6 years ago
Retrospectives are great if they actually lead to change. Unfortunately that’s often not the case. The same issues keep coming up repeatedly and soon the retrospective is just another chore.<p>I would love to see retrospectives where managers one or two levels up attend (usually it’s just the devs), listen to issues and address things that need support from a larger point of view. Agile theoretically should transform whole organizations that way.
评论 #19729081 未加载
评论 #19728996 未加载
评论 #19729448 未加载
评论 #19729132 未加载
评论 #19729589 未加载
Yhippaabout 6 years ago
The present team I&#x27;m on is really good at being open and honest during our retros but we can never seem to do anything with the action items for improvement that comes out of them. We&#x27;ve tried everything from mentioning it explicitly in our daily stand-up or making it a zero-point story in our current sprint but nothing seems to work.
评论 #19731543 未加载
评论 #19733956 未加载
评论 #19752401 未加载
yetudadaabout 6 years ago
Retros are great when there&#x27;s follow up! We always make sure to document things that come from the session.
anacletoabout 6 years ago
Do you know those screenshots from what product are from? Look a bit like.. Confluence pages?
评论 #19731539 未加载
评论 #19730984 未加载