On 17 June 2015 at 15:52, Kevin Smith wrote:
> Thanks Dan! Can you say more?
>
> In that case, you had a product backlog project that spanned multiple
> sub-teams, and had a column for each. Are you saying that the tech leads
> would pull items from "To Triage" into their column, and also move it
Thanks Dan! Can you say more?
In that case, you had a product backlog project that spanned multiple
sub-teams, and had a column for each. Are you saying that the tech leads
would pull items from "To Triage" into their column, and also move items up
and down within their own sub-team column?
Did t
While I was on the Mobile Apps Team, the tech leads of each respective team
had a fair bit of delegated authority to do bug triage themselves and make
product decisions about small-scale things without involving me. I had the
right as product owner to overrule them, but this happened so rarely that
In a recent discussion[1], Quim said:
"Meetings support Grooming, not the other way around. Grooming is an
ongoing, asynchronous, remote-friendly activity open to everybody's input.
Meetings are synchronous and, in practice, leaning towards restrictiveness
and co-location (the problem of distance
These scales are used when UX, art style and usability are major focuses.
These are qualitative goals. You're right, projects are never done. These
targets help teams set qualitative goals and quality bars.
I can't relay the specific implementations from other companies and I left
out one key idea
