We are going with a change of the “greats” in regard to Visual Studio 11 and Team Foundation 11. Let’s see, one of the things you always calling people from Redmond was the concept of iteration was a little “more complete”. Until the version of Team Foundation Server 2010, an iteration was simply a text that could interact with each other in tree format. In my experience, I always ended up changing the tree by default that is created with a Team Project:
- Iteration 1
- Iteration 2
- Iteration 3
By something “more useful” according to my experience:
- 2011 04 01 – POC
- 2011 04 15 – First deploy
- 2011 05 01 – Salsa Time
In other words, the least that you asked one iteration was that could have associated metadata, for example date start and end date.
When Visual Studio 11, access to the Team Explorer panel and let’s edit the iterations of a Team Project,
the first thing we will see is that the edition of iterations from the new Team System Web Access, i.e. NO ES MAS responsibility VISUAL STUDIO the maintenance of this information. This is a big change, because we see that he has not invested in creating interfaces from the IDE, but now many of the options of security, configuration, deploy, etc.; they will be made from Web Access.
But back to iterations. In the configuration we will see that we have already Start Date and End Date as properties of the same.
So now we can edit them and configure them more closely to our project.
With a bit of time and desire, iterations are already configured in the following way
(eye! (this is just one example, no do iterations glued as railway carriages, iteration and iteration must take time to see the Champions, do retrospectives, etc.).
We can also create childs from here and from the IDE, configure security and what we are accustomed to working with iterations.
Greetings @ Home