Le 18/02/2016 20:05, Joel Aufrecht wrote:
> The points field is now global to all tasks, raising some interesting
> questions:
>
> 1) What do engineers/product owners (staff or otherwise) working on
> tasks do when community members set or change points?
I would not differentiate between an organ
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
+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 t
On Thu, Feb 18, 2016 at 12:54 PM, James Forrester
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
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 t
>
> What should we do about making points consistent across teams?
To clarify, do you mean teams using the same points to mean the same thing?
Currently, I suspect teams use points to mean different things (Team A says
5 points is "a day's work" while Team B says 5 points is "two day's work"
whil
I agree with what you say about points should be estimated by the engineers
and points comparisons are verboten.
On Thu, Feb 18, 2016 at 11:05 AM, Joel Aufrecht
wrote:
> The points field is now global to all tasks, raising some interesting
> questions:
>
> 1) What do engineers/product owners (st
The points field is now global to all tasks, raising some interesting
questions:
1) What do engineers/product owners (staff or otherwise) working on tasks
do when community members set or change points?
2) What should we do about making points consistent across teams?
My initial thoughts/proposa
