Jesus MartheynProject Manager SR Lvl 2| GlobantMedellin, Antioquia, Colombia
Hi all,
I'm just asking what's the time stablished on the projects that you work or you have worked for sprints on agile projects? Saving Changes...
Sort By:
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Currently, have a fixed-cost, fixed-deadline project whereas we are utilizing a hybrid approach with 4-week sprints. This is probably not a great example :)
In the past, have used capacity-based planning to determine the number of sprints until completion. This worked out pretty well. And TBH, that was more or less hybrid as well. Saving Changes...
It "depends". 2 weeks is the typical, longer than 4 weeks is not typical, 1 week for products that need to release/improve/replace a lot of small features all the time (ie. Amazon).
...
1 reply by Jesus Martheyn
Aug 19, 2018 6:06 PM
Jesus Martheyn
...
I agree, we use two weeks sprints, I guess is a nice time to manage and react when things go wrong.
Saving Changes...
Jesus MartheynProject Manager SR Lvl 2| GlobantMedellin, Antioquia, Colombia
Aug 19, 2018 5:51 PM
Replying to Sante Delle-Vergini, PhD
...
It "depends". 2 weeks is the typical, longer than 4 weeks is not typical, 1 week for products that need to release/improve/replace a lot of small features all the time (ie. Amazon).
I agree, we use two weeks sprints, I guess is a nice time to manage and react when things go wrong. Saving Changes...
Deepa KalangiManager, Program Management, Author, Trainer| CVS HealthCharlotte, NC, United States
I have worked in companies where the sprint cycles are 2, 3 and monthly cadences. Guess depends on the domain, business area and the organizations in terms of deciding sprint cycles. Two week sprints seem to be ideal though. Saving Changes...
I've done 2,3,4 weeks. 2 weeks was the worst as it didnt give us enough time in the sprint to actually do our work. 3 weeks was ideal as it was a nice balance between productive time and eyes on the long term/short term goals. Saving Changes...
Scott Ambler of the Disciplined Agile Consortium had done a broad survey a few years back and found 2 weeks was the most common sprint duration followed by 3 weeks. However, as Emily indicates, you really need to profile the project context and team maturity when picking a sprint duration - 2 weeks might be too aggressive to deliver anything of value for some teams and might seem like an eternity for others.
Of course, you could also follow a lean, continuous flow approach as encouraged by Modern Agile and do away with sprints entirely...
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Just to add something to Kiron comment we worked with Scott Ambler in my actual work place as a way to facilitate the mindset to implementa Agile. We use 2-4 weeks and we decide it based on a checklist. But let me say: the worst thing you can do is to use a receipt. You have to start with a duration and then you have to calibrate taking into account environmental factors. Envisonmental factors are the key to decide about sprint. Saving Changes...
