Task estimation is probably on the biggest wastes of time I can imagine when it comes to the Agile approach, and planning in general. Most people know by now how hard it is to get a handle of the actual size of the work in terms of man hours and consequently how hard it is to execute on time.
The approach with Agile Kanban I've seen employed seems to make a lot of sense. The idea is to roughly task out work items that cover round about 8 hours of work and schedule these as per usual (prioritization).
Over the course of development with this fixed team, the velocity will be established with regards to certain categories of work items such that planning becomes more accurate as you move along.
That way the focus is on writing good stories/tasks and the planning will eventually become more accurate.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Task estimation is probably on the biggest wastes of time I can imagine when it comes to the Agile approach, and planning in general. Most people know by now how hard it is to get a handle of the actual size of the work in terms of man hours and consequently how hard it is to execute on time.
The approach with Agile Kanban I've seen employed seems to make a lot of sense. The idea is to roughly task out work items that cover round about 8 hours of work and schedule these as per usual (prioritization).
Over the course of development with this fixed team, the velocity will be established with regards to certain categories of work items such that planning becomes more accurate as you move along.
That way the focus is on writing good stories/tasks and the planning will eventually become more accurate.