<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gestion Del Cambio on</title><link>https://www.jaestevan.com/en/tag/gestion-del-cambio/</link><description>Recent content in Gestion Del Cambio on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Thu, 23 Aug 2012 00:00:00 +0200</lastBuildDate><atom:link href="https://www.jaestevan.com/en/tag/gestion-del-cambio/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Dynamics AX 2012 Application Lifecycle Management (ALM-I)</title><link>https://www.jaestevan.com/en/blog/2012/microsoft-dynamics-ax-2012-application-lifecycle-management-alm-i/</link><pubDate>Thu, 23 Aug 2012 00:00:00 +0200</pubDate><guid>https://www.jaestevan.com/en/blog/2012/microsoft-dynamics-ax-2012-application-lifecycle-management-alm-i/</guid><description>&lt;p&gt;Although it may seem curious, even unsettling, a large part of ERP implementation projects, including the &lt;a href="https://www.jaestevan.com/tag/dynamics/" title="Tag: Dynamics"&gt;Dynamics&lt;/a&gt; family in general and &lt;a href="https://www.jaestevan.com/microsoft-dynamics-ax-2012" title="Microsoft Dynamics AX 2012"&gt;Microsoft Dynamics AX&lt;/a&gt; in particular, are not run as software projects. Perhaps because of how close the project is to the business, or because the people involved spend most of their time with a business-oriented rather than software-oriented mindset, it is very common to forget, or ignore, that we are implementing &lt;strong&gt;software&lt;/strong&gt; and therefore it is advisable to treat the project as a software project, applying software engineering concepts to manage the software and project management concepts to manage the project.&lt;/p&gt;</description></item></channel></rss>