<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><b><a href="https://teach.etherpad.mozilla.org/crossteam-Q2">https://teach.etherpad.mozilla.org/crossteam-Q2</a></b></div><div><b><a href="https://teach.etherpad.mozilla.org/crossteam-Q2">https://teach.etherpad.mozilla.org/crossteam-Q2</a></b></div><div><b><a href="https://teach.etherpad.mozilla.org/crossteam-Q2">https://teach.etherpad.mozilla.org/crossteam-Q2</a></b></div><div><b>9am PT / 12pm / 4PM UTC </b></div><div><br></div><div>Apologies for the later than usual send on this -- I wanted to get the blog post below finished first.</div><div style="font-weight: bold; "><br></div><div>I'm going to suggest that tomorrow's call focus on two main topics:</div><div><b>(1) What did we ship in Q1? </b></div><div><b>(2) How do we refine how we work together in Q2?</b></div><div><b><br></b></div><div>I've been working with many of you on (2) -- </div><div>and this blog post lays out some of that thinking:</div><div><br></div><div><div><b>The scrum never stops: building a better workbench for Webmaker</b></div><b><a href="https://blog.webmaker.org/scrum">https://blog.webmaker.org/scrum</a></b></div><div><b><br></b></div><div>We'll do some silent etherpadding on (1) to start the call. </div><div>Then dig into (2) together. </div><div><b><br></b></div><div><b>Please try to read the blog post before the call. </b>Or just the TLDR version I've pasted below. </div><div><b><br></b></div><div><b>Talk to you tomorrow!</b></div><div><b><br></b></div><div>--OpenMatt</div><div><br></div><div><header class="entry-header">
<h1 class="entry-title">The scrum never stops: building a better workbench for Webmaker</h1><div><a href="https://blog.webmaker.org/scrum">https://blog.webmaker.org/scrum</a></div><p class="entry-posted">As we head into Q2, let’s build a better “workbench” and online scrum board for Webmaker.</p></header><div class="entry-content"><p><strong>TLDR version:</strong></p>
<ul>
<li><strong>Check out the freshly udpated <a href="https://wiki.mozilla.org/Webmaker">Webmaker Wiki</a>.</strong>
It’s one-stop shopping for key roadmaps, planning documents, tickets,
and scrums. And will help provide more transparency and co-ordination
across teams going forward.</li>
<li><strong>It clearly lays out Webmaker’s <a href="https://wiki.mozilla.org/Webmaker">key components</a>. </strong>And
how they all fit together. From teaching kits and training to
localization, badges, and Maker Party. These will provide the main
tracks for our scrum board as we go forward.</li>
<li><strong>Shifting to real time<span style="text-decoration: underline;"> production,</span> instead of static <span style="text-decoration: underline;">documentation</span></strong>. The new wiki is a <em>production</em>
document. The main goal is to provide a clear view of *what we’re
building now.* Week by week, quarter by quarter. Instead of a static
repository for documentation that quickly goes out of date.</li>
<li><strong>Project scrum boards</strong>. To that end, each <a href="https://wiki.mozilla.org/Webmaker">individual project page</a>
will lead with a virtual scrum board at the top of the page. We’ll
embed Bugzilla tickets to do this, and use Bugzilla components and
whiteboard tags to do it in a smart, automated way. <em>(If you don’t use Bugzilla, just include links to wherever you’re tracking the work.)<span id="more-11215"></span></em></li>
</ul><p><br></p></div></div><div><br></div><div><br></div></body></html>