JIRA and GreenHopper requires to set the 'Time spent' and 'Remaining Estimate' during a 'Log Work'. The prefered agile way in Scrum is to only track the remaining estimate and do not waste time in thinking about the question how much time should I log for ISSUE-4711. I was not able to find a way to shift this and only track the remaining estimate.
Is there any way to do this?
I also know that I will lose informations if we do not track the 'Time Spent' but this is okay for us.
The remaining estimate can be tracked via the hours burndown chart. For this to be accurate the remaining time should be cleared to zero when an issues is closed. Alternatively a post function can be added which does this automatically and this will be reflected in the burndown.
Ok, 2 cents about: "only track the remaining estimate". This is totally bogus (I know, I know, scrum teams do not want to actually disclose how much wasted time there's in a project, and I understand why). This is where agile looses in front of traditional methods (well, I also have to say that actually I never saw a self-organizing team - some people are just born leaders and that's immediately seen in any team). Please split the theoretical scrum from the practical one.
That being said "how much time should I log" is a question about team discipline. It is good & important info. Keep track of it. It's just sane ;)
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs