I have been told that time tracking in Scrum is "Anti-scrum", however i struggle to find reference to these statements. If Scrum does not mention anywhere "do not track the time" or "track the time", its not a valid statement. However it is something that works for a projects and the projects decide on the practice of time tracking. However if we broaden our vision from project ot organisation , we get no picture on how is the organization performing if we have no clu on estimated vs actual if we have no track of time in projects. Rework is still hidding under the carpet. And i think we need to track time initially till the oraganization becomes mature on processes and we have a good view on project performances.
For me Scrum is just a way of execution which gives a "window" to carry out scoped work for that "window" and in that time "window", we commit to deliver quality.
Subscribe to:
Post Comments (Atom)
Every sprint is time boxed - all work items are in the range of 8-12 man hours - in a 2 week sprint, what is it that one would want to track? There is a concept called product burndown which will tell you that given the weighed product backlog items in story points and team velocity when can you deliver them. Isn't this sort of tracking?
ReplyDeleteYes, it is tracking !
ReplyDeleteBurndown is progress tracking depicting the total task hours remaining per day and velocity can be used to plan projects and forecast release and project/sprint completion dates.
However the other factors for improvement are not considered here e.g. have we reduced rework, are we moving towards defect free delivery, are we proactive to minimize defects, what is the accuracy of estimation and many more questions are still unanswered if we are just calculating burndown and velocity
Scrum, an agile software development framework helps to manage software projects.
ReplyDeleteFor invoicing and time tracking, I use Replicon's time recording software, it is best and amazing application that helps in time and cost management.