Comments on: Sprint, Jog, Sprint http://www.onesandthrees.com/2009/04/sprint-jog-sprint/ ... blogging about coding, music and who knows what else ... Fri, 30 Jul 2010 15:31:56 +0000 http://wordpress.org/?v=2.6 By: Twitter Trackbacks for Ones and Threes » Blog Archive » Sprint, Jog, Sprint [onesandthrees.com] on Topsy.com http://www.onesandthrees.com/2009/04/sprint-jog-sprint/#comment-115 Twitter Trackbacks for Ones and Threes » Blog Archive » Sprint, Jog, Sprint [onesandthrees.com] on Topsy.com Sat, 29 Aug 2009 08:56:51 +0000 http://www.onesandthrees.com/?p=68#comment-115 [...] Ones and Threes » Blog Archive » Sprint, Jog, Sprint www.onesandthrees.com/2009/04/sprint-jog-sprint – view page – cached Since starting with scrum, we’ve always done consecutive sprints. Two weeks of coding (Monday-Friday for the most part) near the end of which we do activities like estimating, planning, sprint review, retrospective. — From the page [...] [...] Ones and Threes » Blog Archive » Sprint, Jog, Sprint http://www.onesandthrees.com/2009/04/sprint-jog-sprint – view page – cached Since starting with scrum, we’ve always done consecutive sprints. Two weeks of coding (Monday-Friday for the most part) near the end of which we do activities like estimating, planning, sprint review, retrospective. — From the page [...]

]]> By: Andy http://www.onesandthrees.com/2009/04/sprint-jog-sprint/#comment-55 Andy Thu, 11 Jun 2009 12:18:31 +0000 http://www.onesandthrees.com/?p=68#comment-55 The urgent requests typically won't wait for anything like as long as a week. Actually 'ad hoc' is a better term than 'urgent' and these things fall into two categories. (1) Support requests (the team functions as dev AND 2nd line support) (2) emergencies (e.g. site is down, or a show-stopping bug has been exposed). It's all down to a single team having both an operational and a tactical focus. Even a 1 week sprint would get interrupted. We've adopted Kanban (temporarily at least) to help fully expose the issues, and once we have a solution for the issues (more devs ? separate 2nd line support team ?) then we can probably go back to sprinting. Andy The urgent requests typically won’t wait for anything like as long as a week. Actually ‘ad hoc’ is a better term than ‘urgent’ and these things fall into two categories. (1) Support requests (the team functions as dev AND 2nd line support) (2) emergencies (e.g. site is down, or a show-stopping bug has been exposed). It’s all down to a single team having both an operational and a tactical focus. Even a 1 week sprint would get interrupted.

We’ve adopted Kanban (temporarily at least) to help fully expose the issues, and once we have a solution for the issues (more devs ? separate 2nd line support team ?) then we can probably go back to sprinting.

Andy

]]> By: Siddharta http://www.onesandthrees.com/2009/04/sprint-jog-sprint/#comment-54 Siddharta Thu, 11 Jun 2009 09:44:15 +0000 http://www.onesandthrees.com/?p=68#comment-54 Andy, Why not do 1 week sprints? It looks to me thats what you are doing in practice anyway, just under a terminology of sprints and jog weeks. With 1 week sprints, you can look at the backlog every week, decide whats important at that point in time, schedule it and work on it for a week. Besides should any urgent request come through, you only have to wait a maximum of 7 days to pull it in. Andy,

Why not do 1 week sprints? It looks to me thats what you are doing in practice anyway, just under a terminology of sprints and jog weeks. With 1 week sprints, you can look at the backlog every week, decide whats important at that point in time, schedule it and work on it for a week. Besides should any urgent request come through, you only have to wait a maximum of 7 days to pull it in.

]]>