5 replies
by jamesrl
Projects must be measured.
A project must be done either a) as a cost of doing business (remaing in the game) or b) because you will save money,improve customer service, improve productivity or enable increased revenue.
If its B, you need to set a target and assess what the numbers are if you acheive the target. You then balance the cost of doing the project with the expected benefits.
That I like to do is use a payback period calculation. On a month by month basis calculate the costs of the project. Then calculate the benefits on a similar scale. At some point you will go from the benefits paying off the costs to a net gain -thats the payback period. A good rule of thumb is do the projects with the shortest payback first.
Also think about the product lifecycle - making a huge improvement in a system that you intend to change in two years is not a good idea, if the payback is 18 months.
In large projects we would usually look at an 18 month payback as reasonable.
James
by kstokes
I am still trying to find a way to measure the value of a project. This answer helps a little but not exactly what I was hoping for. How do you measure business value of a project prior to beginning and after implementation.
by jamesrl
Business Value of a project.
The problem is that many projects have no definable value.
You want to look at the things that can compose a benefits statement: Reduce costs (labour/service fees etc), Improve sales (revenue projections), improve productivity (reduce need to hire additional heads, improve output of existing headcount). These are known as "tangible" benefits, in that they can be measured.
Intangible benefits are things like, supports goal of common infrastructure, reduces complexity, makes a subsqequent project feasible. Tangibles are the only ones that can be measured.
The trick is often looking at the list of intangibles and seeing if they can be defined as tangible. In other words, take something fuzzy and apply a measure to it.
Six Sigma type process improvement projects use stopwatchs. They time processes, create averages, and set goals for improvement.
Perhaps if you email me with more details I can help refine your intangibles to tangibles.
James
by goodwisj
Well it isn't an exact science and it will depend on the type of organisation that you are operating in.
In the past we have used the metrics of cost, complexity, scale, time and strategic alignment to provide a measure
Cost ($):
Find 3 categories - say <= $50k, $50 to 100k, >=$100k....... score these with 1, 3 and 5 respectively
Complexity (X):
Find 3 categories - say simple, moderate, complex ... score these with 1, 3 and 5 respectively
Scale (S):
Find 3 categories - say 1-3 Users, Department/Division, Organisationwide ... score these with 1, 3 and 5 respectively
Time (T):
Guess what.... find 3 categories - say <= 1 month, 1-6 months, >= 6 months ... score these with 1, 3 and 5 respectively
Strategic Alignment (A)
And to complete the set find 3 categories - say not rated as strategic, necessary to support current operations, aligned with the updated business strategy ... score these with 0, 0.5 and 1 respectively.
Score your projects in these metrics and then calculate the function of each of them -
score = $ x X x S x T x A
Anything that is not aligned falls out as it has a functional score of 0, the others end up with a rating.... this is a start and needs to be refined to suit your needs..... try it out though; it is fiendishly simple and moderately effective!
cheers
Steve
by realgem
The value of the project is it's benefit to the company. Cost can be a factor in determining value, but not all companies cost projects the same way. Some include the staff cost as part of the project cost, some include only external costs, etc. You'll have to decide on that.
Business benefits are best outlined in a business case. These can be big and complex, or small and simple.
There are a few types of benefits: efficiency (less time to do something), new capabilities that enable the company to do something new, or maintenance of status quo. Categorize your projects this way. You'll find that the second category is the most popular because it's the sexiest, and the last category is the least popular. That's why you cannot measure benefits on just revenue alone.
You then have to align the project to your major business processes. These are not hard to identify. e.g. process insurance claims, sell products, manufacture products, etc. The most important processes, as determined by someone outside IT, will lend their value to the IT projects.
You must also determine the quantitative benefit and impact of each project. Enabling revenue, saving dollars, saving effort, number of users affected, impact of not doing the work, and so on.
Sum these up in a spreadsheet and then review them with your major business clients. You have to get agreement on all of this before you can call it complete.
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending