How do we measure success? This seems like it should be an easy question to answer but is it? Success itself is a dynamic variable that can be defined in several different ways from a promotion or even recognition from your peers. Now what about a successful cloud implementation or implementation in general? How would you define success? The true definition of implementing is to fulfill; perform; carry out: or to put into effect according to or by means of a definite plan or procedure. How do we apply this definition?
- The design and implementation team, success could be defined by the completed installation design, deployment and verification testing of all functionality as defined in the statement of work.
- The Steady-State team would have a completely different measure of success since their starting point would not begin until the deployment implementation was actually completed and signed off and their version of implementation would be to fulfill a role of maintaining the environment. A Project Manager may not consider things a success until the infrastructure has been built as well as the servers, desktops and or applications have been populated.
What about the people at the top of the food chain?
- The CTO or the CIO, how would they define a successful deployment or implementation? Wouldn’t the C-Level executives consider the complete lifecycle from build up to the tear down or hardware refresh?
I have personally have been involved with all sorts of projects and different roles over the years. I have done the design and implementation for one client, Steady-State for another client, Project Management for a different client and each implementation was measuring success in a completely different way from each other. One measurement of success, for me personally, was performing a major release upgrade to an environment and being asked days after the upgrade was complete, “when are you going to get started on the upgrade and will there be an outage?”.
I am going to say a successful implementation is going to be measured over the complete life-cycle of the technology that would be graded on all the projects and tasks performed on the infrastructure during the complete life-cycle of the deployment. Is that to broad of a timeline to get a clear picture of success or failure? Should we refrain from using the term “successful implementation” and focus the idea of success or failure on all the different projects, change control and SLA’s combined?
What would be your definition of success? Inquiring minds want to know.
Share this Article:
Latest posts by Steve Beaver (see all)
- Priorities of Uninterrupted Data Access - May 18, 2016
- Flip Side of the Coin: Automation Tools of the Trade - May 10, 2016
- A Look at Automation Tools of the Trade - May 2, 2016