Communiquez avec les autres et partagez vos connaissances professionnelles

Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.

Suivre

Do you think 2 weeks sprint is enough time in your project or you do you think you need more time ?

user-image
Question ajoutée par mohamed khiry , Senior Database Administrator , confidential
Date de publication: 2016/12/20
Bassel Yousef Alhussein Alhussein
par Bassel Yousef Alhussein Alhussein , Senior Web Developer , Thiqah

Two weeks is a good average period for a sprint, so that you can keep aligned to the plan and manage any latency and changes smoothly. It's more recommended to shorten it more if possible(One week for example).

Dheeraj Ahuja
par Dheeraj Ahuja , IT Delivery Manager , Ola Money

ideal time for sprint is 2-4 weeks. 2 weeks sprint is fine when your epics and features to be delivered are big enoough to be fit in 2 weeks during. When if your features are complext enough and a good fit be delivered at once, you can increase your sprint time to 4 weeks. It all depends what kind of feature you are delivering in your sprint.

Gaurav Talreja
par Gaurav Talreja , Associate Tech Specialist , Tech Mahindra

Two week time is good average time for a sprint but it also depends on the project requirement and backlogs. So Scrum master will plan accordingly

KIRITKUMAR SHANKERLAL  PATEL
par KIRITKUMAR SHANKERLAL PATEL , GENERAL MANAGER , SHETH CONSTRUCTION COMPANY

No, Be in touch in every Moment

Mayur Kumshi
par Mayur Kumshi , Project Lead and Scrum Master , Bitwise

Well, It depends on project to project and  how much development work has been completed, as in our projects, once the development is finalized only then we receive the proceed ahead message from our managers and we start with testing. The ideal duration of the sprint should be4 weeks but not more than that.

Sheeraz Junejo
par Sheeraz Junejo , Enterprise Architect , TEMENOS UK LTD

It depends on your requirements. Simply keep the fundamental reason for using AGILE development model "Faster Feedback" and adjust accordingly.

Christophe Tarayre
par Christophe Tarayre

 

"Scrum employs an iterative and incremental approach to optimize predictability and control risk."

The sprint duration depends of diverse constraints (business need, customer need, possibility to deliver a piece of working software). Nevertheless must not exceed one month.

But you can say that higher is the risk shorter is sprint to get predictability.

It is a compromise between with the possibility to deliver value and control the risk.

Harvey Kertland
par Harvey Kertland , Senior IT Project Manager , Air Liquide

This is a broad question: It depends on the team and the project. Two weeks is average and a default value, but some teams would be better aligned around a one-week Sprint (unusual though due to the high overhead it brings), others three weeks - for big projects.

Sejal Thanki
par Sejal Thanki , Software Developer , Crystal Martin International LTD

2-Week-long Sprints are most common for IT and software product development but shouldn't be longer than 4 weeks. Anything less than 2 weeks will not allow enough time to work accurately or efficiently. Anything more will not be SCRUM as its just way too long for sprint.

Zainab Khan
par Zainab Khan , Software Test Engineer , Infosys Technologies Limited

Depends on factors -  Cross functional team members , Correct Planning (that  divide bigger chunks into achievable deliverables ) .. That leads to deliver successful sprint . Sprint is binary 0 or 1 so  key is planning decision making and work together to achieve best results . TWO WEEKS is ENOUGH 

ahmed mohammed
par ahmed mohammed , Bi Solution Architect /Delivery manager , Melton City Council

Two weeks is a recommended time for a sprint provided the deliverables are delivered, else the sprint time can be extended or minimised  

More Questions Like This

Avez-vous besoin d'aide pour créer un CV ayant les mots-clés recherchés par les employeurs?