Topic on Talk:Team Practices Group/Task Tracking

Option 1: Don't associate goals with tasks

Option 2: Use a separate Phab project for each goal. (see Dao of DarTar))

• Arthur: Would tracking epics for non-core efforts on our weekly board be enough to give folks a sense of capacity/what all is going on with the team?

• Arthur: Are core efforts consistent enough that there's little to no value in tracking them on the board too?

• Arthur: If we adopted the Tao of DarTar (for the record, I'm into it), what are the different project tags that we would employ? Would we remain disciplined enough to ensure we're correctly tagging our tasks with projects/goals/etc?

Option 3: Use a separate Phab column for each goal. Each task can be in multiple boards, but must be on the master board, where it is categorized by column.

Option 4: Use a Phab Task with a blocked by relationship for each goal.

Is this question specifically about TPGer work? I would love to come up with a general answer that will work for engineering teams as well, rather than solve it in a non-standard way.

Does "goal" here mean "departmental quarterly goal"? I hope so, but it would be good to be explicit one way or the other.