TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> My bottom line statement is the same... Estimate the job at 1200 hours, and see
> what happens. Your job in the planning stage of SCRUM is to estimate
> realistically. If you don't have 1200 hours in a 30-day sprint (my calculator
> tells me that requires 40-hour days), then the team has to scale back. It's as
> simple as that. If they don't provide the resources to match the expectations,
> don't blame SCRUM.
This goes for any project planning/scoping model, not just scrum. This
is where waterfalls fail as well, which causes teams to look at scrum
to replace the broken waterfall model. But if you carry over bad
practice and poor scoping/project management practices during the
change, you're looking at broken scrum. GIGO is a constant, even in
recycling.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
LavaCon 2010 in San Diego Sept 29 - Oct 2 is now open for registration.
Use referral code TECHWR-L for $50 off conference tuition!
See program at: http://lavacon.org/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
