42510RE: [scrumdevelopment] Tracking Actual Hours
- Nov 5, 2009
Thanks for the feedback. We are about to start our first scrum team in Jan., so I am looking forward to the easier reporting. I currently have many Designers and QA who work across multiple projects in a year so tracking this is a bit labor intensive for me.
On Wed, Nov 4, 2009 at 7:58 PM, Ron Jeffries <ronjeffries@...> wrote:
>Your point is well take, Ron. We could, in fact start doing this too.
> For years I took number of people on the project times 40 hours a
> week and reported that. Worked just fine. Auditors didn't care a
Our history has been that any given engineer was working on multiple
projects, some which would be R&D and some maybe not. This required
the reporting of multiple projects by any one engineer.
Scrum and other more Agile practices (planning by team instead of
individual "resources," more focus on project value at the portfolio
level, recognition that task switching is high cost, etc.) has help
change this scattered focus considerably. Nearly all the engineers
are now assigned to one project per sprint. That makes the reporting
you describe possible.
A much better world!
- << Previous post in topic Next post in topic >>