Showing content from https://www.mediawiki.org/wiki/VisualEditor/2015_Team_Process_Review below:
VisualEditor/2015 Team Process Review - MediaWiki
- Onboarding and Orientation for Joel and Neil
- Interview with 3 members of the VE team (as it existed pre-reorg) for micro-retrospectives.
- multiple ad-hoc interviews with James and Trevor to start understanding the VE process (and WMF processes)
- asking various people about how Tasks work for VE
- start a list of VE stakeholders Stakeholders
- build a list of standard questions for interviews
- Interview 7 more members of VE team
- Interview 6 more stakeholders
- Extend list of stakeholders/interview candidates (total of 35 names)
- Interview more people
- Complete 1st draft of report
- Most of the team is traveling
- Some editing of the report
Milestone 1: Collect information DONE 9 May 2015[edit] Milestone 2: First draft of report DONE 11 May 2015[edit]
- Complete interviews with all team members
- Complete interviews with majority of stakeholders and at least one representative from each group of stakeholders
- Report has complete outline
- Report includes 75% of notes and ideas from interviews and discussion in some form, either text or notes or diagrams.
Milestone 3: Report distributed to interviewees for feedback. DONE 8 May 2015[edit]
- Report uses only constructive and positive language
- Report sent to all interviewees and anyone else who contributed to the review
Milestone 4: Highest priority challenges identified. DONE 2 Jun 2015[edit]
- Based on input from team leads, stakeholders, and process reviewers
- document contains specific recommendations
- recommendations are prioritized to match challenges
- Relevant stakeholders do not object to changes (and at least some approve of them)
Milestone 6: Process change initiated DONE 12 June 2015[edit]
- List of challenges broken into appropriate sizes and prioritized
- Menu of options for each challenge developed (several options defined, in enough detail to discuss, with pros and cons and with indications where one change may address several challenges)
- Team, team leadership, other stakeholders agree to changes
- All sources of information have had a chance to read it and correct/rebut anything authors misunderstood or misrepresented.
- Document reflects the Foundations communication goals.
- Report converted from Google Doc to Wiki page.
- Report announced on (?) mailing lists, blogs?
Milestone 8: Process changes evaluated for value[edit] Milestone 9: Report archived for reference[edit]
- Report can serve as guide for process change in other teams
- Report updated with results of process change
Reference material[edit]
- "State of the team" report
- top strengths
- top concerns
- from team
- from external stakeholders
- Process diagram showing how VE team works now
- Process Menu with feedback from team
- Suggested progress changes
- Previous WMF Process Review (theoretical model for all of WMF, not specific to VE team)
Interview notes (etherpad)
- Joel and Neil learning the team's processes
- Joel collecting information prerequisite to suggesting any changes as TPG detailee to VE
- Documenting how VE team works because it may be a model for other Editing teams and other teams in WMF
- Provide VE team retrospection on progress up to point of re-org and VE release
- Meet requests from execs for better forecasting and visibility
Information Collection: April
Make changes: May?
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4