<div dir="ltr">Our boards are a WIP too and we're eager to use burndown for Phabricator once it's deployed (<a href="https://phabricator.wikimedia.org/T153">https://phabricator.wikimedia.org/T153</a>)<div><br></div><div>Our main backlog board is here:</div><div><a href="https://phabricator.wikimedia.org/project/board/840/">https://phabricator.wikimedia.org/project/board/840/</a><br></div><div>It's where we groom our tasks, prioritize and point them. Many of these tasks cover our various platforms which each have their own project (Analytics-EventLogging, Analytics-Wikimetrics, etc)</div><div><br></div><div>At our sprint planning meeting, we create a new project (type sprint) and move the item to that new board. It helps keep distinct what the team has committed to from the backlog:</div><div><a href="https://phabricator.wikimedia.org/project/board/848/">https://phabricator.wikimedia.org/project/board/848/</a><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 2, 2014 at 1:54 PM, Antoine Musso <span dir="ltr"><<a href="mailto:hashar+wmf@free.fr" target="_blank">hashar+wmf@free.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Le 02/12/2014 22:32, S Page a écrit :<br>
<span class="">> Do other teams have team boards in Phabricator?<br>
<br>
</span>Sure!<br>
<br>
MediaWiki-Core-Team:<br>
<a href="https://phabricator.wikimedia.org/project/board/37/" target="_blank">https://phabricator.wikimedia.org/project/board/37/</a><br>
<br>
Release-Engineering:<br>
<a href="https://phabricator.wikimedia.org/project/board/20/" target="_blank">https://phabricator.wikimedia.org/project/board/20/</a><br>
<br>
The later being my team. Among other projects, we are responsible for<br>
the Beta cluster (staging area) and Continuous Integration which have<br>
their own boards:<br>
<br>
CI: <a href="https://phabricator.wikimedia.org/project/board/401/" target="_blank">https://phabricator.wikimedia.org/project/board/401/</a><br>
Beta cluster: <a href="https://phabricator.wikimedia.org/project/board/497/" target="_blank">https://phabricator.wikimedia.org/project/board/497/</a><br>
<br>
CI uses software components such as jenkins and zuul which might well<br>
have their own boards. I merely load the default page which list opened<br>
task, ex for 'zuul': <a href="https://phabricator.wikimedia.org/tag/zuul/" target="_blank">https://phabricator.wikimedia.org/tag/zuul/</a><br>
<br>
<br>
For both beta cluster and CI, only parent / tracking tasks are marked<br>
with the team project. That helps keep the team workboard light weight<br>
for our weekly team check-ins.<br>
<br>
<br>
As the lead for CI, I open the workboards several times per day and move<br>
cards around as needed. I even created my own dashboard which I have<br>
'installed' as the default Phabricator homepage:<br>
<br>
<a href="https://phabricator.wikimedia.org/dashboard/view/6/" target="_blank">https://phabricator.wikimedia.org/dashboard/view/6/</a><br>
<br>
It has:<br>
<br>
- a text box with links to the board / projects that matter to me<br>
- tasks assigned to me by priority<br>
- tasks I authored<br>
- team related searches<br>
- all tasks I am subscribed to<br>
<br>
That let me look for a task using my browser search.<br>
<br>
<br>
Some troubles I have:<br>
<br>
<br>
I often end up closing tasks without moving to the appropriate column.<br>
That is merely to save a few page loads and clicks. Once closed, a task<br>
disappear from the workboard, so it is imho not much of an issue.<br>
<br>
<br>
Often tasks are blocked by another team / project. I am considering<br>
opening sub task for the other team so they can assign/set priority<br>
according to their rule / triage workflow. So I would end up with:<br>
<br>
T42 install more servers for CI<br>
project: continuous-integration<br>
assignee: me!<br>
priority: high<br>
column: externally blocked<br>
<br>
T43 install servers for CI<br>
project: operations<br>
assignee: none<br>
priority: need triage<br>
column: backlog<br>
<br>
This way it is clear that CI wise I am responsible for that action, on<br>
the other hand it is clear that ops need to acknowledge it.<br>
<br>
Potentially each card could have a per project assignee/priority much<br>
like they have a per project column.<br>
<br>
<br>
We are still iterating / figuring out a good workflow. I guess it would<br>
take us all a few more weeks to refine.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
Antoine "hashar" Musso<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<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>
</div></div></blockquote></div><br></div>