Microsoft team foundation server agile project management

And IвЂ™m not digging on the little colored rectangles in the Backlog to show/hide Tasks, or divide the Backlog into Features. If I had a dime for every minute IвЂ™ve spent visually scanning a screen for a particular recordвЂ¦ LetвЂ™s just say that any time you show data in a table, you should provide sorting functionality. Not being able to easily sort backlog in order to find a particular PBI is just awful. So my two big suggestions to improve it are: Sortable Table Headers andВ More Explicit Hierarchy View Toggling.

Improved Backlog views вЂ“ Basically, I find the navigation around the various necessary views of the Backlog to be unintuitive. But thatвЂ™s lame - these are pretty basic measures which should be available by default. Yes, these metrics can be derived through the Reporting page. This is starting to seem like maybe a process thing that I should initiateвЂ¦.Д«asic totals and counts вЂ“ I find it harder than necessary to get meaningful metrics like Effort Points per Sprint, or counts of PBIs per Feature, etc. I have noticed that we have spent a lot of time trying to find PBIs or clarify which PBI we are talking about. TFS provides numbers but doesnвЂ™t show them by default in the Backlog. We provided links to a given Story in an email, sometimes just mentioned the number, and all was clear. I resisted them at first but I came to realize how nice it was to have a specific shorthand for any given PBI. Use the PBI Numbers more prominently вЂ“ JIRA somewhat forces you to accept and use the item numbers it generates for Backlog stories and tasks. HereвЂ™s some steps that might improve the usability of TFS (and maybe get me to stop wanting to beat it with a hammer): Other differences, however, constitute feature and usability gaps that are pretty painful. IвЂ™m sure for anyone having gotten used to one, moving to the other will be an adjustment. I can definitely say it was a lot easier to get my hands dirty in TFS than it was to learn JIRA. TFS uses SharePoint 2013 for an online interface - which is a boon to me, as I have become a native SharePoint user over the years.

And obviously, the user interfaces are different. There are some terminology differences (вЂњPBIвЂќ = вЂњStoryвЂќ, вЂњFeatureвЂќ = вЂњEpic). The basic Scrum-oriented workflow, creation of Backlog Items and then tasks for those items, task linking and relationships, resource management and sprint-level capacity planning - these are more similar than they are different. On the whole, the JIRA and TFS workflow and organization are equivalent. But having cut my Agile teeth in a world of open source tools like JIRA and Confluence, I canвЂ™t say IвЂ™m 100% satisfied in what TFS brings to the table.

IвЂ™m a longtime user of TFS as an integrated source control/dev process tool, and I think itвЂ™s wise to incorporate this Agile management element into it. This has been my first experience using that aspect of TFS, so IвЂ™ve been alternately surprised, annoyed, gratified, accepting - IвЂ™ve run the gamut of human emotions dealing with this tool. Our industry experts have collected the latest application modernization trends impacting the automotive, financial services, healthcare, and manufacturing verticals.ДЇor several months, IвЂ™ve been working on a DW/Reporting project which uses Team Foundation Server (TFS) 2012 for Agile project management. Application Modernization Industry Quick GuidesДЄpplication modernization enables you to optimize business processes and transform the way you do business today, and in the future.

Microsoft team foundation server agile project management