Hi Georges, Yes, I got lots of bouncing from dev to tester... About counting bugs,Yes addressing bugs before the end of the sprint will not help the team and...
52286
Dan Rawsthorne
drawstho
Aug 27, 2011 8:19 am
When you say that the tester finds a bug in the PBI there are two cases: 1. The tester finds that the PBI does not meet its acceptance criteria, which must be...
52287
avi_a@...
avinap77
Aug 27, 2011 8:37 am
Thanks Ron for the feedback. I agree that the best way to deal with technical debt is not to have it in the first place, but sometimes it's unavoidable - it...
52288
avi_a@...
avinap77
Aug 27, 2011 9:03 am
Hi Samer. I understand your working with TFS, so I'm not sure how my advice would fit in, but nevertheless... Try Approach 3 - not bouncing in the first place:...
52289
RonJeffries
ronaldejeffries
Aug 27, 2011 11:23 am
Hello Samer, ... Right. And why should you record that? What matters is how many features your team produces. Ron Jeffries www.XProgramming.com I try to Zen...
52290
Samer
samerghosn
Aug 27, 2011 11:58 am
Hi Ron, I need to have an idea how much my developers are producing bugs within the sprint, as I have told Alan: I am trying to find a way to measure the bugs...
52291
RonJeffries
ronaldejeffries
Aug 27, 2011 1:51 pm
Hi Samer, ... You keep saying that you need it. You seem to want to monitor and control "your" developers. The Scrum way is for your developers to monitor and...
52292
Joshua Partogi
thejavafreak
Aug 27, 2011 3:03 pm
Hi all, I am just wondering here. In your Scrum team, who produces the bundown chart? The team or the Scrum Master? I'm interested to know why does that role...
52293
Alan Dayley
alandond
Aug 27, 2011 3:07 pm
I understand the need to find ways to measure improvement. A word of caution: If you track bugs, as in count them as a negative measure, the count will go down...
52294
Alan Dayley
alandond
Aug 27, 2011 3:13 pm
Someone on the Scrum Team updates the chart every day. In my experience and observation, usually it is the ScrumMaster that makes the next dot and draws the...
52295
George Dinwiddie
gdinwiddie
Aug 27, 2011 4:18 pm
Samer, ... I fear that you don't get the point of collaborative software development at all. - George -- ... * George Dinwiddie *...
52296
Steve Ropa
steveropa
Aug 27, 2011 4:43 pm
Sorry for the top post, still haven't figured out how to get Touchdown to do otherwise... I recognize and support that the team is the best entity to decide if...
52297
Michael James
michaeljames...
Aug 27, 2011 4:51 pm
... I noticed you wrote "developer" where I would have expected "developers." Is just one developer working on each thing? This doesn't sound like the kind...
52298
Michael James
michaeljames...
Aug 27, 2011 5:08 pm
... An example of this mental gymnastics is the oxymoronic phrase "technical user story." Which is it? If it's a USER story, why is it too "technical" for...
52299
Samer
samerghosn
Aug 27, 2011 5:38 pm
Hi, Each developer for 1 task but more than 1 developer in the team. Once you have the number of bugs produced during a sprint you can tell what caused the...
52300
flavius.stef
flavius_stef
Aug 27, 2011 6:04 pm
Hi, Are you more concerned with product quality or with estimation accuracy? This micromanagement technique of bug counting during sprints sounds like a tool...
52301
avi_a@...
avinap77
Aug 27, 2011 8:20 pm
... Agreed. I also mentioned using a story as just one of three options, and there are probably many more. The point is to communicate the need, the cost and...
52302
avi_a@...
avinap77
Aug 27, 2011 9:09 pm
I'm not sure where "technical user story" came in.... lol Looking back at what I wrote in reply to Ron, I realize that the term "technical debt" may be...
52303
Laurent Bossavit
morendilfoo
Aug 27, 2011 9:38 pm
... That doesn't mean you don't use that many... (And I'm pretty sure if you did put some time into it you'd be able to come up with at least 50.) ... I think...
52304
Gary Brown
gb70840
Aug 27, 2011 10:09 pm
Hello, Ron! ... In my experience, not all developers immediately embrace the freedom to do their best that an Agile method provides. Perhaps if Samer can show...
52305
extremeprogrammer
extremeprogr...
Aug 28, 2011 3:35 pm
52306
Dan Rawsthorne
drawstho
Aug 28, 2011 3:40 pm
Ron has it right here, but probably doesn't go far enough. One of the issues in this thread has been how to manage these 'bugs' "in the tool." Don't do that,...
52307
Dan Rawsthorne
drawstho
Aug 28, 2011 3:43 pm
As with almost everything else, the Team produces the burndown chart (if you have one). The Team is responsible for everything. It is a self-organization issue...
52308
Silvana Wasitova
wasitova
Aug 29, 2011 1:06 pm
Hi Josh, Dan +1 In good teams, the team members do it - anybody. In so-so teams, the SM. In new teams, the Coach :)...
52309
Joshua Partogi
thejavafreak
Aug 29, 2011 1:09 pm
Thanks everyone. I thought it is the Scrum Master responsibility as part of his/her service to the team. :-) ... -- @jpartogi...
52310
David A Barrett
barrettdab
Aug 29, 2011 2:54 pm
... Samer, There's definitely something missing here. The concept of a "bug" during development doesn't make any sense at all. All that it means is that the...
52311
Ash Gupta
traderashish
Aug 29, 2011 3:44 pm
Creating Burn down is something a tool can do easily for you, why have Team members spent time on it. Take a look at AgileWrap, Agile Project Management Tool -...
52312
Alan Dayley
alandond
Aug 29, 2011 3:54 pm
Why have team members do it? Because holding a marker and drawing a line segment is an extremely easy way to make the the information in the line tangible,...
52313
leeann.berner
Aug 29, 2011 8:52 pm
Join software professionals around the world that are taking part in the Annual State of Agile Development Survey: www.AgileDevSurvey.com ...
52314
Charles Bradley - Scr...
charles_brad...
Aug 29, 2011 9:19 pm
Well said David. Samer, While your desire to make things more transparent so that your team can inspect and adapt is laudible and respectable, the way in...
