Loading Profile...
Possibility of specifying tasks for each story, and estimating them in hours
In our approach to SCRUM:
- In the release planning we estimate with story points
- In the sprint planning we decompose stories into tasks, and estimate them with hours
This is the method proposed by Mike Cohn in his Agile Estimating and Planning Book.
It would be great if Tracker supported this approach
- In the release planning we estimate with story points
- In the sprint planning we decompose stories into tasks, and estimate them with hours
This is the method proposed by Mike Cohn in his Agile Estimating and Planning Book.
It would be great if Tracker supported this approach
35
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has not planned to implement this.
-
Inappropriate?I concur. Our team SCRUMs with the same method. We like a lot about Tracker but without task estimation it doesn't quite allow us to run our current process. -
Inappropriate?You could try scrumy.com as a work-around for sprint planning and use PivotalTracker for backlog management and release planning.1 Comment
Add a comment
This is one of the best points
-
But with that, the project management is very dificult!
The main feature of the software of project management "must be easy to use for the team" -
Inappropriate?We need that!
a feature can have many chore -
Inappropriate?This is very useful as you often have to gather metric for stakeholders that may not understand points.
-
Inappropriate?We are trying to this cross department: Marketing, Creative, and Tech. Without it, it's impossible to use this for the whole organization.
-
Inappropriate?As a developer, I've come to loathe estimation. When I'm forced to estimate something, I come up with my best honest guess and then quadruple it. Sometimes that works sometimes it is still not large enough. If I'm doing work that can be easily estimated then I might was well work in a factory. Fresh new interesting work cannot be estimated with any amount of accuracy. There are simply too many variables.
I'm doing my best to stay out of environments where the illusion of estimation is maintained.
I’m sad
-
Inappropriate?I'm looking for ideal hour estimation too. I'm trying to implement Scrum with a new team and story points just don't make sense to them right away. (See http://agile.dzone.com/articles/plann...) I'd love to be able to switch between hours and points.
-
Inappropriate?Mike, what we usually do with new teams is to either find the smallest broken down story, and tell them to think of that as a 1 point story, and estimate everything else relatively, considering only complexity and risk. If that doesn't work, start with 1 point = 1 ideal day (or half day). We find that teams quickly embrace complexity estimation, and don't look back, but sometimes it does help to ground points in something concrete.
EMPLOYEE
