Hi all,
As a reminder, all[1] of your Discovery-related research and coding work should be tracked in phabricator. During our Tuesday/Thursday standups, most of what you talk about should be tasks on one of the "sprint" workboards. If you are working on a task that isn't in the sprint board, please a) re-check to be sure that is the highest priority thing you should be working on, and b) if it is, add it to phabricator and/or to the sprint board as needed.
When you pick what to work on, try to grab something from near the top of the sprint's Backlog column, and move it to In Progress. Please use the Needs Review column as needed, and when the task is really done, move it to Done.
Each sub-team should be focused on its quarterly goal. Please be sure that Dan is aware of any work you do outside that. If you have any questions, check with him, me, or a team lead.
[1] If you do a 15-minutes task here or there, it doesn't need to be tracked in phab. But any substantive work should be. Personally I would set the threshold at about an hour, but your mileage may vary.
Thanks much!
Kevin Smith Agile Coach Wikimedia Foundation
*Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment. Help us make it a reality.*
On Wed, Jul 8, 2015 at 10:51 AM, Kevin Smith ksmith@wikimedia.org wrote:
Hi all,
As a reminder, all[1] of your Discovery-related research and coding work should be tracked in phabricator. During our Tuesday/Thursday standups, most of what you talk about should be tasks on one of the "sprint" workboards. If you are working on a task that isn't in the sprint board, please a) re-check to be sure that is the highest priority thing you should be working on, and b) if it is, add it to phabricator and/or to the sprint board as needed.
When you pick what to work on, try to grab something from near the top of the sprint's Backlog column, and move it to In Progress. Please use the Needs Review column as needed, and when the task is really done, move it to Done.
My bad. In at least one instance David's started some work I suggested in preparation for me leaving that isn't related to the quarterly goal. I created a ticket for it this morning: https://phabricator.wikimedia.org/T105165
It felt like the right thing to do at the time but it could certainly have waited for sprint planning.
Nik
On 8 July 2015 at 08:07, Nikolas Everett neverett@wikimedia.org wrote:
My bad. In at least one instance David's started some work I suggested in preparation for me leaving that isn't related to the quarterly goal. I created a ticket for it this morning: https://phabricator.wikimedia.org/T105165
It felt like the right thing to do at the time but it could certainly have waited for sprint planning.
I read Kevin's email as mostly being about untracked work, and this is appropriately tracked, so good!
Generally, if you're definitely sure something has to be pulled into the sprint for whatever reason (e.g. outrage related work), don't feel like you need to wait for me to rubber stamp it. I trust you all. But, do make sure it's tracked in our sprint board, and do drop me a quick email, or ping me on the card in Phab saying you moved it into the sprint, just so I'm aware. :-)
Thanks!
Dan
On Wed, Jul 8, 2015 at 11:49 AM, Dan Garry dgarry@wikimedia.org wrote:
On 8 July 2015 at 08:07, Nikolas Everett neverett@wikimedia.org wrote:
My bad. In at least one instance David's started some work I suggested in preparation for me leaving that isn't related to the quarterly goal. I created a ticket for it this morning: https://phabricator.wikimedia.org/T105165
It felt like the right thing to do at the time but it could certainly have waited for sprint planning.
I read Kevin's email as mostly being about untracked work, and this is appropriately tracked, so good!
Yeah. I didn't add it until he sent the email though. Its better now!
outrage related work
Typo or just awesome comment? Maybe both!
Nik
There's always going to be bits of work that come up that don't relate to the quarterly goals. That's just the reality, and it's okay. But, please do make sure it's tracked in Phab, so that we can have an honest conversation about whether it's the right thing to do or not.
Thanks!
Dan
On 8 July 2015 at 07:51, Kevin Smith ksmith@wikimedia.org wrote:
Hi all,
As a reminder, all[1] of your Discovery-related research and coding work should be tracked in phabricator. During our Tuesday/Thursday standups, most of what you talk about should be tasks on one of the "sprint" workboards. If you are working on a task that isn't in the sprint board, please a) re-check to be sure that is the highest priority thing you should be working on, and b) if it is, add it to phabricator and/or to the sprint board as needed.
When you pick what to work on, try to grab something from near the top of the sprint's Backlog column, and move it to In Progress. Please use the Needs Review column as needed, and when the task is really done, move it to Done.
Each sub-team should be focused on its quarterly goal. Please be sure that Dan is aware of any work you do outside that. If you have any questions, check with him, me, or a team lead.
[1] If you do a 15-minutes task here or there, it doesn't need to be tracked in phab. But any substantive work should be. Personally I would set the threshold at about an hour, but your mileage may vary.
Thanks much!
Kevin Smith Agile Coach Wikimedia Foundation
*Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment. Help us make it a reality.*
Wikimedia-search mailing list Wikimedia-search@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-search