http://kanemar.com/2006/10/07/allowing-time-for-testing/ Adventures in Agile Software Development and Scrum Thu, 19 Apr 2012 09:24:37 +0000 hourly 1 http://wordpress.com/ http://kanemar.com/2006/10/07/allowing-time-for-testing/#comment-6746 Sun, 18 Mar 2007 13:50:39 +0000 http://kanemar.wordpress.com/2006/10/07/allowing-time-for-testing/#comment-6746 We’ve been considering a 3 + 1 schema for one iteration. 3 weeks of development with full focus on stories and tasks and one week of stabilizing, with intensive testing (by team members and QA testers) and fixing. This way we can keep the monthly rhythm and should be able to reach a higher quality level. The team which develops the Eclipse IDE is obviously working like that. What do you think of this?

]]> http://kanemar.com/2006/10/07/allowing-time-for-testing/#comment-1096 Mon, 09 Oct 2006 20:58:37 +0000 http://kanemar.wordpress.com/2006/10/07/allowing-time-for-testing/#comment-1096 [...] Kane Mar wrote recently about the difficulty teams have adjusting to finishing within an iteration: Typically what this means is that the software will be code complete at the end of an iteration, but will not have been fully tested. A comment that was frequently heard during the early retrospectives was that code was delivered late to the testers; usually just a day or two before the end of the iteration. [...]

]]>