Am 12.10.2009 16:14, schrieb Scott:
I think fixing these bugs can be planned, just like a user story.I would think that you would want to size those bugs in order to add them to the next development sprint. Otherwise, your velocity would get skewed because you would be spending time on things not accounted for in the sprint.
That's exactly the point - you're spending time on stuff which does not add real value from a PO point of view. If the team produces many bugs, they can not deliver that many new features. So your low velocity just shows the bad quality.
Do not hide bad quality by giving user story points for bugs (unless you actually *plan* to produce bugs on purpose).
Just curious, how are you planning on incorporating bug #907 into your
> next development sprint?We have a list of bugs+features and we will pull in as much as we think we can possibly do.
fs
smime.p7s
Description: S/MIME Cryptographic Signature
