Meeting Notes/2015 Dec 8 TPG Goals Review Meeting

These notes have not been reviewed for accuracy by the participants and may not reflect their views, even when directly attributed.
 * "TPG decides/tests/starts implementing TPG Strategy" should be a goal


 * The table for goals should also show (1) goals from last quarter, so we can see continuity of goals and what is completed or discontinued; (2) standing goals, so we can see whether or not all standing goals are covered.


 * Can we phrase goals in terms of # of teams we are supported?
 * Tried that previously and it was rejected
 * Are we getting sufficient (relative to cost) value from these goals at the group level, independently of the requirement to report them up?
 * We should have a max of three goals to have a good chance of meeting most of them.
 * Proposal for what the three goals should be:
 * TPG strategy
 * Something addressing Wes's target of "Every engineering can report their average percentage of core work relative to new work." Incorporating Maintenance Fraction, metrics, burnups, evidence-based planning.
 * Grace: if that depends on engineering work from Analytics, make sure you talk to Analytics before publishing something about this
 * David: Sounds like there is a deeper need behind just a maintenance fraction number, so we should find out what that is and get that deeper need into the goal.
 * Arthur:
 * Either a second goal around metrics, or something from standing goals.
 * Kristen: should we have a goal around team off-sites?