agile - In Sprint methodology when should the adaptive part be done? -


in sprint, plan @ start , try follow plan next 2 weeks. see sprint teams changing things while sprint in progress.

question: when following sprint-based agile software development process, normal adaptive while sprint in progress, or any adaptive changes should occur @ end sprint these changes can incorporated next sprint?

to me seems counter-productive adaptive within sprint period, since violate fundamental principle of 'execute plan succeed'.

example

as example, let's sprint next 2 weeks has been planned 5 tasks assigned each of 4 developers in team. then, after week sprint, team lead adds task 'developer 1' , 'developer 5'.

this example of changing things i.e. being adaptive when sprint in progress. in view, should not happen since amounts changing plan set out achieve, , in end doesn't team or stakeholders.

after all, trying follow plan next 2 weeks , not next 6 months, , have full opportunity after 2 weeks change things around , adaptive.

in general, i'd depends on changes are. ideally, adaptive process apply next sprint, if changes drastically affect work being done in current sprint cycle, incorporate adaptive process current sprint. that's 1 of major advantages of methodology - can adapt without throwing off whole project. (or should be) normal? in experience, no, changing sprint plan not normal (or advised).

edit: given example in edit, typically added future sprint.


Comments

Popular posts from this blog

c# - Better 64-bit byte array hash -

webrtc - Which ICE candidate am I using and why? -

php - Zend Framework / Skeleton-Application / Composer install issue -