What’s worse: too much or too little implementation time?
Vice President, IT & Systems in Software, 1,001 - 5,000 employees
When we tend to prolong an implementation, it becomes a problem. But when you stretch it too thin, that's a worry too. When we rush this, I have seen IT has no time to get the right vision from stakeholders. We then lack user stories, a good amount of User Acceptance Testing (UAT), and think about change management and enablement, which is the key to successful implementation because there's only that much time. So even if we claim victory in a record implementation time, we're left wondering, was the project successful? I believe the magic number or formula is somewhere in between.
Director of IT in Software, 201 - 500 employees
Both are not ideal… if you have to choose one then too much time is better then too little time. You can have the time but pretend you have just enough so you finish/implement the project and them use the slack time for something else, otherwise things can get dragged and you loose focus of the objectives.Content you might like
Yes43%
No57%
347 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.Daily20%
Weekly38%
Monthly15%
Every few months9%
I have never used a VPN to unblock content.16%
Other (comment below)2%
192 PARTICIPANTS
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 moreDirector Global Network / Security Architecture and Automation in Finance (non-banking), 10,001+ employees
Nothing ever dies in Enterprise. Why did Broadcom Software buy Symantec and VMWare, why did SDX Central post a story today about MPLS and how it lives on. Why is the hot news about cloud repatriation becuase a terrible app ...read more
I've come to the conclusion that sometimes you're better off saying, "Forget your current processes. We're going to put this in. Start using it and maybe we'll go back if there's a real problem." The normal enterprise approach is to spend the first 3 months arguing over the processes and how you want to change the software to fit your processes.