Intent faster than Estimating

[Code Like Hell]

Much easier to use as well, in terms of clear motivation and having a
clear idea of the task, or process, at least. Wouldn't it be faster,
instead of estimating stories, to list intentions for the day? It's
what it all boils down to anyway--I intend to finish this by 5--it
makes it very clear in your mind. That's what you tell them in an
actual conversation. Estimation and assessment of stories seems
unengaged by comparison. Estimating stories is such a pain--just ask
me what I intend to do, and measure if I get what I intended to do to
figure velocity. This is probably already in the wiki somewhere.

[Code Like Hell]

"Phlip" <phlip_cpp@yahoo.com> wrote in message news:<osLRa.784$2N3.655@newssvr19.news.prodigy.com>... SUPER KOOL 223 wrote: Much easier to use as well, in terms of clear motivation and having a clear idea of the task, or process, at least. Wouldn't it be faster, instead of estimating stories, to list intentions for the day? It's what it all boils down to anyway--I intend to finish this by 5--it makes it very clear in your mind. That's what you tell them in an actual conversation. Estimation and assessment of stories seems unengaged by comparison. Estimating stories is such a pain--just ask me what I intend to do, and measure if I get what I intended to do to figure velocity. This is probably already in the wiki somewhere. Review the Customer and Developer Bills of Rights. The Developer has the right to estimate, and the Customer the right to prioritize. This means each has the right to know what the other decided. Our token of that right - like a unit of currency - is the user story card. That conducts intent.

What a slow process you describe. This is XP? Real-time software
processes are BS. Mgmt needs to be working with a backlog, the rest
is faked and sold to the customer for profits extracted, which is one
thing mgmt knows how to do...

[Phlip]

> What a slow process you describe. This is XP? Real-time software processes are BS. Mgmt needs to be working with a backlog, the rest is faked and sold to the customer for profits extracted, which is one thing mgmt knows how to do...

Of course! Executives are perfectly free to sell things the programmers have
not written yet, then scream and scream at the programmers to work all
night. That technique does, indeed, get the executives more money, faster,
than all that "take the time to do it right" baloney.

--
Phlip

[Code Like Hell]

"Phlip" <phlip_cpp@yahoo.com> wrote in message news:<XtbUa.4585$m25.4540@newssvr17.news.prodigy.com>... What a slow process you describe. This is XP? Real-time software processes are BS. Mgmt needs to be working with a backlog, the rest is faked and sold to the customer for profits extracted, which is one thing mgmt knows how to do... Of course! Executives are perfectly free to sell things the programmers have not written yet, then scream and scream at the programmers to work all night. That technique does, indeed, get the executives more money, faster, than all that "take the time to do it right" baloney.

ok I agree. XP comes as close as you can safely get to a normal conversation.