Webmaker/TPS: Difference between revisions

Webmaker/TPS (view source)

Revision as of 21:18, 2 October 2014

90 bytes added , 2 October 2014

→‎How it works

Matt Thompson

Confirmed users

9,624

edits

@@ Line 17: / Line 17: @@
 =How it works=
-TLDR:
+The life-cycle of a Heartbeat:
-* '''Small groups gather on First Mondays.''' Small groups and cross-functional teams get together on the first Monday of each Heartbeat. To discuss what their team wants to get done together over the next two weeks. The TPS then meets to review everyone's proposals.
+* '''Plan on Monday.''' Small groups and cross-functional teams get together on the first Monday of each Heartbeat. To discuss what their team wants to get done together over the next two weeks. The TPS then meets to review everyone's proposals.
-* '''The entire Webmaker tribe gathers on Tuesday'''. To review and talk about about the finalized list of priorities. We start in open plenary, then break into small groups for deep dives as needed. Everyone leaves  with a shared sense of what we're all working on together that Heartbeat.
+* '''Communicate on Tuesday'''. The entire Webmaker tribe gathers on Tuesday. To review and talk about about the finalized list of priorities set by the TPS. Everyone leaves  with a shared sense of what we're all working on together that Heartbeat.
-* '''That's it!''' The rest of the two weeks are up to you. You can add on additional meetings or stand-ups as you and your manager see fit. We get together at the end of the cycle to demo what we got done.
+* '''That's it!''' The rest of the two weeks are your own. You can add on additional meetings or stand-ups as you and your manager see fit. The TPS meets at the mid-point to look ahead and ensure we're on track. And we get together at the end of the cycle to demo and celebrate what we got done.
-= Fewer meetings, more time to get stuff done.
+= '''The result:''' Fewer meetings, smarter communication, more time to get stuff done.