Meeting Notes/2016-01-06 TPG Q3 Planning

What do we need TPG work tracking to do?
Proposed: DStrine: Don't need help with daily priorities, maybe week to month.
 * 1) Help us determine our top priority tasks each day
 * 2) Improve our efficiency by reducing context switching and task fondling
 * 3) Make us more effective by weeding out low-priority work
 * 4) Show our stakeholders our value (for annual planning, quarterly planning, individual performance, strategy)

Kevin, DStrine: Don't see 1-3 as broken enough to need group attention (kevin, Strine: could be improved, but not top item). Kevin: not finding it broken, not the right time to overhaul. Would overhaul for Q4.

Grace: The time we spend each week reviewing existing items that we don't change (aka task fondling) is productive time, not wasted, and it's five seconds per item, not 30.

Item 4 is useful.

What should our work processes by for Q3?
Our current process is: Two Phabricator boards (team-practices and team-practices-this-week); weekly triage (30 min); weekly review/planning (~30 min); monthly retro (1 hr).
 * how do we accomplish each of the goals above?
 * Scrum, Kanban, other?

What needs improvement?

TODO: Joel to finish cleaning up notes below this point.

Max: TPG board is a context switch from embedded team work. Kevin: and nothing pushes me to look at the TPG work (agreement from others) Max: so I show up Thursday [at review meeting] and think, oh yeah.

Joel: Epics column drives me crazy. Max: it doesn't go anywhere, it just sits there. Joel: we don't use it to identify progress toward goals and figure out, "we need to do X this week to get Y done this quarter"

David: What exactly do we need to do in Phabricator (and wiki and meetings) now in order to make Phlogiston work?

How should we do work breakdown?

1) Straight to phab right at the beginning?

2) break it out in Etherpad or Wiki as we conceive it, and then turn it into Phab tasks

3) or in Phab description fields

Principles:

once in phab, keep in phab

zero out the wiki once we start it in Phab, so the wiki

it depends - up to product owner's discretion?

can we ask other people to nagivate through Phab to see scope of work? Grace: on the board. Joel: board is not hierarchical. david: do walkthroughs of stories. Kevin: that works for flat list of stories, but not hierarchies.

Do we need point TPG work?

Max: why do we need to point in order to get the data we need in Phlogiston?

can we use burndowns instead of burnups?

What do we need to change in meetings?

Do daily standup?

Do estimation

- use t-shirt sizes?

What should we do to wrap up Q2 work?
Proposed: Did not discuss.
 * 1) document for Quarterly Review
 * 2) Review Q2 milestones and close some of them?
 * 3) Re-frame standing Goals and Milestones for continuity
 * 4) figure out how to show continuity for Quarterly Goals, in concert with ongoing projects

What are TPG's permanent goals? Straw wolf:
Did not discuss.
 * 1) develop/codify/refine Best Practices
 * 2) help teams do Best Practices directly
 * 3) help teams do Best Practices indirectly
 * 4) coordinate, self-evaluate, maintain TPG

What are TPG's FY2016Q3 full Goals/Milestones?
We have "Quarterly Goals", but we are doing a lot of other work, such as continuing to work embedded with teams. Should we have a list of that?

TODO: Grace is creating a task for everybody in TPG to update the FY2016Q3 standing goals with a list of committed and anticipated work in Q3.

Next Steps
1) make a list of standing goals

2) Make a backlog for all Q3 work where appropriate, i.e., stuff that is a project but not for continuous work. (probably for 100% of quarterly goals, and a fraction of "standing goals"

3) David and Grace to determine a more accurate label for "standing goals"

4) Joel to document this meeting, what we agreed, what we are doing, and open issues to still be resolved ASAP.

Milestone Board aka X Board aka Super-MPL
Issues
 * Prototype X Board for TPG in Google Sheets
 * TPG Milestones in Phabricator
 * TPG in Phlogiston
 * How can this be reframed to remove the quarterly bias and instead show sequence of variable-length milestones?
 * Which technology should this be implemented in?
 * Scale items on board relative to size (by points/count/hours/% of FTE)
 * Should, or how could, there be a catchall bucket to show all the smaller tasks in each bucket?
 * Query Phab at end of quarter and add it manually? How can we track during quarter?
 * How to integrate Maintenance Fraction for TPG? (as pilot of doing MF for non-Engineering teams