How is the maximum value (right end-point) of the X-axis of a GreenHopper Version Report determined? I have a version defined with a Start Date 14/Jul/13 and a Release Date of 20/Sep/13.I would expect the left end-point (the minimum "zero" value) to be the version Start Date and it is. But we have two projects:
1) Real project with 27/Sep/13 as the Release Date. It does not yet have an active sprint. The right end-point of the X-axis of its Version Report is 27/Sep/13 as I would expect.
2) A test project which, over the past few hours, I've created a board, defined a single version with Start Date of 14/Jul/13 and Release Date of 20/Sep/13, created the issues, organized into a sprint, and started the sprint. The Version Report X-axis has a minimum of 14/Jul/13, the release Start Date, as expected. But the X-axis maximum value seems to be 12:00 AM tomorrow (that is, the end of today when I've done all the work). Why is the X-axis maximum value not 20/Sep/13?
Got it--was misinterpreting the report. The solid line is a projection based on the resolved issues, and so updates instantly; it is not a guideline fixed at the start of the version as we thought. The right-most = maximum value of the X-axis is therefore the currently projected completion date + 10% for the "pessimistic" case. In my test project, that project completion date was indeed only a few hours away.
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG