How do you measure the success of a major implementation project?
Director of IT in Software, 1,001 - 5,000 employees
The measure of a successful project is how satisfied the end-users are with the result. There's going to be bumps in any technology project. Things aren't always going to go perfect. Software is imperfect by nature. You can plan as much as you can but you're always going to hit some snags during deployment week. But ultimately the end-users are either satisfied or they're not satisfied, regardless of those blips. So the way that I measure my personal effectiveness is related to that. "Has this made your day-to-day lives easier?" That's super important, because technology is an enabler; it is not the one doing the job for you. The people are doing the job; the tools are what are enabling them to do that. So if they're not doing that and they're actually doing the opposite, then that's not success for me. Number two is, the folks who worked on the project, what was their experience like? Did they feel successful? Does the team feel like they delivered a good product or service? And if not, why? That's also a critical area that I measure myself on. So those are the two core things I look at in a project post-mortem perspective.Deputy Chief Engineer(Information Technology) in Energy and Utilities, 5,001 - 10,000 employees
1. Has the objective to implement the project been met? To what extent?2. Are users adopting to the new environment.
3. Is the new implementation directly/indirectly enhancing core business activities.
CIO in Energy and Utilities, 11 - 50 employees
ROIClient satisfaction
Productivity (project costs deviations in time, money and resources)
Team and company experience (lessons learned)
Content you might like
Production45%
Backup65%
Replication33%
Non-production DBs (Dev, Training, QA, etc.)30%
216 PARTICIPANTS
Very important.31%
Important.60%
Not necessary.5%
Not important at all.1%
880 PARTICIPANTS
CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.Director of Information Technology in Education, 201 - 500 employees
We use a simple test - ask them, on the fly, to code three or four items. One or two are simple, medium hard - and used more to see where the head is, logically speaking. Looking to see how they approach the issue. Other ...read more