Team Practices Group/2016-04-04 best practices

Joel, Grace, Kevin

Purpose
Several teams have come to us asking how to best set up Phab boards for their projects. What should TPG's Best Practice response be?

Grace tends to point to a few examples (TPG, DarTar, Analytics).

Potential agenda ideas

 * 1) What is the range of common boards (e.g. Kanban, Scrum, services, etc.
 * 2) For each board, what is the context that makes it a best practices
 * 3) Pick a best example for each category
 * 4) existing team's board
 * 5) no existing team has a good example/is happy with their own board, so wait
 * 6) Invent our own dummy board and drive people to it
 * 7) Existing teams probably aren't fully using sub-projects and milestones
 * 8) What documents do we want to point to, and maintain?
 * 9) What is the TPG portal location?
 * 10) https://www.mediawiki.org/wiki/Team_Practices_Group/Proposal_for_work_categorization
 * 11) https://www.mediawiki.org/wiki/Phabricator/Project_management#Organizing_your_projects
 * 12) https://www.mediawiki.org/wiki/Phlogiston

Agenda

 * 1) Timeboxed 20 minutes to work through the above topics (roughly 5 minutes per)
 * 2) Use that to come up with a plan (including go/no-go)

GO!

 * 1) What is the range of common boards (e.g. Kanban, Scrum, services, etc.) and what is the best example of each?
 * 2) Scrum
 * 3) Use if: Pure development, dedicated team, have roles staffed (especially, have a ScrumMaster), have some control over backlog 4+ weeks out
 * 4) What board design and process do we recommend if no scrummaster?
 * 5) Android? when it's stable in Q4
 * 6) Community Tech? https://phabricator.wikimedia.org/tag/community-tech/ and https://phabricator.wikimedia.org/tag/community-tech-sprint/
 * 7) Kanban & JIT tasking:
 * 8) Use if: subject to interruptions, or very mature team that doesn't need Sprint mechanism to commit to work and focus
 * 9) Analytics https://phabricator.wikimedia.org/project/view/1030/
 * 10) a bit hosed right now because column counts are broken.
 * 11) backlog: https://phabricator.wikimedia.org/project/view/11/
 * 12) UI Standardization https://phabricator.wikimedia.org/project/view/1806/
 * 13) Scrumban
 * 14) Use if: want to do Scrum but don't meet all pre-requisites
 * 15) Discovery
 * 16) They each have a backlog/sprint pair similar to TPG
 * 17) The backlog half of each is currently in flux, being populated from the original monolithic https://phabricator.wikimedia.org/tag/discovery/
 * 18) Analysis: Sprint: https://phabricator.wikimedia.org/project/board/1241/ Backlog: https://phabricator.wikimedia.org/project/view/1850/
 * 19) Search: Sprint: https://phabricator.wikimedia.org/project/board/1227/ Backlog: https://phabricator.wikimedia.org/project/view/1849/
 * 20) Portal: Sprint: https://phabricator.wikimedia.org/project/board/1235/ Backlog: https://phabricator.wikimedia.org/project/board/1899/
 * 21) TPG: Backlog https://phabricator.wikimedia.org/tag/team-practices/board/ Sprint:  https://phabricator.wikimedia.org/project/view/1105/
 * 22) Horizontal/embedded/Service (e.g. TPG, DR)?
 * 23) Use if: team does most of its work on other boards belonging to other projects, and has team-specific work
 * 24) DR backlog: https://phabricator.wikimedia.org/project/view/1307/
 * 25) DR https://phabricator.wikimedia.org/project/view/839/
 * 26) OIT quals match Kanban more closely, but maybe matches this because most of their work is in a ticket tracking system.
 * 27) TPG: Backlog https://phabricator.wikimedia.org/tag/team-practices/board/ Sprint:  https://phabricator.wikimedia.org/project/view/1105/
 * 28) Broader discussion around boards:
 * 29) Possible organizing principle: should have two main boards, one for by-phase and one for by-category.
 * 30) Possible next work: complete Use Cases for work tracking within WMF projects
 * 31) Pointing to a board, without understanding the associated workflow and processes, might not be helpful
 * 32) Premise that we can recommend a board template depends on assumption that team has process close to board SOP
 * 33) Is this meeting shifting from "Team has a process, wants to set up a board" to "Team wants to know what process they should use"?
 * 34) Documentation
 * 35) Shouldn't start with documents, too off-putting, start with discussion
 * 36) What is our reference doc for people to use?  Is there a need for this?
 * 37) need to separate different users: developer, end-user, PO, admin, etc.

Potential next steps

 * 1) Update our knowledge on how to use newest Phab Pheatures
 * 2) Joel could present on this to TPG?
 * 3) Complete the Phab Use cases (proposals for work categorization)
 * 4) Checking them against a broad pop of users
 * 5) differentiated for different project methodology patterns (scrum, kanban, etc)
 * 6) Completing inventory of existing examples
 * 7) testing best practices example candidates against use cases
 * 8) Writing a friendly HOWTO apply phab to your project (depending on methodology)
 * 9) Should the doc include the phrase "Go talk to TPG"?
 * 10) update our docs related to sub-projects and milestones