Category Maturity Scorecard - Plan:Project Management FY21-Q2 IACV - Validate complete maturity of Issue Tracking
Current discussion occurring in Mural
- Research issue: https://gitlab.com/gitlab-org/ux-research/-/issues/900
- Previous score and scorecard: N/A
- Walkthrough: {{add link to YouTube video or walkthrough document}}
- Recommendations: {{add link to your recommendation issue/s}}
Category Maturity Scorecard Checklist
Learn more about Category Maturity Scorecards
-
Review the Category Maturity Scorecard handbook page and follow the process as described. Reach out to the UX Researcher for your stage if you have questions. -
Document the results of each JTBD scenario using this template -
Add links for each participants' session recordings. Consider downloading the session videos from Zoom, and uploading them to the shared Google UX Research folder in the appropriate section/stage/project folder. -
If the participant has not granted permission to share the recording publicly, ensure the sharing settings are set to GitLab-only. -
If needed, create a recommendation issue for these sessions.
CM Scorecard Results Template
Jobs to be done
- When planning an iteration, I need to understand the team’s capacity in order to know how to prioritize and manage stakeholder expectations
- When planning an iteration, I need to be able to break down business ideas into workable units
- When reviewing a plan, I need to ensure that high-risk items can be identified and continually monitored so I can validate and modify mitigation plans.
- When monitoring a team's status, I need to be able to easily review and digest the current progress so that I can confidently explain progress to stakeholders.
- When working through a list of validated opportunities, I need to be able to understand effort and map ROI for each, so I can prioritize the right sequence of work.
- When working through a list of validated opportunities, I need to be able to provide and receive feedback on an idea with the team so they can gauge effort and know how to prioritize.
- When working through a unit of work, I need to be able to flag something as at risk so that my stakeholders and team know something needs attention.
- When iteration planning, I need to be able to add estimates to units of work so that my stakeholders understand mine and team capacity and can plan, prioritize work.
- When iteration planning, I need to be able to provide and receive feedback on an idea with my internal stakeholders so that they can gauge effort and I know how to estimate.
- When iteration planning, I need to be able to commit to work by assigning myself so that my team and stakeholders know what I’m working on.
Scenarios
- Scenarios breakdown for issue tracker (PM and engineering leads) role: https://docs.google.com/spreadsheets/d/1IA9p60GPgxmYkorG0cf-Tz5tahgSH0lvCVwbLIfk_9k/edit#gid=0
- Scenarios breakdown for issue worker (engineers, designers, etc.) role: https://docs.google.com/spreadsheets/d/1IA9p60GPgxmYkorG0cf-Tz5tahgSH0lvCVwbLIfk_9k/edit#gid=272160495
Participants
Sachin F.
- Role: Issue tracker (Lead engineer)
- Top 3 tasks/responsibilities:
- Developing high quality code
- Making sure the team also makes high quality code
- Create and adopt latest technologies
- GitLab usage: Has been using GitLab for the past 4-5 years
- Video link (in Dovetail)
Shane P.
- Role: Issue worker (Data scientist/software engineer)
- Top 3 tasks/responsibilities:
- Handling defects from Splunk
- Application performance monitoring
- Machine learning
- GitLab usage: Has been using GitLab for the past 6 years
- Video link (in Dovetail)
Matthew B.
- Role: Issue tracker (Product manager)
- Top 3 tasks/responsibilities:
- Managing the sprint cycle for the product
- People management
- Escalation management... routing production issues, client needs, etc.
- GitLab usage: Doesn't use GitLab
- Video link (in Dovetail)
Alison M.
- Role: Issue worker (Product designer)
- Top 3 tasks/responsibilities:
- Worked on assigned issues
- Creating design deliverables
- Communicating with stakeholders
- GitLab usage: Less than 1 year
- Video link (in Dovetail)
Igor K.
- Role: Issue tracker (IT Manager)
- Top 3 tasks/responsibilities:
- Budgeting, IT related tasks, hardware
- Hardware maintenance, software installation
- Project management
- GitLab usage: Over a year
- Video link (in Dovetail)
Gustavo M.
- Role: Issue worker (Full stack dev)
- Top 3 tasks/responsibilities:
- Write code
- Test code
- Review others' code
- GitLab usage: None
- Video link (in Dovetail)
Nikunj D.
- Role: Issue worker (Developer)
- Top 3 tasks/responsibilities:
- Writing code
- Deployment of apps
- Troubleshooting deployments
- GitLab usage: Little to none
- Video link (in Dovetail)
Kelly M.
- Role: Issue tracker (IT manager)
- Top 3 tasks/responsibilities:
- Help developers daily
- Work with managers to determine tools and software for the team
- Also determining technologies and tools for connecting with faculty members and students
- GitLab usage: Some but does not consider self an expert
- Video link (in Dovetail)
Juhi S.
- Role: Issue worker (Senior software engineer)
- Top 3 tasks/responsibilities:
- Development
- Working on infrastructure side... determining resources needed to build the system.
- Managing the code and pushing the changes for the team.
- GitLab usage: 2-3 years
- Video link (in Dovetail)
Brandon W.
- Role: Issue tracker (Product Manager)
- Top 3 tasks/responsibilities:
- Making sure the engineering team has current and up to date work
- Making sure their backlog is groomed and prioritized
- Making sure obstacles are removed and fires are put out
- GitLab usage: Over a year
- Video link (in Dovetail)
Tuilly M.
- Role: Issue tracker (Technical product manager)
- Top 3 tasks/responsibilities:
- Roadmap planning
- Prioritizing current work
- Planning future work
- GitLab usage: None
- Video link (in Dovetail)
Anh N.
- Role: Issue worker (Junior software developer)
- Top 3 tasks/responsibilities:
- Automation
- Front end, back end development
- UI feature work
- GitLab usage: About a year
- Video link (in Dovetail)
Luke W.
- Role: Issue worker (Software developer)
- Top 3 tasks/responsibilities:
- Completing stories, implementing code, writing code
- Reviewing code from team members
- Production support/debugging
- GitLab usage: A little over a year
- Video link (in Dovetail)
Luke W.
- Role: Issue worker (Product manager)
- Top 3 tasks/responsibilities:
- Maintaining the roadmap
- Writing requirements for engineers
- Interfacing with customers to get feedback on the roadmap or certain features, or discover new problems that they have
- GitLab usage: Less than a year
- Video link (in Dovetail)
Other notes
- This was one of the first CMS attempts and the process has evolved since then.
- I'd determined the two primary users of the issue tracking set of features and workflow were roles I defined as the "issue tracker" which is typically a product manager or engineering team lead, or the "issue worker" which may be the team member such as engineers, designers, etc. Testing was done with both roles.
Edited by Holly Reynolds