Welcome to SpellCoder Sign in | Join | Help

eScrum a Microsoft tool for Scrum

This is new at least for me Microsoft developed a web based Scrum project management tool which is on top of Team Foundation Server, this tools helps the teams that use Scrum project management methodology to manage the project.
It is a free tool, download it from here
also this is a good post that discusses the practices of using eScrum Tool
Quick eScrum Review

Published Friday, July 13, 2007 5:55 PM by Mohammed Hossam
Filed Under:

Comments

# re: eScrum a Microsoft tool for Scrum

Sunday, July 15, 2007 1:51 PM by Mohammed Nour
The weired part in the conversation when she was talking about the number of working hours per day. She said - for her - it's 4h/day - saying that developers don't spend all their day on developing. 50% percent of the day work hours spent on other things. The question is should this point considered when putting the hours/day estimation or not?!

# re: eScrum a Microsoft tool for Scrum

Saturday, July 21, 2007 5:56 PM by Adel
allow me, this should depend on what those thing exactly, is it reports and biz email... or personal email checking...

# re: eScrum a Microsoft tool for Scrum

Monday, July 23, 2007 6:01 PM by mnour
Hi Adel, Actually, as a scrum master, you have no way to control how much people spend on development and how much they don't. You are not spying to know how the team members acting in the entire day hours. Estimation is always hard. But the question that we can specify some kind of error percentage to add to our estimation. The question is how to specify this percentage. It's not just saying 2% over each estimation. I guess it should  be retrieved by some kind of measurement. Thanks

# re: eScrum a Microsoft tool for Scrum

Monday, August 27, 2007 11:55 AM by Dhominator
I'd say no to the original question... estimates are in terms of "effort", not duration.

Velocity helps you scope a sprint. It took a few sprints before I really internalized Velocity tells you how much planned work the team can do in a sprint. Anything other than planned work is considered wastage, a term that may be intentionally provocative. Estimation by Analogy is the primary tool to improve both story and task estimates over time.

On some projects, where wastage seemed high, we included one, or more, "unplanned" stories with "zero story points". This story was used to collect stuff like production support, meetings, and such... so we could see where the time was going, but not get any "credit" for the work.

Best,
John Dhom
Anonymous comments are disabled