Bryan Hinton

One of the gaps that I have been communicating over the last couple of years is the desire to have Iterations as first-class citizens. I want to be able to have iteration objects that have fields (like start date and end date or velocity) or perhaps custom iterations that are actually Release Iteration objects that contain child Iteration Iteration objects. Any plans in this area to make Iterations first class citizens (similar to how it sounds like links are now first class citizens being that you can create new customized link types)



Re: Visual Studio Team System Code Name "Rosario" Work with Iterations and making them first-class citizens in TFS

Siddharth Bhatia MSFT

Hi Bryan,

I hear you and I agree that it is a gap. Iterations as first-class citizens is something we're certainly thinking about but we're not sure what we'll be able to do for it in Rosario.

Can you tell me more about how you would plan on using Iterations that have start date and end date fields As well, can you tell me more about the idea of custom iterations that are Release Iterations and how the child Iteration object would fit in

Thanks,

-Siddharth





Re: Visual Studio Team System Code Name "Rosario" Work with Iterations and making them first-class citizens in TFS

Bryan Hinton

Well Iterations by almost everyone's definition are time boxes and so there are a whole slew of reports out there (including most of today's out of the box reports in TFS2005) that have to have a date hard-coded in them to reflect say the Remaining Work report for a given Iteration. With Iterations as first class objects I could bind the report parameters to those reports to the current iteration (by doing a query that "discovers" the current Iteration or Release by comparing current time to the defined length of each Iteration.

Going further on custom iteration objects - with the control over them you could add fields that predefine the length of them (to auto create them etc... as the project rolls forward) or the size (in terms of features) which could be used in planning (both manually and in planning tools). In general in terms of reporting and planning it would be an incredibly powerful lever.

As far as Release Iterations versus standard iterations we do and I would imagine others do as well - nest Iterations to reflect those relationships (1.4 release with child objects reflecting the actual iterations that manage accomplishing work). There are different types of reporting and planning that happen for those different types of Iterations (like generating a report that takes the current release iteration and publishes to stakeholders the release status versus a report that looks at the current iteration report that is used by the development team as a status board in standup etc...)





Re: Visual Studio Team System Code Name "Rosario" Work with Iterations and making them first-class citizens in TFS

Siddharth Bhatia MSFT

Thanks Bryan. Excellent input.