I agree with most of what has been said here. My only concern/suggestion from the original post is that the guidelines about who should enter point values need to avoid putting staff in a special category. The last thing we need right now is to put up barriers between staff and community.
David's summary on wiki nicely avoids that trap (yay!): "The person or team who estimates a task should be the ones who will eventually do the task". Works for me (although I might replace that final "task" with "work". Kevin Smith Agile Coach, Wikimedia Foundation On Thu, Feb 18, 2016 at 12:18 PM, David Strine <[email protected]> wrote: > +1 and to build on Bryan's comment: > It may help to have a cross team task with linked subtasks for individual > teams. A specific subtask can be estimated in the context of the team who > owns it. > > I would also want to leave this point up to the teams who share the work. > I don't think anyone is going to be able to police all the cross team tasks > but we should have recommendations for team who have this problem. > > Also I've added this to the wiki page about the upgrade here: > https://www.mediawiki.org/wiki/Phabricator/Feb_2016_Upgrade > > > > On Thu, Feb 18, 2016 at 12:08 PM, Bryan Davis <[email protected]> wrote: > >> On Thu, Feb 18, 2016 at 12:54 PM, James Forrester >> <[email protected]> wrote: >> > This is mostly an issue for tasks that sit in multiple teams' boxes. >> For VE >> > I've 'til-now set these to 0 if externally blocked (e.g. >> > https://phabricator.wikimedia.org/T119780 ), but that only works if the >> > other team(s) involved don't want to set points themselves. >> > >> > When points were only available to the few teams using the Sprint >> extension >> > this was no-one, to a first approximation (off the top of my head, two >> tasks >> > have had clashes like this in the past year, and no-one cared enough to >> > enforce their way over others). Now all projects have it, it's much more >> > likely to be a thing. >> >> The pedantic scrum nerd that I try to keep locked up in the back of my >> skull says that a task that is passed around from team to team is not >> of a granularity that estimable for sprint work. It may be an epic or >> theme that has been given some estimation for the purpose of backlog >> grooming but those points are not comparable to sprint task points. >> >> Bryan >> -- >> Bryan Davis Wikimedia Foundation <[email protected]> >> [[m:User:BDavis_(WMF)]] Sr Software Engineer Boise, ID USA >> irc: bd808 v:415.839.6885 x6855 >> >> _______________________________________________ >> teampractices mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/teampractices >> > > > _______________________________________________ > teampractices mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/teampractices > >
_______________________________________________ teampractices mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/teampractices
