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.
In Scrum, velocity is the total amount of story points group of
programmers can get through in a sprint. Over time, counting velocity
helps with planning, as the group can make ever more realistic guesses
about how much of the backlog they can schedule for each sprint.
When sizing doc stories, I always counted my own portion as zero,
since I was not a programmer and how much or little time a story took
me had no effect on their velocity. To put it the other way around, I
was not helping the programmers with their stories the way they were
helping each other, so my points didn't belong in the same pool. I
didn't vote, either, since I was not committing myself to
accomplishing the dev tasks. I did take part in the discussions and
sometimes had a big influence on the final votes.
On rare occasions, when it seemed that a story would require
significant developer time, the developers would size their portion,
usually as 1.
On Mon, Jul 14, 2014 at 6:26 AM, McLauchlan, Kevin
<Kevin -dot- McLauchlan -at- safenet-inc -dot- com> wrote:
> I blinked when I saw âzero fibâ. Zero is zero, after all. Only in cosmology are there degrees of none-ness... :-)
> OK, maybe some obscure branch of philosophy.
>
> Some of our groups use the Fibonacci numbered cards for Agile poker/voting, but thereafter we just refer to the effort estimates as... estimates or, in our more truthful moments, as SWAGs.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
