Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion best approach for defects
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dan Rawsthorne  
View profile  
 More options Aug 23 2012, 12:30 pm
From: Dan Rawsthorne <dan.rawstho...@drdansplace.com>
Date: Thu, 23 Aug 2012 09:30:17 -0700
Local: Thurs, Aug 23 2012 12:30 pm
Subject: Re: [Scrum] best approach for defects

So, then, you're not using the Backlog to manage your work, just order
the business priorities?

Dan Rawsthorne, PhD, PMP, CST
3Back.com <http://www.3Back.com>
Author of /Exploring Scrum: the Fundamentals/
<http://www.amazon.com/dp/1461160286>
On 8/23/2012 5:09 AM, Ernesto R. Corona (BHP) wrote:

> Sam,

> From our experience, I would recommend not to write stories for each
> defect. We only use stories when defects are "legacy" (when they comes
> from previous phases, before agile was in place for the team), or when
> they have strong impact on traceability to several components or
> functionality.

> Sometimes (most of them) we fix ASAP when they appear, and after
> several sprints we agree with the product owner to have a bug fixing
> sprint.

> Obviously that's what we do, not what you have to do.
> --
> Ernesto

> On Thu, Aug 23, 2012 at 8:32 AM, Joshua Partogi
> <joshua.part...@gmail.com <mailto:joshua.part...@gmail.com>> wrote:

>     Put it on the Sprint Backlog and fix it right away.

>     On Thursday, August 23, 2012, Sam Dsoca <samds...@gmail.com
>     <mailto:samds...@gmail.com>> wrote:
>     > Hi,

>     > What would be the best approach for working on bugs and defects,
>     > Is is good to rewrite write them as new stories with high
>     priority or
>     > just allocate some time during the iteration for defect fixing
>     work ?

>     > Regards

>     > --
>     > You received this message because you are subscribed to the
>     Google Groups "Scrum Alliance - transforming the world of work."
>     group.
>     > To post to this group, send email to
>     scrumalliance@googlegroups.com
>     <mailto:scrumalliance@googlegroups.com>.
>     > To unsubscribe from this group, send email to
>     scrumalliance+unsubscribe@googlegroups.com
>     <mailto:scrumalliance%2Bunsubscribe@googlegroups.com>.
>     > For more options, visit this group at
>     http://groups.google.com/group/scrumalliance?hl=en.

>     --
>     @jpartogi

>     --
>     You received this message because you are subscribed to the Google
>     Groups "Scrum Alliance - transforming the world of work." group.
>     To post to this group, send email to
>     scrumalliance@googlegroups.com
>     <mailto:scrumalliance@googlegroups.com>.
>     To unsubscribe from this group, send email to
>     scrumalliance+unsubscribe@googlegroups.com
>     <mailto:scrumalliance%2Bunsubscribe@googlegroups.com>.
>     For more options, visit this group at
>     http://groups.google.com/group/scrumalliance?hl=en.

> --
> You received this message because you are subscribed to the Google
> Groups "Scrum Alliance - transforming the world of work." group.
> To post to this group, send email to scrumalliance@googlegroups.com.
> To unsubscribe from this group, send email to
> scrumalliance+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/scrumalliance?hl=en.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.