<div dir="ltr"><div><div><div><br></div>I'd certainly make use of an available scrummaster. Right now we are just getting started with Agile, and because of the small size of our team, I'm taking on both the product owner and scrummaster role. I know this isn't ideal due to the nature of those two roles, so I'd really like to be able to have someone with expertise to take the scrummaster work. <br>
<br></div><div>Having these resources centralized and available part-time makes a lot of sense since I don't see the need for a full-time scrummaster for one project.<br><br></div></div>- Dan<br><br><br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Mar 3, 2014 at 3:59 PM, Oliver Keyes <span dir="ltr"><<a href="mailto:okeyes@wikimedia.org" target="_blank">okeyes@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>So, I'm not an Engineer, I just work here, but my first thought is: you want to <i>start</i> with 3 staff, and scale it up to 5 within the same budget year, for this?<br><br></div><div>The justification is a pretty good justification for having <i>some</i> resources; teams are finding your knowledge and mentorship useful, you don't have the time to provide as much knowledge and mentorship as people need. But do you and Tomasz really have five staffers' worth of work you're currently having to turn down? Because that's what your ask necessitates. I'd be more comfortable with the idea of hiring a single person and, if they report 'gosh, I'm terribly
overworked', hiring a second or even a third at the start of the next
budget cycle, but I can't see any explanation in your proposal of why five are necessary: the only example of training you guys have provided that you explicitly call out is a session last August.<br><br></div><div>If mentorship on scrumming is necessary, mentorship on scrumming is necessary. But we need to be very careful about how we spend money. What you're asking for is an entire Features team worth of money to train the engineers we currently have - on an opt-in basis. That sort of ask requires an active demonstration that this workload exists, and I'm not seeing it in your argument. I'd like an explanation of where you guys have five scrum-masters worth of work, and why it wouldn't be just as effective, and far more efficient, to take our existing engineers and spend a relative pittance getting the Scrummaster Certification and external training for <i>them</i>that you say the ASG will need anyway.<br>
<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On 3 March 2014 15:44, Arthur Richards <span dir="ltr"><<a href="mailto:arichards@wikimedia.org" target="_blank">arichards@wikimedia.org</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hi everyone,<div><br></div><div>Tomasz Finc and I have been working on a proposal to create an 'Agile Specialist Group' (ASG) in the engineering department that would be dedicated to helping the engineering teams at the WMF that want support in either adopting or evolving an agile approach to software development.</div>
<div><br></div><div><b>We are eager for your feedback</b>:</div><div><a href="https://www.mediawiki.org/wiki/Wikimedia_Engineering/Agile_Specialist_Group" target="_blank">https://www.mediawiki.org/wiki/Wikimedia_Engineering/Agile_Specialist_Group</a><br>
</div><div><br></div><div>Please note that this proposal is to institutionalize and make scalable much of the work we have already been doing - providing mentorship, support, and trainings to those who have asked for it. None of what the ASG would offer would be mandatory. Everything the ASG would offer would be in collaborative service to the team's and individuals seeking its support.<br clear="all">
<div><br></div><div>Please provide feedback either on this list or on the discussion page: <a href="https://www.mediawiki.org/wiki/Talk:Wikimedia_Engineering/Agile_Specialist_Group" target="_blank">https://www.mediawiki.org/wiki/Talk:Wikimedia_Engineering/Agile_Specialist_Group</a></div>
<div><br></div><div>Thanks for your time and input!</div><span><font color="#888888"><div><br></div>-- <br>Arthur Richards<div>Software Engineer, Mobile</div><div>[[User:Awjrichards]]</div><div>IRC: awjr</div>
<div><a href="tel:%2B1-415-839-6885%20x6687" value="+14158396885" target="_blank">+1-415-839-6885 x6687</a></div>
</font></span></div></div>
<br></div></div>_______________________________________________<br>
Engineering mailing list<br>
<a href="mailto:Engineering@lists.wikimedia.org" target="_blank">Engineering@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/engineering" target="_blank">https://lists.wikimedia.org/mailman/listinfo/engineering</a><br>
<br></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br><div dir="ltr">Oliver Keyes<br>Product Analyst<br>Wikimedia Foundation<br></div>
</font></span></div>
<br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><span style="color:rgb(153,153,153)">Dan Foy</span><br><span style="background-color:rgb(255,255,255);color:rgb(153,153,153)">Technical Manager, Mobile Partners</span><span style="color:rgb(153,153,153)">hips</span><br>
<span style="color:rgb(153,153,153)">Wikimedia Foundation</span><br><br style="color:rgb(192,192,192)"><span><span style="background-color:rgb(0,0,0)"></span></span><br>
</div>