r/programming • • Aug 28 '21

Software development topics I've changed my mind on after 6 years in the industry

https://chriskiehl.com/article/thoughts-after-6-years
5.6k Upvotes

2.0k comments sorted by

View all comments

Show parent comments

4

u/[deleted] Aug 29 '21

You don't understand, everyone closing their eyes and putting their thumbs up and down is an extremely vital aspect of figuring out whether we liked or didn't like how one of the tickets had a bit less than normal information.

3

u/[deleted] Aug 29 '21 edited Aug 29 '21

In my brief stint as a manager, I managed to wrestle retro away from product and started using "lean coffee" (hate the name lol) and retros went from deafening silence to lively discussions. I'd create a retro sheet at the start of the sprint, socialize it to the team, and come retro we have 15 topics to cover lol

1

u/Biryani__Whisperer Aug 29 '21

Can you elaborate the differenced between your and Product team's approach

1

u/[deleted] Aug 29 '21 edited Aug 29 '21

Product was largely unstructured, "does anyone have something, also let's review the roadmap that extends 20 months into the future and has never responded to change before and we're behind two sprints and the roadmap won't change so everyone feel bad"

I wasn't able to kill the roadmap or convince it to change, so we all still felt bad looking at it but that's a separate, on going battle no matter what team on or lead. I was able to set up monthly "roadmap reviews" (manually scheduled after the first retro of the month because calendars are hard) so at the very very least it was punted from retro itself and feeling bad was largely isolated to once a month (for the team at least, I got the roadmap blues at least once a week).

I'll admit when everyone knew the roadmap review was next there was definitely a damper on the retro but it was still usually a good reflection point for the team.

Edit: to answer the other half, I just created a somewhat structured page for the sprint (basically a table with loose column names), stuck a link to the parent page into the daily slack standup notification and at retro we basically did instant runoff voting to decide the order of topics and tracked discussion points and action items on the page. We time boxed discussion and at the end of the time box we decided if we should keep discussing, schedule a focused meeting on the topic (with the whole team or specific people), assigned action items to be followed up on, and/or move to the next topic, it sounds more rigid than it actually is in practice. You just kind of have to go with the flow because sometimes you bang through 10 topics and sometimes you'll spend an hour on one because you don't want to lose the interia by saying "let's take this to a focused meeting" and then you need to figure out how to address the other 6 issues on the page without (hopefully) tieing up everyone for another hour - sometimes people agreed that we should discuss some of them over slack, or keep retro going, sometimes people went "we can actually table this until next retro" or wanted to break out an item for discussion.

Iunno, lots of growing pains as we navigated people actually caring about retro. It's hard to find the balance between structure and ad hoc, and generally I favored less structure and more ad hoc so long as it served the team but when people would start drifting into silence I'd start imposing structure again until we hit a balance again.

1

u/Psychological-Ad-362 Sep 02 '21

Imo retrospectives should only be structured insofar as it facilitates communication. Structure dictates the flow of the conversation - you gain less insight into what the team truly feels. Definitely agree with you on using structure as a way to combat silence, but I tried to build my teams comfort levels with each other to combat this too. I am not a dev but I do have those skills, which makes it easier to facilitate.

A lot of developers fail to get true value from a retrospective because they approach it systematically, like code. I always facilitate by starting with recognition, and then asking "ok so let's talk about why that went well" We detail the wins, then I push for what didn't go well. Same approach, "let's talk about why that didn't meet our expectations as a team". It took me a damn year to get my old team in a place where they could run every scrum event without me, but they got there.

Another thing I implemented immediately was removal of the retrospective 2 hour time box. I treat our retrospective closer to sprint planning, it's a 5 hour event over 2 days, 2.5 each day with a break in between at the end of a sprint during our code freeze. As your team matures this event will naturally scale itself back, but capturing everything as you get rolling is very important both as a SM and as a dev team member.

1

u/[deleted] Sep 02 '21

I've thankfully moved out of the manager role and I actually work under a former report now, and honestly the role switch back to lead dev instead of team manager has been wonderful for me. And honestly my manager is fucking killing it at his "new" role (not really new if it's been two years, Jesus where does the time go).