The Chopping Block: Cutting Features From an IT Project
Consider dropping non-essential features for the good of the project and the organization.
I am often involved with projects that are running behind schedule and over budget. Such is life of an IT consultant, I suppose. In many instances, projects can recoup valuable time if non-essential features and functionality are removed from the immediate plan and postponed until a later time. This post explores the decision on what can and canβt be cut from IT projects.
Consider the following three questions:
- What type of project is it?
- Are executivesβ incentives in synch with other employees in the organization?
- What are the risks and rewards of keeping non-essential functionality to the overall project and the organization itself?
What type of project is it?
To read the rest of this post, subscribe or sign in with your
π Free account.
It'll only take a moment.
