Re: [teampractices] Phabricator workboards appear to show story point, WIP limit, AND count

[James Forrester]

This is because I have that column set to a limit of 0 (because there
shouldn't be any tickets left to triage) which apparently breaks a bit – if
I change the limit to '1' it displays correctly:

[image: Inline images 1]

On 28 April 2016 at 12:36, Max Binder  wrote:

> In James' example, I don't see the separation of count vs points (with the
> points limited). I'd expect to see this, for example:
>
> [image: Inline image 1]
>
> The attached shows that there are 9 cards in the column, totally 74
> points, with a WIP limit of 2 points (I faked this one for an example).
>
> James, is this your experience?
>
> On Thu, Apr 28, 2016 at 12:27 PM, James Forrester <
> jforres...@wikimedia.org> wrote:
>
>> On 28 April 2016 at 12:18, Arthur Richards 
>> wrote:
>>
>>> Cool! What happens if you exceed the WIP limit (eg 9/8)?
>>>
>>
>> ​It shades it red​:
>>
>> [image: Inline images 1]
>>
>> ​J.
>> --
>> James D. Forrester
>> Lead Product Manager, Editing
>> Wikimedia Foundation, Inc.
>>
>> jforres...@wikimedia.org | @jdforrester
>>
>> ___
>> teampractices mailing list
>> teampractices@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/teampractices
>>
>>
>
> ___
> teampractices mailing list
> teampractices@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/teampractices
>
>


-- 
James D. Forrester
Lead Product Manager, Editing
Wikimedia Foundation, Inc.

jforres...@wikimedia.org | @jdforrester
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices

Re: [teampractices] Phabricator workboards appear to show story point, WIP limit, AND count

[Arthur Richards]

Psyched to see this! The fact that this didn't happen previously was a pet
peeve of mine.

On Thu, Apr 28, 2016 at 12:27 PM, James Forrester 
wrote:

> On 28 April 2016 at 12:18, Arthur Richards 
> wrote:
>
>> Cool! What happens if you exceed the WIP limit (eg 9/8)?
>>
>
> ​It shades it red​:
>
> [image: Inline images 1]
>
> ​J.
> --
> James D. Forrester
> Lead Product Manager, Editing
> Wikimedia Foundation, Inc.
>
> jforres...@wikimedia.org | @jdforrester
>
> ___
> teampractices mailing list
> teampractices@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/teampractices
>
>


-- 
Arthur Richards
Team Practices Manager
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices

Re: [teampractices] Phabricator workboards appear to show story point, WIP limit, AND count

[James Forrester]

On 28 April 2016 at 12:18, Arthur Richards  wrote:

> Cool! What happens if you exceed the WIP limit (eg 9/8)?
>

​It shades it red​:

[image: Inline images 1]

​J.
-- 
James D. Forrester
Lead Product Manager, Editing
Wikimedia Foundation, Inc.

jforres...@wikimedia.org | @jdforrester
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices

Re: [teampractices] A tool for keeping action items accountable?

[Kevin Smith]

As a facilitator of (monthly) retrospectives for Discovery, shortly after
the meeting I have emailed an "action items" reminder to anyone who was
assigned one. Typically that's a few days after, at the same time the notes
get put on wiki. Then, during the following retrospective, we start off by
reviewing the status of previous action items. Similar to what Guillaume
described, but a bit lighter.

Recently, I have started to create a calendar event for myself at the
midpoint between retros (at about the 2 week mark). At that point, I email
a reminder to action item owners. I don't yet know whether this is
appreciated, and/or if it will help increase the rate of action items being
completed.

If I create the retro etherpad/google doc a few days before the next retro,
I might send yet another email reminder to action item owners. But I'm not
committing to that.


Once someone owns an action item, I trust them to create a phab task, or
not, as they see fit. Often the action item is "Create a phab task for X",
and adding a task to create another task would be silly. I think most
action items are along the lines of "Convene a meeting about X", or
"Discuss X with Y".



Kevin Smith
Agile Coach, Wikimedia Foundation


On Wed, Apr 27, 2016 at 1:23 PM, Greg Grossmeier  wrote:

> That's basically how we do it in releng during our meetings.
>
> --
> Sent from my phone, please excuse brevity.
> On Apr 27, 2016 10:20 AM, "Guillaume Lederrey" 
> wrote:
>
>> In another life, I have been facilitating a few retrospectives. Not
>> here yet, so the context is probably different and this past
>> experience probably does not apply without the necessary amount of
>> tweaking. Still:
>>
>> The usual rule we put in place with our teams was: "A retrospective
>> action must have a fairly limited scope and be possible to implement
>> before the next retrospective". Larger items are not considered to be
>> retrospective actions, but might be put into the team backlog. Action
>> items are the responsibility of their owner (if we can't find an owner
>> for the action, the action is dropped). The facilitator responsibility
>> is to check the status of those actions at the next retro. If those
>> actions have not been completed by the next retro, they are either
>> dropped (if we did not make progress, they are probably not as
>> important as we thought), converted as backlog item (they were larger
>> than we initially thought), or kept as action item for the next retro
>> (rare case).
>>
>> With those rules, we don't rely on specific tools...
>>
>> No idea how this applies at WMF...
>>
>>
>> On Wed, Apr 27, 2016 at 9:55 AM, Quim Gil  wrote:
>> > Could you provide examples of these "action items"? It will help
>> > understanding the relevance of "non-dev/product" action items coming
>> out of
>> > (presumably dev/product) sprint retrospectives.
>> >
>> > This sounds like a matter of threshold:
>> >
>> > * If an action item is purely personal, then sure, use the purely
>> personal
>> > tool to deal with it.
>> > * If an action item has an impact on the team, then use the team tool to
>> > deal with it, no matter how simple, small, "non-dev/product".
>> >
>> > Is it fair to assume that most actions coming out of a sprint
>> retrospective
>> > will have impact on the team?
>> >
>> > This is where the fear to i.e. bringing back Trello doesn't sound any
>> > visceral to me, but well justified. Someone starts creating strictly
>> > personal actions in Trello (Asana, etc), they continue adding other
>> small
>> > actions because 'since we are using this tool anyway and I'm writing the
>> > actions quickly after the meeting'... Three months down the road that
>> > parallel board has got a life on its own, they start having tasks
>> > duplicating with the team's tasks in Phabricator, some things fall
>> between
>> > the cracks...
>> >
>> > Yes, I know this would not happen to *you* or *your* team (whoever *you*
>> > are), but looking at our history we have solid reasons to think that
>> this
>> > will certainly happen to *someone*, and then that will be taken as a
>> > reference by * someone else* not reading this thread today, and then...
>> >
>> >
>> >
>> > On Wed, Apr 27, 2016 at 1:49 AM, Max Binder 
>> wrote:
>> >>
>> >> The first thought was to use existing Phabricator boards, but the team
>> >> agreed that Phab was a lot of overhead for reminding folks to follow
>> up on
>> >> non-dev/product tasks.
>> >
>> > Why overhead? Creating a minimally acceptable Phabricator task takes one
>> > title and one project to associate it with. Even a description is
>> optional.
>> > If that project is #Team-X-Internal-Stuff, then the rest can't be
>> bothered.
>> >
>> > If the "overhead" concern also (or actually) encompases a concern about
>> lack
>> > of privacy (i.e. "John to get a headset that actually works in
>> hangouts")
>> > then you can always request a 

Re: [teampractices] Phabricator workboards appear to show story point, WIP limit, AND count

[Arthur Richards]

Cool! What happens if you exceed the WIP limit (eg 9/8)?

On Thu, Apr 28, 2016 at 11:00 AM, Max Binder  wrote:

> I noticed a change over the last few days.
>  [image: Inline image 1]
> This example attached shows that the column is counting 1 card, 1 point,
> with a WIP limit of 1 out of 8. Teams have been requesting card count for a
> long time (Kanban, for example, uses card count rather than points), so
> this is good news!
>
> I've tested this new implementation, and confirmed my observation above.
> However, I've also confirmed that the WIP is still points-based, rather
> than count-based, but this is a good first step! :)
>
> ___
> teampractices mailing list
> teampractices@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/teampractices
>
>


-- 
Arthur Richards
Team Practices Manager
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices

[teampractices] Phabricator workboards appear to show story point, WIP limit, AND count

[Max Binder]

I noticed a change over the last few days.
 [image: Inline image 1]
This example attached shows that the column is counting 1 card, 1 point,
with a WIP limit of 1 out of 8. Teams have been requesting card count for a
long time (Kanban, for example, uses card count rather than points), so
this is good news!

I've tested this new implementation, and confirmed my observation above.
However, I've also confirmed that the WIP is still points-based, rather
than count-based, but this is a good first step! :)
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices