Usage Poll: Do you work in iterations/sprints that aren't whole numbers of weeks?

Hello Dave,

we have several different approaches in our Division. The division spans about 1500 RTC user, in about 50 RTC Project areas.

- Most used approach: 4 weeks, but startday must not be Monday. Very often it is Tuesday or Wednesday, so on last Monday or Tuesday in the sprint, the projects are doing the Sprint Demo and Retrospective. Monday is a quite bad day to start an Iteration from our experiance.

- Another approach is: one calendar month, regardless of the days and when they start. This has big advantages because the management rhytm of an organisation is monthly based. So specially in larger projects where you have some sort of a hybrid process, this gives lesser effort in harmonizing e.g. reporting, resource allocation, cost accounting etc..

- Smaller projects with one or just a few teams are using sometime three weeks sprints. Again start is seldom on Monday.

- Very seldom we ahve projects wioth an odd number of days. e.g. 29 days or so. We try to limit to the three approaches above.

- One important thing, end of sprint should be midnight of the last day in RTC. today, when you create an iteration, you get 12:00AM as end hours. But then you miss 8h of the last day in your capacity. For this I wrote an enhancement request, to have 11:59PM as default for end time. But it's still on backlog.