Summary of Practice Domain Retrospective #14
Replies: 1 comment 1 reply
-
To fill in some details regarding how we can use these Github discussions as an anchor/artifact of participation; An initial question in a discussion board here is a "call to action" where the reader understands they can take a few minutes to read the question prompt and toss in an answer or reply without any further obligation. CTA: The question of the week is "How has a FISMA, NIST 800 or other security policy impact your project in an unexpected way?" Go to our Github discussion here and post a few sentences about it right now to help us understand the space!" Post this call-to-action vigorously and repeatedly in Slack channels and The Beef posts and wherever. Have a few ringers you've talked to in advance to populate the first few replies so nobody feels like they're first. If related discussions happen on Slack have someone summarize or link to them from a post. Over a few days the discussion post will start to evolve into a shape and gain some value as a document or suggestions for agenda items. Particularly interesting responses can be a 2-3 minute verbal summary by the poster, followed by discussion. As interesting things get posted, highlight them in subsequent slack posts touting the discussion thread URL link. Hold the in person meeting based on how the discussion thread evolved, schedule it around the most active participants of the thread but leave room for others who might want to join. Record the meeting but only for the purpose of summary notes afterwards. Post the summary notes to the chat and encourage any discussions that would have happened in a longer meeting to occur on the discussion thread as a post-meeting and continued async discussion. The thread has its own searchable value in Github now. Use it as an artifact to build other things such as documentation, marketing, or business development artifacts, particularly parts of the discussion that tell a story about how Fearless solves customer problems. Wash, rinse, repeat. |
Beta Was this translation helpful? Give feedback.
-
We've been advancing the practice domain concept since the beginning of February, and we conducted a 6-month retrospective to better understand how we can iterate on our engineering practice as a whole and better support everyone's needs through Practice Domains.
Here is the original miro retro board. We had approximately 14 people attend and engaged in active and productive discourse.
Key Insights:
Actionable Changes:
Future Steps:
TL;DR: We're refining our practice domain meetings to be more structured and engaging, dividing them into project-oriented and domain-oriented categories. We'll leverage our successful tools like the GitHub repo, Project board, and discussions more actively and address concerns around billable hours to ensure these meetings are valuable without feeling burdensome.
This was workshopped with chatgpt
Beta Was this translation helpful? Give feedback.
All reactions