Источник:
http://www.jaestevan.com/why-you-sho...cle-management
==============
If you already use Team Foundation Server in your Dynamics AX projects, providing all benefits it can give to your teams, or if you are already convinced to use it soon, then this article is not for you.
You may not be convinced or, even worst, you may disagree about it to be beneficial to your methodologies and team behaviors. You can try to challenge my points with your project’s circumstances that make TFS unacceptable. That’s fine. I’m only asking you to read the full article first 
Team Foundation Server (or
Visual Studio Team Services*) is a tool, and as such, it will allow you to achieve the same tasks
faster and with less effort. Furthermore, TFS will also give the ability to execute
crucial tasks that are only available by using this kind of tools. Those tasks are mostly related to development work and source code management, what makes developer’s life easier, but some of them also help project managers and consultants, and support
Quality Assurance guidance and validations, testing and all the rest of
Application Lifecycle Management steps, whichever methodology is used to manage our projects:
Microsoft SureStep, Agile, Scrum, …
Not to mention that using TFS is mandatory in the new
Dynamics 365 for Operations, so including it in our lifecycle processes today will ease the transition and will put in place
a set of Best Practices than will improve your team since day one.
Let’s have a look at the benefits of TFS in the three main categories of Application Lifecycle Management:
- Work
- Code
- Build & Release
Read the full article at “Dynamics AX in the Field”, the blog from the Premier Field Engineering team at Microsoft.
Источник:
http://www.jaestevan.com/why-you-sho...cle-management