Add engineering project retro process #403
Conversation
✅ Deploy Preview for meltano-handbook ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
@cjohnhanson This is awesome. Thanks for creating! What do you think of discussing amongst the team this coming Tuesday, with goal of merging next week? |
src/_engineering/index.md
Outdated
| - Every retrospective will have a _leader_ who is responsible for faciliting scheduling, setting up the Miro board for the async portion, encouraging participation, and documenting the follow-up work that needs to be done. | ||
| - Ideally, retros should be conducted within a month of the completion of the relevant project so that the project is fresh in everyone's minds. | ||
|
|
||
| ### Phase 1 (Async) |
There was a problem hiding this comment.
If initial feedback is shared openly and non-anonymously among the team (e.g. posting moods), then a team member (particularly one who has perceived authority or is otherwise being looked up to) could bias what others report merely by sharing their own opinion. To avoid this bias, maybe some amount of this process should be done privately, and then after every interested party has provided their initial feedback it's revealed all at once.
There was a problem hiding this comment.
Maybe Google forms could be useful for this.
There was a problem hiding this comment.
That's a really good idea. Lattice may also have some functionality that could help here. I'll look into it.
There was a problem hiding this comment.
@WillDaSilva -- in the interest of "progress over perfection", I'd like to push this forward even without establishing a solid channel for providing anonymous feedback.
I've added a note that this process is not meant to take the place of other feedback mechanisms and that anonymous or 1:1 feedback is always encouraged in Slack or Lattice.
I'd like to revisit making the initial async feedback round anonymous in the future, but I think it's okay to omit in this first iteration.
There was a problem hiding this comment.
I've used https://www.smileagile.io/ to track mood sprint-over-sprint, but perhaps we can still find it useful for our use case. It's definitely anonymous.
@aaronsteers sure thing, I was also hoping to give this a test run with a project retro for the private beta launch in the next ~2 weeks. |
There was a problem hiding this comment.
Looks good to me, and I'm looking forward to participating in the Private Beta project retro.
I'd appreciate if one other member of @meltano/engineering could review and leave their thoughts before we merge this, since I presume that whatever we merge here will be what is used for the first formal project retro.
cjohnhanson
requested review from
a team and
seth-meltano
and removed request for
seth-meltano
There was a problem hiding this comment.
LGTM 👍 Now that we have subcategories, what do you think about creating a new page under Team Practices for Project Retrospectives? Its quite a large content addition to the main engineering team index.md, which we may want to reserve for overview and navigational/quick-links content (I know it is currently a mix of the two 😅).
No description provided.