We have been using TFS for a number of years and I still struggle to get a handle on the progress (e.g. burndown) of an Epic.
The Epic spans multiple team backlogs.
We use the Scrum template and are on TFS 2017 on-premises version.
Any suggestions will be appreciated.
Thanks
Install this Feature timeline and Epic Roadmap to your TFS.
FeaturTimelinene
UserStories chart
Extending your feature sprint
Related
My TFS version is 2013.4 and I need EPIC workitem type in the Scrum 2013.4 process template.
I was trying to follow the instructions here but EPIC.XML is not found in the process template. Can anyone please let me know will I be able to make the following changes to get the EPICS? Where should I download the EPIC.XML file to import it?
https://blogs.msdn.microsoft.com/tfssetup/2015/09/16/configuring-the-epics-for-upgraded-team-projects-in-team-foundation-server-tfs-2015/
TFS 2013 did not have an epic work item type. Upgrade to a modern version of TFS.
Although you may be able to backport the work item type into prior versions of TFS, you won't have any of the additional features that were released in TFS 2015 around backlog management.
I have a requirement of moving Team projects between two team project collections in TFS 2015. Also need the History & Label to be moved to the new collection.
I am aware there is no direct way of moving the project between collection along with history & label.
Can someone suggest a better way to handle it?
Thanks in Advance,
Dinesh
There is already a UserVoice for this request, and this feature is under plan:
We are committed to allow you to move team projects between
collections, although it’s currently not in scope for the 2016
calendar year. We’ll provide an updated timeline as we get closer to
2017.
An alternative, you can try with 3rd tools to move team projects, such as TFS Integration Tools, OpsHub. Please read the limitations before using the tools.
I noticed that I can change the order of the PBIs of the current sprint on visualstudio.com via Drag&Drop. At work we use TFS 2013 on our own server (I think the newest version Update 4) and that's not possible. Both use the SCRUM template.
Is this a configuration issue? It would help a lot if this would work at our own TFS too. What should I do?
The features available in VSO are beyond that of TFS 2013 update 4. The feature that you are referring to is planned for TFS 2015.
https://www.visualstudio.com/en-gb/news/release-archive-vso
For most customers, regardless of size, I recommend moving to VSO to get access to the latest and greatest features as they become available.
I would like to modify the Burndown chart in TFS 2012's Scrum 2.0 Template so that weekends no longer show. I've already looked at this article, but unfortunately the solution listed there doesn't apply to the Burndown Chart when running from Board View.
Does anyone have a suggestion for how I can modify it in Board View?
UPDATE: The burndown excludes the weekends on Visual Studio Online. Later this year, this feature ships with TFS 2013 Update 2 for on-prem customers.
See the announcement at http://www.visualstudio.com/news/2014-jan-22-vso.
If you want to configure the working days of your team, you can click on the gear button in the top right corner which will open the admin area in a new tab. Click on your team, and choose the “settings” tab.
The TFS team on uservoice explained recently that they started working on this feature request Burndown chart should exclude non-work days.
My team and internal business customers often ask the start/end dates for sprints and the projected release date. Is there a way to attach a note to an iteration in TFS so that these dates can be published and/or queried?
Take a look at the following links which describe how to set start and end dates to your sprints and be able to track these dates. Also, check out the new Microsoft Visual Studio Scrum 1.0 process templates. It may have the ability to add notes or more information to your iterations since it has a sprint work item type. TFS 2012 has the type of functionality you mentioned as well.
Make Agile Work for You in TFS 2010
Microsoft Visual Studio Scrum 1.0