Geek Answers Handbook

How is TFS 2010 used by Microsoft for scrambling?

We are a Microsoft store, so using other incompatible tools for Scrum does not make much sense. So, we use TFS - for Scrum.

However, we found the TFS templates quite simplistic. There is no way that MSFT can release the next Visual Studio or the next .Net infrastructure by doing all the planning using TFS tasks.

What is hiding Microsoft from the rest of the world? Alternatively, how do you use TFS 2010 to fight in enterprise (= huge) software?

EDIT: In particular, trying to figure out how the different parts fit together can be difficult. Imagine the following epic (as if it were developed in .Net 5.0 and not executed in .net 3.5): We want to implement the LINQ library. Now let's take a look at this task ... before they can do this, they must carefully identify all the stories in the DETAIL , and only then try to bring them together. However, the number of use cases is huge and the interaction between different parts of the system. Without a lot of Wiki pages, a lot of Word documents, a combination of the two, and maybe something else, I don’t see how they can track things.

+4
source share
3 answers

The old TeamsWitTools blog has 9 columns on how dev-div uses TFS. The first post in the series talks about breaking down epics. This is probably a good place to start.

+1
source

I do not know about TFS 2010, but I know that TFS 2008 has some important features for Scrum.

After properly configured, TFS automatically launches many tasks for huge projects that Scrum was created to manage very productively. Some of these tasks are to compile the assembly at the scheduled time. In the case of Scrum, I would say after each Sprint, after which the obligations of the Team were fulfilled. “Finish” is a very important word in Scrum, which means that nothing remains here. So, think about it, as all kinds of testing, test automation, etc. Your code works, is 150% sure, without errors. In any case, TFS can report failed tests and determine who this task was assigned to (Team, not individually).

After I looked at the @Shiraz Bhaiji link, I think FS 2010 got everything you need with Scrum. You have a Burndown chart, the purpose of which is to illustrate the remaining work during the whole time, you got a speed chart, which gives significant information about the speed of the team to work together. Keep in mind that team speed should increase with time when the team works together.

I don’t see a problem using TFS2010 at all and I configure it to work with Scrum, as it can track the backlog of the product, and should also allow you to write Team Sprint Backlog. In fact, now, with the advent of VS2010, PSD certification, which is a Professional Scrum Developer certification.

Microsoft development tools (TFS and VS) are compatible with Scrum.

0
source

More articles:


All Articles