Dynamics Implementation Teams Must Reach Escape Velocity
Project teams implementing Microsoft Dynamics solutions need to achieve escape velocity with their work effort in order to successfully complete the project. In project management terms, escape velocity refers to developing sufficient kinetic energy through teamwork to allow the team to execute planned work and overcome project and non-project obstacles in their path, while operating within the project constraints as defined by the project charter.
Back in 1959, the “first cosmic ship” was built by the soviets and launched toward the moon. Originally named Mechta and later re-named “Luna 1”, the spacecraft earned the distinction of being the first man made craft to achieve “escape velocity” from earth. The escape velocity as achieved by Luna 1 can be defined as the speed needed to break free of the earth’s gravitational field without further propulsion. When Luna 1 reached 119,500 km from earth a large cloud of sodium gas was released from the spacecraft which also gave the craft the distinction of becoming the first artificial comet. The glowing orange trail of gas was easily seen over the Indian Ocean and photographed as far away as the USSR.
Standing in my backyard looking at the night time stars I realize that if Luna 1’s propulsion system was insufficient to achieve escape velocity, then the craft would have either been stuck in a standard orbit around the earth, or the craft would have quickly bounced back to earth and crashed. Luna 1 needed to achieve escape velocity to overcome earth’s gravitational pull and achieve the goals and objectives of the mission. Luna 1’s story is no different from a team working on a Dynamics NAV implementation. The project team fuels the project through their efforts and propels the project to achieve the goals and objectives as originally defined in the project charter; if the team fails to provide sufficient fuel for the project then the project crashes and burns.
Often, project teams fool themselves into believing that they are moving at escape velocity. Some teams ignore the reality of their velocity and refuse to look down at their gauges of their systems as they fly through space on a mission. We all know the projects these teams are on; they are the projects that appear to go on and on until the executive sponsor finally pulls the plug.
Understanding, measuring, and adjusting team velocity is critical to the success of Dynamics projects. Project teams must confront reality and achieve escape velocity before the project can have any chance of being successful.