Webinar Events
Join us for a live webinar:
An Introduction to ScrumWorks Pro

Wed, Jan 7, 2009
10:00 AM - 11:00 AM PST
Sign up online »

Team members in Scrum

Thur, Jan 8, 2009
11:00 AM - 11:45 AM PST
Sign up online »

Default Site Image
Submitted by pparker on June 25, 2008 - 5:06am.

The recent teams I've worked with get wrapped up in hours estimated for each Sprint, over analysis can cause team paralysis. Management wants to ensure each person on the team is at full capacity during a Sprint and want the estimates to match hours available. Unfortunately, it is a reality in most organization that projects are capitalized and the hours spent working on task need to be captured for business reasons. Therefore, they look at the initial estimates as gospel (i.e. in the Waterfall tradition). Until a development organization can show true benefits from loosely coupling task hours and capacity will this problem be resolved.

P.Parker

Reply

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
More information about formatting options

Captcha Image: you will need to recognize the text in it.
Please type in the letters/numbers that are shown in the image above.