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.
Related
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
One of the key differences between the MSF for Agile template and the Visual Studio Scrum template is that Scrum
manages bugs along with product backlog items during sprint planning
http://msdn.microsoft.com/en-us/library/vstudio/ms400752(v=vs.110).aspx
The Scrum approach makes sense to me. Fixing a bug involves planned work and creates some sort of benefit for end users.
Why are bugs not managed as backlog items using the agile template?
Is the team expected to just absorb time spend fixing bugs?
Is the template assuming another resource will attend to bugs outside of the project scope?
The expected workflow in the Agile template, is that a Bug WI will be created, then a linked User Story to represent the work to fix that bug. The User Story is what goes on the backlog and is prioritized.
If you inspect the Bug WITD XML you will see that in the transition from Active to Resolved one of the Reasons is "Copied To Backlog", this is meant to indicate a related User Story was created.
It's really awkward, but that's how the template was originally designed for whatever reason.
Because the Agile template is not intended to support Agile work. It is an agile implementation of the Microsoft Solution Framework (MSF) designed by Microsoft Consulting Services (MCS) for working with client engagements.
The only template that supports an agile workflow out of the box is the Scrum template.
http://nakedalm.com/agile-vs-scrum-process-templates-team-foundation-server/
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
I'm currently using Jira Agile for managing my projects.Currently, I have 3 projects: A,B and C. Is there any way to create a Sprint with task from different projects. For example, this week should work on bug fixing so it might be expectable to have 2 bugs from project A, 3 bugs from project B and 2 from project C. How can I accomplish this?
I agree with mdoar, you simply need filters.
I'd create new Issue Type, let's say "Bug_fix_sprint" which is common for all projects, then open tickets with that type in each project, then I'd use Issue Type Filter to add them on dashboard. Or, maybe, I'd create a new dashboard for this sprint
The filter for your board needs to be changed to include the issues you want from all three projects
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 am currently working on a project where - while coding - there are some wishes about the layout (changing font color, changing the texts etc.)
What would be the best category in tfs?
bug, feature, issue or task?
I've read that: What are the differences among bugs, issues and tasks in TFS
But this did not help me on that question
To me, this would be either a Bug or a Feature.
It is a bug if it was supposed to be that way, and was not done.
It is a feature if it is a new idea/change.
After you create the bug/feature, you will add tasks to it as children. Those tasks should be the low level things needed for the overall feature to be done.
(By the way, if you are doing scrum, "features" are usually called Product Backlog Items. But both Bugs and Product Backlog Items go on the Product Backlog.)
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.