Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
i have found a queue build option in Team Founder .. so whats the exact purpose of queue build? we are able to build in vs itself...so just need clarification
You can build projects directly from visual studio, from a command prompt using msbuild - what TFS gives you (in brief) is the ability to set up continious integration, so a build is automatically initiated when a member of the team checks in - and you can hook in mail to notify team members if they broke the build. You can also manage work items, sprints, etc. Well worth the effort in my opinion.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I want to move my TFS 2008 to Visual studio Team Services. Could you please tell me how to do that ? I saw few articles on this but it looks complicated to follow those steps.
Since TFS 2008 (and indeed 2010) is no longer supported you Will likely find it difficult to find documentation. There are two tools to help you. One from OpsHub that can migrate you to Team Services and the other from the product team called TFS Integration Tools.
You should follow the ALM Rangers migration guide if you can, and use the OpsHub tool if you can't.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I get this error when I attempt to add a new project to Source control after a fresh installation... It seems when I am not installing VS2010 I do not get this..
Can anyone help ? I suppose I need permissions.. but WHO needs permission to what exactly ?
TF206018: The items could not be added to source control because either no team projects have been set up, or because you do not have permission to access any of the team projects in the current collection.
Sorry.. I am a dummy.. A COLLLECTION.. needs a TEAM PROJECT and THEN you add the project to source control.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
We're using TFS Work Items to manage our bugs and work items.
Would that be possible to use TFS for agile scrum project management? e.g. defining user stores, drawing burn down chart and cumulative chart, etc?
How?
Thanks
Absolutely yes.
Generate a new Team Project choosing the default process template (MSF for Agile Software Development 5.0) during the Wizard execution.
Now within this new Team Project a great deal of ready-baked reports is available, 'agile' work-item type User Story as well. Out-of-the-box sprint planning is also quite nicely delivered.
With a small time-investment for orientation, customizing & tailoring to your own needs should be possible.
A very comprehensive presentation by A.Bjork was really helpful for me.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I'm thinking of giving each part of the agile lifecycle its own project (TFS project, not csproj) as per Microsoft's agile template.
Is it possible to move items (like User Stories or Tasks) from one Project to another?
Does the organization of these projects have any bearing on or affect the actual software build (solutions, csproj, etc)?
What is the recommended organizational structure of Projects, etc for an agile project?
Are there any guides you can recommend for setting TFS up to work with the standard agile process?
Do not set up multiple TFS projects for the same team/product line. You can't move things from one to another and they won't be able to share a common parent source control so you would miss out on much of what source control has to offer. Do some research by reading the links on the other answers.
I have never heard such a strange idea.
You should have one team project for each endeavor. Basically, a team project is the intersection of a team with a project.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Does it make sense to use the project management features of Team Foundation Server without using the Source Control and Automatic Build features? We're doing agile in an non-.net environment and would use TFS to manage the project but keep using the currently used source control and build software.
Thanks in advance,
One of TFS' primary strengths is that the work item tracking and source control are so closely linked. Another of its primary strengths is the integration into the Visual Studio IDE. It sounds like you wouldn't be using either of those features, so that starts to drive you away from using TFS as a solution.
Another factor that is an unknown here is how much you would need to pay for TFS licensing. If you already have that covered under existing MSDN licenses, then it probably isn't a factor.
That being said, the agile process template in TFS 2010 is a very nice agile-in-a-box solution, giving you the work items and management reports that you need to work in an agile environment. Additionally, you can modify the process template as needed to meet your particular flavor of agile.