I concur that productivity is still mainly time measured and most project planning tools should be described as old wine fit for old wineskins. They need tweaking to fit into new wineskins and new thinking. Nevertheless, with scrum since productivity is that of the team and not of an individual team member, work allocation is for instance done in points, the no of points delivered within a sprint help determine team velocity which is then linked to time; valued by the business.
On 29 June[masked]:25, Scot McSweeney-Roberts <[address removed]>
On Fri, Jun 29, 2012 at 11:54 AM, Dominic <[address removed]>
Also, when you start assigning time to coding task, you are already doing scrum wrongly.
It doesn't help that "hours" appears to be the default metric in a lot of project planner software (or at least, the ones I've used). While it's usually easy to change, I think it shows there's still a lot of inertia around measuring effort and/or productivity in units of time.
This message was sent by Scot McSweeney-Roberts ([address removed]) from LJC - London Java Community.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
To learn more about Scot McSweeney-Roberts, visit his/her member profile