February 9, 2017 at 12:59 pm #15317@allanwilsonOnly available when logged in
I’d like to know how other software teams avoid the final push to fix bugs before a release. Approaches could be to fix defects as they arise, allocate time each sprint/dev cycle for bug fixing (for example bug Wednesdays :P).
How to avoid a development team moving from “forward energetic creative push” to “bored debugging until release date”February 10, 2017 at 11:47 am #15346@tassaweraminOnly available when logged in
Our development team also use a “Bug Fixing Day” i.e Wednesday duirng their Scrum sprint.February 10, 2017 at 4:58 pm #15357@archanaOnly available when logged in
One of my client has set a target of “x” defects to be fixed each week by each developer.March 19, 2017 at 9:43 am #15746@groza-alin88Only available when logged in
In projects I have worked a developer was allocated for bug fixing each sprint by rotation. In this way, the load related to bug fixing during the sprint was kept at a constant level and there was not such a high push before release. Another approach I have seen on projects is to fix the bugs as they arise.
AlinMarch 28, 2017 at 1:48 pm #15847@msalazar18Only available when logged in
We do what we call bug “Stand-down” once in a while before the release, in order to tackle Major and high priority bugs, fixe it and verify it. In this way the counting of bugs towards the release date most of the time remain in the target scope. For “minor” bugs it always depends on resource availability and time.
You must be logged in to reply to this topic.