Timeline for Code Reviews do they really work in true Agile?
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2016 at 20:56 | history | protected | gnat | ||
| May 20, 2011 at 14:25 | vote | accept | user25702 | ||
| May 20, 2011 at 13:27 | comment | added | Berin Loritsch | If you want to argue code reviews away, then I recommend taking some stats. Document the time taken for the code reviews (in total man hours), the number of bugs/issues discovered in them, along with the severity of the problem. For my team it turned out we spent at least 16 man hours per review, found on average 2-3 bugs, all of which were cosmetic in nature. It was easy to argue for test-first methodology to replace peer reviews in the face of those numbers. | |
| May 20, 2011 at 13:23 | comment | added | Berin Loritsch | Some PMs think that iterations mean we have a couple short iterations in the beginning and a couple long iterations in the middle followed by as many short iterations at the end as needed. The problem is that this messes with the battle rhythm of software development and the ability to catch bugs early. The 8 week iteration would be one of those middle iterations. I do agree that this is not agile. | |
| May 20, 2011 at 7:14 | comment | added | Martin Wickman | 8 week iterations is not agile and definitely not "extreme agile". | |
| May 19, 2011 at 22:26 | answer | added | mmeyer | timeline score: 1 | |
| May 19, 2011 at 21:24 | comment | added | Steven A. Lowe | @user25702: the process you describe does not sound like Agile, it sounds like RUP/spiral. Specifically "Several times during the weeks of our development we hold sesssions with the stakeholders again to see if they still agree features/functions/UX/UI are still a fit and on target." is anti-agile; features are frozen during an iteration to avoid the moving-target problems associated with RUP/spiral approaches. As to your nominal question, I don't see much value in code reviews here if and only if you are certain the bugs would have been found by QA. | |
| May 19, 2011 at 21:06 | comment | added | Steven A. Lowe | @DeadMG: User Experience | |
| May 19, 2011 at 20:56 | answer | added | David Thornley | timeline score: 7 | |
| May 19, 2011 at 20:45 | answer | added | BillThor | timeline score: 0 | |
| May 19, 2011 at 20:43 | answer | added | Berin Loritsch | timeline score: 13 | |
| May 19, 2011 at 20:37 | answer | added | pdr | timeline score: 3 | |
| May 19, 2011 at 20:27 | answer | added | JB King | timeline score: 13 | |
| May 19, 2011 at 20:25 | answer | added | Dave | timeline score: 4 | |
| May 19, 2011 at 20:19 | history | asked | user25702 | CC BY-SA 3.0 |