Sprint plan always reports progress with hours
The Sprint Plan seems fixed to use hours instead of whatever is set in the planning complexity attribute. The Sprint template sets that attribute to points and Release and Team Plans show progress using points. But Sprint Plans are always measured in hours. Changing the planning complexity attribute has no effect on Sprint Plans, only Release and Ream plans (top-level).
Does iteration planning require all stories to be broken into something measured in hours? Maybe there should be seperate complexity attributes for top-level plans and execution-level plans.
Many thanks.
Does iteration planning require all stories to be broken into something measured in hours? Maybe there should be seperate complexity attributes for top-level plans and execution-level plans.
Many thanks.
One answer
The Sprint Plan seems fixed to use hours instead of whatever is set in the planning complexity attribute. The Sprint template sets that attribute to points and Release and Team Plans show progress using points. But Sprint Plans are always measured in hours. Changing the planning complexity attribute has no effect on Sprint Plans, only Release and Ream plans (top-level).
You are right. Complexity is used in Release and Team Plans only. Currently, Sprint Plans show hours only. We are aware of this limitation and have that in mind while working on 3.0.
Does iteration planning require all stories to be broken into something measured in hours? Maybe there should be seperate complexity attributes for top-level plans and execution-level plans.
Well, I think it should be like that. The sprint/iteration is the place where the story is going to be implemented and that should be done on the basis of (implementation) tasks.
Note: As a workaround -to see the point per sprint/iteration- you can open a release plan and view in the