Webmaker/TPS: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(47 intermediate revisions by 2 users not shown)
Line 1: Line 1:
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/12rdrihb.png<br>
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/eymnv3uo.png
__NOTOC__
=TPS=
=TPS=
* '''What?''' '''Tactical Priorities Syndicate'''. MoFo leaders who help translate our strategic goals into tactical priorities each two-week cycle.
* '''What?''' '''Tactical Priorities Syndicate'''. MoFo leaders who help translate our strategic goals into tactical priorities each two-week cycle.
* '''Why?''' A more agile working style, distributed leadership, and short, time-bound initiatives that tie back to our quarterly and yearly goals.
* '''Why?''' A more agile working style, distributed leadership, and short, time-bound initiatives that tie back to our quarterly and yearly goals.
* '''Who?''' '''Friendly MoFos here to serve''': David Ascher, Paul Johnson, Chris Lawrence, Geoffrey MacDougall, Cassie McDaniel, Ben Moskowitz, Andrew Sliwinski, Matthew Thompson, Michelle Thorne, Simon Wex
* '''Who?''' David Ascher, Paul Johnson, Chris Lawrence, Geoffrey MacDougall, Cassie McDaniel, Ben Moskowitz, Andrew Sliwinski, Matthew Thompson, Michelle Thorne, Simon Wex '''(tps [at] mozillafoundation [dot] org)'''
* '''How?''' Through weekly TPS meetings. In a collaborative production cycle we design together.  
* '''How?''' Through weekly TPS meetings. In a collaborative production cycle we design together.  
* '''When?''' The TPS meets every Monday ([http://mzl.la/tps_poll time TBD])
* '''When?''' The TPS meets every Monday ([http://mzl.la/tps_poll time TBD]) in the '''TPS Vidyo room'''. Dial-in: 650-903-0800 93 8810#
[[File:TPS heartbeat.012.png|800px]]<br>
==Links==
''TPS meetings happen Mondays, at the beginning and mid-point of each Heartbeat.''
* '''TPS notepad''' https://etherpad.mozilla.org/tps
* '''Webmaker wiki''' https://wiki.mozilla.org/Webmaker (Links to project briefs, key priorities for the current Heartbeat, etc.)
* '''Project Brief Template''' (new) (draft) https://wiki.mozilla.org/Webmaker/Project_Brief A standard project brief template (aka "TPS Report") for teams to use. Outlining the project's goal, roles and tasks.
* '''List of active Webmaker projects and modules'''. (coming soon) A list and visual that explains the varying # of initiatives, using examples of initiatives that will connect w/ impact (e.g. "EOY rapid response team")
* '''[Please add your links here]'''
[[File:Collaborative Production Cycle.011.png|800px]]


= Production cycle =
= Our production cycle =
* '''Collaborative production is our goal'''. MoFos build things. Many different kinds of things -- not just software. Our goal is to work across teams effectively for smart, collaborative production.
* '''We work in two-week "Heartbeat" cycles.''' A well-designed, two-week production cycle helps us do collaborative production better. Working across teams with the right mix of cohesion, empowerment and communication.  
* '''We work in two-week "Heartbeat" cycles.''' A well-designed, two-week production cycle helps us do collaborative production better. Working across teams with the right mix of cohesion, empowerment and communication.  
* '''The TPS helps design and optimize this cycle.''' Meeting at the beginning and mid-point of each Heartbeat to prioritize and allocate resources.  
* '''The TPS helps design and optimize this cycle.''' Meeting at the beginning and mid-point of each Heartbeat to prioritize and allocate resources. [https://wiki.mozilla.org/Webmaker/Heartbeat ''More details taking shape here.'']
* '''Key points''':
** '''Not everything requires two weeks'''. Work gets shipped whenever its done, not just at the end of the sprint. And emergencies get handled as they deserve.
** '''There are planning phases at the beginning of each Heartbeat.''' We do planning and communicating up front, then let take agency to get stuff done.
** '''We report large progress bi-weekly'''. At the end of each Heartbeat, we take stock, demo our best work, and use what we learned to inform the next cycle.  


[[File:Collaborative Production Cycle.011.png|800px]]
==How it works==
 
=How it works=  
The life-cycle of a Heartbeat:
The life-cycle of a Heartbeat:
* '''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.
* '''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.
* '''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.
* '''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 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.  
* '''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.  
'''The result:''' Fewer meetings, smarter communication, more time to get stuff done.  
'''The result:''' Fewer meetings, smarter communication, more time to get stuff done. [https://wiki.mozilla.org/Webmaker/Heartbeat Much more detail on our Heartbeat production cycle here.]


''''How do I get stuff into the queue?'''
* How to get stuff into the Heartbeat production queue.
* Need more detail here
* TLDR: File a TPS report! :) https://wiki.mozilla.org/Webmaker/Project_Brief


==Overview==
[[File:Production Cycle.png|800px]]
* '''Two-week heartbeats'''. We work in two-week cycles or "heartbeats." Not everything can or needs to be done in two weeks -- but it's a helpful way to plan and communicate. ([https://etherpad.mozilla.org/heartbeat-faq Here's a "Hearbeat FAQ" on what, how and why])
=TPS Roadmap=
* '''First Mondays.''' The first Monday of each Heartbeat is special. It's all about planning, brainstorming, and proposing what we want to get done together that cycle. You'll meet in your teams and groups to come up with big ideas and make proposals. It involves a lot more meeting and communicating than other days -- this is where we make sure we're working ''smart'', not just hard.  
===[oct3]===
* '''TPS meetings'''. '''For the TPS group'''. TPS gets together to discuss priorities for each heartbeat. They filter up your proposals to talk about prioritizing, resource allocation, and how they align with our quarterly and yearly goals.  '''Proposal''': these should happen on Mondays. Proposed time: 1pm ET. (Use this Doodle Poll to tell us if that works.)
* DAVID: share the URL of "top 5s". Put it in a spreadsheet.
* '''Webmaker Now meetings''' (aka: "Heartbeat Overview" meeting). '''For everyone working on Webmaker'''. These happen the first Tuesday of each heartbeat. So we can communicate together as a large group, and pull together a crisp shared story of what Webmaker is working on that heartbeat.
* CASSIE: prep for how to do this next week
* '''Demos'''. Happen every Friday at 4pm ET. These are a chance to show what you learned and got done that heartbeat. Big demos happen at the end of the heartbeat. Smaller works-in-progress at the mid-point.  
* MATT:  
* '''Team meetings and stand-ups'''. These are up to individual teams, managers and groups to design, schedule and format. There's a list in progress here: https://etherpad.mozilla.org/standups
** create this TPS wiki.  
** document our production cycle in draft form.  
** set up TPS mailing list and Vidyo room


https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/u6x_vlmw.png
* SIMON:
 
** prep for how to do this next week
==Detail==
** help w. component map
===First Mondays===
===[oct17]===
The first Monday of each heartbeat is special. The focus is on:  
** 1) cleaning up. Dusting off, polishing, pushing to production, or blogging about etc. the stuff you made in the last heartbeat.
** 2) planning. Proposing in teams and groups what you want to get done in the next one.
** 3) teeing up success. This is where we take a regular breathe to think, plan, brainstorm and communicate.  
 
=== '''Webmaker Now meetings''' ===
'''This is the Heartbeat Overview meeting'''. For everyone working on Webmaker. The goal is to:
* a) '''document'''. one crisp headline what each group is working on. captured in an etherpad before the call starts.
* b) '''communicate'''. understand each group is proposing to put on the train that cycle. '''question'''. challenge each other for clarity, prioritization and smart resource allocation.
* c) '''follow up.''' break into small groups for deeper dives. The above should take about 15 minutes of open plenary. Then we can do break-outs with smaller groups for offline conversations where they're most needed.
 
=TPS Roadmap=
[oct3]
* (milestone)
[oct17]
* (milestone)
* (milestone)
[oct31]
===[oct31]===
* (milestone)
* (milestone)
[nov14]
===[nov14]===
* (milestone)
* (milestone)
[nov28]
===[nov28]===
* (milestone)
* (milestone)
[dec12]
===[dec12]===
* (milestone)
* (milestone)

Latest revision as of 14:50, 8 October 2014

eymnv3uo.png

TPS

  • What? Tactical Priorities Syndicate. MoFo leaders who help translate our strategic goals into tactical priorities each two-week cycle.
  • Why? A more agile working style, distributed leadership, and short, time-bound initiatives that tie back to our quarterly and yearly goals.
  • Who? David Ascher, Paul Johnson, Chris Lawrence, Geoffrey MacDougall, Cassie McDaniel, Ben Moskowitz, Andrew Sliwinski, Matthew Thompson, Michelle Thorne, Simon Wex (tps [at] mozillafoundation [dot] org)
  • How? Through weekly TPS meetings. In a collaborative production cycle we design together.
  • When? The TPS meets every Monday (time TBD) in the TPS Vidyo room. Dial-in: 650-903-0800 93 8810#

Links

  • TPS notepad https://etherpad.mozilla.org/tps
  • Webmaker wiki https://wiki.mozilla.org/Webmaker (Links to project briefs, key priorities for the current Heartbeat, etc.)
  • Project Brief Template (new) (draft) https://wiki.mozilla.org/Webmaker/Project_Brief A standard project brief template (aka "TPS Report") for teams to use. Outlining the project's goal, roles and tasks.
  • List of active Webmaker projects and modules. (coming soon) A list and visual that explains the varying # of initiatives, using examples of initiatives that will connect w/ impact (e.g. "EOY rapid response team")
  • [Please add your links here]

Collaborative Production Cycle.011.png

Our production cycle

  • We work in two-week "Heartbeat" cycles. A well-designed, two-week production cycle helps us do collaborative production better. Working across teams with the right mix of cohesion, empowerment and communication.
  • The TPS helps design and optimize this cycle. Meeting at the beginning and mid-point of each Heartbeat to prioritize and allocate resources. More details taking shape here.
  • Key points:
    • Not everything requires two weeks. Work gets shipped whenever its done, not just at the end of the sprint. And emergencies get handled as they deserve.
    • There are planning phases at the beginning of each Heartbeat. We do planning and communicating up front, then let take agency to get stuff done.
    • We report large progress bi-weekly. At the end of each Heartbeat, we take stock, demo our best work, and use what we learned to inform the next cycle.

How it works

The life-cycle of a Heartbeat:

  • 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.
  • 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 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.

The result: Fewer meetings, smarter communication, more time to get stuff done. Much more detail on our Heartbeat production cycle here.

'How do I get stuff into the queue?

Production Cycle.png

TPS Roadmap

[oct3]

  • DAVID: share the URL of "top 5s". Put it in a spreadsheet.
  • CASSIE: prep for how to do this next week
  • MATT:
    • create this TPS wiki.
    • document our production cycle in draft form.
    • set up TPS mailing list and Vidyo room
  • SIMON:
    • prep for how to do this next week
    • help w. component map

[oct17]

  • (milestone)

[oct31]

  • (milestone)

[nov14]

  • (milestone)

[nov28]

  • (milestone)

[dec12]

  • (milestone)
Retrieved from "https://wiki.mozilla.org/index.php?title=Webmaker/TPS&oldid=1023409"