Summary
With the transition of the Helper Program into phase 3 and the onboarding of teams for each of our primary roles, Community Helpers, Newcomer Helpers, and Event Helpers, we have decided to update our mid-term strategic approaches. This will be conducted through a collaborative effort with each respective team, and will progress through several steps:
- Goal Mapping
- Future State (Gap) Analysis
- Bullseye User Canvas
- User Profile Canvas
- User Attribute Grid
- Touchpoint Mapping
- Journey Mapping
- 4-Corners Canvas
- Metrics Audit
Contents
Goal Mapping
Deadline:TBD
Participating Team Members:
Summary
Goal mapping is a three phase process. First each team member generates a list of 3 to 5 goals that represent successful outcomes for the Community Helper team. These goals can range from project level, server level, team level, or personal level goals. Techniques like 5-whys and Ishikawa diagrams to analyze perceived challenges, and then formulating goals to achieve that may overcome those challenges, can be used to help generate goal lists. These goal lists are then brought together, and the team collaborates to categorize them into a set of 5 or fewer similar themes that are shared between them. When this is finished, the team collaboratively determines the ordering of those categories according to their priority in achieving success.
Team Member Goal Lists
@patmaddox
Goal: Document Committer Workflows
There are a bunch of developers working on this project on a daily basis. I have questions about their workflow and would like to learn from their experience. It would be neat to see how people work, what they do differently, and what they have in common.
- What steps do they take when producing a change to upload to Phabricator?
- How do they use the tools in src/ to assist them?
- What tools have they made for themselves to help with the work?
- Are those tools useful examples to others, or potentially candidates for open sourcing?
- How do they integrate their changes into their own builds prior to it being committed?
- What do they do to eventually land a commit?
Then there's a whole other set of questions for maintaining ports...
I would love to do mini interviews and screen recording sessions - ask questions, and see how they work. Ideally these videos could be published on the YouTube channel. I'd also want to write up instructions from the sessions, to incorporate into pertinent documentation.
Goal: Cherry-pick good info from blogs / forums / mailing lists into the project
from discord thread
- identify content blogs / forums / mailing list that is worth incorporating into project docs
- reach out to the author for interest and permission
follow through on bringing that info into the docs, whether by assisting the author, or other volunteers
Goal: Develop process to identify, encourage, onboard new committers
from discord thread - identify potential committers - analyze bugs.freebsd.org for patches, git repos for applied commits
Proposed and Selected Thematic Categories
Finalized Category Prioritization
Notes and Comments
Future State Analysis
(TBC)