29 replies
Current IT governance frameworks such as COBIT
focus on IT's internal processes. Governance can be made even more
effective by including metrics structured around systems.
At Metrici, we have been comparing our system governance approach with COBIT, which is probably the most widely adopted framework for IT governance.
COBIT is very broad, and system governance is not a replacement, but complementary. Our Metrici Advisor product can be used to capture, analyse and report on many of the key metrics that COBIT uses.
But
there is a difference in emphasis between COBIT and system governance.
COBIT is arranged around IT's internal processes, and system governance
is arranged around systems.
The focus on process is absolutely
appropriate to ensure that the IT function works effectively. But an
exclusively process-based approach has drawbacks.
- The approach is too inward looking. It over-emphasises IT
functional activities (such as ensuring IT staff are properly trained,
or how well IT suppliers are monitored) at the expense of the IT
deliverable - viable, working systems that deliver valuable business
benefit. - It requires a reasonably high degree of process maturity. Without
this, most organisations find it hard to understand and adopt a
governance approach structured around processes. - It does not suggest where to direct action. It may identify, for
example, that disaster recovery is generally weak and that testing is
generally strong. But it does not highlight which systems actually need
better disaster recovery, or which systems buck the trend and have weak
testing. As a result, it tends to suggest broad "IT initiatives" rather
than focussed individual improvements. - It makes little sense outside IT. In fairness to COBIT, most of
its measures are externally relevant system qualities or relate to the
broader business. However, it presents these measures structured around
internal IT processes, and not around things the rest of organisation
understands.
System governance redresses this balance. It focuses on the
outcome of IT processes, as shown in the capabilities and qualities of
the systems. It does not require a high degree of process maturity. It
directly suggests where to act. And it makes sense outside IT because
it presents IT issues structured around systems that are familiar to
the broader organisation.
System governance still allows you to
view measures by process. But an exclusively process-based approach
does not allow you to view measures by system because the underlying
facts are not gathered per system.
If you use a process-based
framework like COBIT, consider using system governance within it. This
will help you distinguish between externally significant outcomes and
internal working practices. It will help you make the figures relevant
and understandable outside IT. Our comparison found that 60% of COBIT's
key metrics relate to systems and can be captured, analysed and
presented using a system governance approach. (Of the remainder, 20%
are general IT-business relationship measures, and 20% are measures of
internal IT practices.)
If you do not use a governance framework,
you can use system governance anyway. Unlike COBIT, it does not aim to
give you control and assurance of IT's internal processes. But it will
give you many of the same measures you need to manage IT effectively,
at a fraction of the cost of a full process-based governance framework.
To find out more about Metrici's approach to system governance, read our whitepaper System governance: the missing link in IT governance.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
To govern outsourcing you need
to establish service levels, check the supplier's development skills,
and negotiate costs. But how can you make sure that the supplier will
maintain and improve the systems?
What do you look for in a good nursery school (preschool)?
-
Service. You need to find a nursery that is open for the days and hours
that you need your children looked after. There is no point in a
nursery that does not open until 9am if you need to be in work for 8:30. -
Development. You want your child to learn and develop. You need to
check that the nursery staff are qualified, and can help your child to
learn and grow in basic skills. - Cost. And you need to understand how much it will cost.
But
these are not the most important. What's really important is that your
child will be looked after well, and given the care and love and
attention that you would give them if you were looking after them
yourself. In comparison, the other factors hardly matter at all.If you decide to outsource your IT, you need to look for similar things.
-
Service. You need to understand what service you will get from the
outsourcer. You can use tools like service level agreements (SLAs) to
define and then track performance against service targets. -
Development. If the outsourcer is going to provide development
services, you need to know that they are competent. You can ask for
evidence, such as an assessment against the Capability Maturity Model
Integration (CMMI), which measures the maturity of an organisation's
system development processes. - Cost. And of course you will negotiate costs.
Important though these are, they miss one vital element.
If
you have entrusted the care of your system to an outsourcer, how do you
know they will look after it? Will they keep the documentation
up-to-date? Will they upgrade the databases to the latest versions?
Will the code be as well structured and documented as when you gave it
them, or even improved? Will there be up-to-date test packs? Will the
system still comply with all necessary regulations? Will the system be
as efficient as it can be? Would it be easy for you to take the system
back if you had to?
These questions are critical. They determine
how well the system can support day-to-day business. They make a big
difference to how easy it is to change the system. They dictate how
long the system will last. Without care and attention, systems regress
in all these areas. If you have outsourced your systems (or even if you
have not), what have you put in place to manage this?
System
governance can answer these questions. System governance is a framework
for gathering and analysing this information, so that you can monitor
these system characteristics. Just like an SLA, it is a way of setting
targets for your service provider.
But it goes much further than an SLA. It looks beyond short-term
service delivery measures, into every corner of your system's well
being. It's a way of checking that your systems are giggling and
smiling, and not crying quietly in the corner.
To find out more about Metrici's approach to system governance, read our whitepaper System governance: the missing link in IT governance.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
There are surprising similarities between system governance and agile methods. Although they address different problems, they share many core values.
To get closer to the business, IT must recognise and promote its role as stewards of the business' IT systems.
To gain the benefits of system governance, you only need simple materials, processes and tools. Anything more complicated would get in the way.
System governance solves problems that affect everyone in IT. But it is hard to position system governance because few people are directly responsible for solving the problems.
Writing a single, definitive list of the IT systems within your organisation is a simple task that can deliver significant long term benefits.
IT risk management overlooks critical long-term risks. With system governance, you can identify and manage these risks.
Simple, direct websites work. Complicated, vague websites fail.
The web is indispensable to Metrici.
Many IT specialists see their web presence as an optional extra - the
thing to do - somewhere to publish a brochure. We are different. We
have captured our specialist knowledge in our product Metrici Advisor.
We deliver Metrici Advisor as a service over the web. The web-based
service costs much less than traditional consultancy. Our website is
our product. It is our competitive advantage.
We needed to think hard about our web presence. We looked at other businesses, to see what they do.
-
We looked at the websites of two leading suppliers of testing tools.
The home page of the self-proclaimed "Leader in IT value" took over 50
seconds (on dial-up) to load. What for? To show an animated hand. The
other one took 25 seconds to ask what country I was from, and show me a
picture of skyscrapers. 25 seconds later, I got a moving graph with the
name of their product on it. Both sites took around 360k of network
traffic, just to enter the site. Would you buy performance tuning tools
from these people? - We looked at the website of a company that
provides IT management tools over the web. They proudly explain how
much cheaper a hosted service is than an in-house solution. But they
don't actually tell you their prices. - We looked at a local IT
consultancy. Their home page says, "To see how we can help you deliver
your business vision more effectively, please take some time to explore
this site." Evidently they have no idea what they would like to tell me
about themselves. But they considerately warn me that finding out for
myself might take some time. And they do have a nice picture of a
motorway.
These sites are typical. None of them get their
message across simply and directly. Perhaps they are not sure of their
message. Perhaps they can't explain it. Perhaps they're trying to hide
something. Maybe they believe they can entice readers to their site
with pictures of skyscrapers, and then bewilder them into buying.
To stand out, we needed to be different. We adopted two rules:
-
Be simple. Use a straightforward text-based layout. Don't have
irrelevant pictures of skyscrapers, motorways, or hands. Don't have
anything that moves. - Be direct. Explain how we deliver value, and what our products are. Publish our prices. Give the reader a call to action.
It
is a high-risk strategy. We may look amateurish - as if we lacked the
skill or money to build a proper "professional" website. It is true
that we are not visual design experts. It is true that we don't like to
spend money unless we understand what value it brings. But these are
not the real reasons behind our approach. Our real reason is that we
need a website that reflects our simple and direct approach to IT
management.
What does your website say about you?
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
To make your website simple and direct you
have to focus on a simple message. You can't be all things to all
people. You have to make hard choices about what to leave out.
Your website needs to focus on
- what products you offer
- what customers you target
- what benefits your products will bring
- the call to action for your website visitors.
You need a short list of things to include, and a long list of
things to leave out.
To show you what I mean, here is the short list of what the
Metrici website includes.
- We offer a web-based tool (Metrici Advisor)
that supports a method for long-term management of IT systems
(System
Governance). - We target IT managers in end-user organisations, who have
responsibility for the long-term management of multiple IT
systems. - We present how our products "answer your questions" about the
state of your systems and the actions required to improve their
long-term effectiveness. - We invite our readers to take a 30-day free trial of our
product.
Here is the long list of what we could say but leave out.
- We do not offer our more general consultancy services in system
governance. - We do not explain how Metrici Advisor can support assessments
and evaluations in other subjects. - We do not offer Metrici Advisor as packaged software.
- We do not target project managers, who could use Metrici
Advisor as a tool for reducing cost and risk in a single
project. - We do not target other IT consultancies, who could incorporate
our products into their services, to deliver more value to their
customers. - We do not present how Metrici Advisor could be used as a
product configuration tool. - We gloss over how much cheaper our products are than using
human experts to assess every project. - We miss out how our products can help manage outsourcing
contracts. - We do not cover how our products can support IT restructuring
after mergers or acquisitions. - We do not cover how our products can help regulatory
compliance. - We do not explain how system governance can add to company
valuations by quantifying the asset value of business systems. - We do not stress that we are happy for potential customers to
contact us and arrange a face-to-face discussion. - We omit to mention that anyone can use a guest logon to our
service, to have a quick look round.
Deciding what to leave out is really hard. You have to miss out
some of the best parts of your products. You have to ignore some
customers. You have to omit some benefits. You have to cut down the
options for what your readers do next.
Having a clear, simple focus makes your website easy for your
readers to follow. You will lose a few readers because of what you
have missed out. But you will retain many more.
It is tempting to leave all the content in, and let the readers
choose for themselves. But they will not choose. They will see your
website as vague and confused, and leave. If you want an effective
website, you must make hard choices.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
Lead your readers on a path through your website. Follow them to make sure they don't get lost.
To
be effective, your website must be simple, direct and focused. It must
call the reader to action ? to buy your goods, view your pictures, read
your documents.
But this is not enough. You must lead your
readers on a path through your website. The path must start at the page
they land on and lead them to the call to action. If you do not define
the path, your readers will not find it for themselves.
To show you what I mean, I will "lift the hood" on the Metrici website website.
Our
call to action is: "take the free trial of our service". It is a
web-based service that helps IT managers assess and improve their IT
systems.
We have two landing areas: the home page, and the publications pages.
The path from the home page is:
- Home page gives an overview of the main benefits of the service, and leads to
- Product page, which explains the product, its uses, and its benefits, and leads to
- Free trial page.
The
path from the publications pages is similar. The publications pages
provide details of our ideas on system governance. They then lead to
the product page, the same path as from the home page.
Defining
a path through your site is a balancing act. If the journey is too
short, it will not be convincing and it will not call your readers to
action. If it is too long, you will lose your readers.
Of
course, some readers want more. You should provide navigation, and more
in-depth content, to satisfy their curiosity. But most readers have
neither the time or the inclination, and laying a path for them should
be part of the service your website offers.
Having defined a
path, you need to follow your readers and check that they are not
getting lost. To do this, you can use statistics gathered from web
server logs.
There is some excellent material on web statistics at Google Conversion University. At Metrici, we use AWStats to understand how well our readers keep to the path.
These
statistics have shown us that "less is more". We have seen an
improvement as we have removed less relevant content from the path, and
taken out links that tempt the reader to stray from the path. We have
learnt to put the most important information and links at the top of
the page (for impatient readers), and the detail below. We have learnt
to focus on benefits, not features.
We have more work to do. We
are happy with most of the path, but we are losing readers on the last
step. Perhaps we have removed too much content. Perhaps we have created
a barrier. But at least by laying a path, and measuring how it is being
followed, we know where to improve.
Is there a clear path through your website? Are your readers following it?
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
If you want a website for your young company, do
not waste money on elaborate design. A simple design will be more
effective. And cheaper.
We started Metrici a few months ago. We needed an effective website. How could we get one?
We
could buy an off-the-peg website. There are companies offering cheap
template-based designs for small companies. Or we could spend some
serious money and hire specialists to design and build a custom website
for us.
Neither of these options met our needs. The
template-based approach would give us a "me too" site. It would not be
easy to integrate with our application. It would not be easy to change
and grow with the business.
Specialists could build us an
excellent site. But we would have had to tell them what message we
wanted the site to give ? which we couldn't do. When we started out, we
were not sure what we wanted to say. We could have thrown away
thousands of pounds on a site that would not say the right thing.
We
decided to build the website ourselves. We looked for examples of good
websites: there are very few. Some websites are all style and no
substance. Some have so much in them that they are difficult to use.
Many are laughably inept.
But there is excellent advice out there. We read Gerry McGovern avidly. Some sites impressed us. I was particularly impressed by Skype because they managed to persuade me to give them money within five minutes of my first visit to their site.
We adopted some web design principles.
- Be simple, direct and focused.
- Have a clear call to action.
- Have a clear path through the website.
- Avoid non-core content altogether.
- Avoid unnecessary images.
- Avoid "bells and whistles" such as visitor counters.
- Monitor how readers use the site.
- Be open to change ? reflect the evolving message and reader feedback.
Over
the months, we have picked up a lot of web design best practice. We
have put this best practice into our Metrici Advisor tool. With this we
can easily check the quality of our own site. You are welcome to try
our website assessment tool for free to review your own website.
Our
website is not perfect. We could make the site more visually appealing.
We could improve the wording. We could improve usability. However, we
do understand our website intimately. It accurately reflects our
marketing message. We know where it is effective. We can change it
ourselves, simply and cheaply.
At the start, web specialists
would not have given us much value. Our website might have looked more
professional but it would not have given the right message. It would
have been all style and no substance. Now we know what we are trying to
achieve with our website. Now we know where we could get value from
specialists.
We could have spent a lot more money up front. I am
glad we did not. Our website works well for us. We are in control. By
spending less, we have achieved much more.
Try our new website assessment tool for free.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
Web accessibility is not an expensive imposition just to make your
website usable by a few visitors with special needs. It makes your
website more effective for all your visitors, and pays for itself.
Philip Crosby's book "Quality is Free" makes the point that an
investment in quality pays for itself quickly, and that quality becomes
an ongoing source of profit.
In the same way, making your website accessible is free.
I was working on our website assessment tool
(which you can try for free). We had divided our assessment criteria
into three main sections: content, structure and interoperability. I
thought we had missed out a section for accessibility, and naively
asked a colleague what we should have in it. He quite rightly pointed
out that accessibility is something you have to build in to the content
and structure of the website, and into the technology choices you make.
Accessibility isn't an add-on.
Nearly all accessibility requirements are just good practice that will help all your visitors.
To be accessible, you need to use simple and clear language, divide
information into manageable chunks and use subheadings. By doing this,
you get your message across to all visitors. Remember that most people
just scan-read.
To be accessible, you need to have meaningful link text, provide a
site map or table of contents, and provide consistent navigation.
Clearly this makes it easier for all visitors.
To be accessible, you need to separate content, layout and style.
You should use cascading style sheets (CSS) to keep the layout and
styling separate from the underlying HTML. This makes website
maintenance easier. It makes the site usable on multiple devices, such
as mobile phone browsers, and on future browsers and devices.
If you use active content such as JavaScript or Flash, accessibility
can become harder. You may need to provide an HTML-only alternative for
when these are not available. But an HTML-only version has other
benefits. Many browsers do not support active content, and often people
turn it off because of security fears. Search engines only understand
text, so an HTML-only version makes your site easier to find in search
engines.
For most sites it is more effective to avoid active content
completely and only provide an HTML version. Put your effort into
understanding your visitors and into superlative content, not special
effects.
Accessibility requirements are not an imposition. They help your
website meet the special needs of a minority of visitors and the
general needs of the majority. By making your website more effective
for all your visitors, accessibility pays for itself quickly and
becomes an ongoing source of profit.
Accessibility is for all, and accessibility is free.
To find out more about web accessibility, read the W3C's Web Accessibility Initiative, especially the Business Case for Web Accessibility. Also try out our website assessment tool (for free), which provides a high-level analysis your website's accessibility.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
We think of governance as a long-term strategic
initiative. But governance of IT systems also delivers short-term
tactical benefits.
System governance is a method for the
long-term management of IT systems. The main aims of system governance
are to reduce support issues, avoid difficult "legacy" systems, and
prolong the useful life of systems.
At Metrici,
we have been presenting our ideas on system governance for a few
months. Much of the feedback we get is, "Nice idea, but not our
priority right now." People are more concerned with the immediate
problems of project delivery.
This is a challenge to us. We
clearly see that well governed systems would help project delivery. But
we have not been clear about how these benefits can be achieved in the
short term, not just the long term.
To tackle this, we have been looking at maturity modelling.
Many
in IT are familiar with the Capability Maturity Model (CMM) and its
derivatives. This measures how much an organisation uses defined
processes to manage its systems development activity.
Maturity modelling is a more general technique. The general idea is:
- Different organisations tend to adopt the different parts of a method in a similar order.
- Mapping where on that order an organisation lies gives an indication of its maturity in the method.
- The maturity level shows what the most appropriate next steps are, and what the benefits are likely to be.
We drew up a maturity model for system governance. We came out with six levels:
- Non-existent. Organisation carries out no system reviews.
- Ad hoc. Organisation carries out occasional, non-standardised reviews.
- Standardised. Organisation carries out occasional, standardised reviews.
- Committed. Organisation reviews all project and existing systems.
- Consolidated. Reviews are co-ordinated across IT organisation.
- Strategic. System governance is used to set, communicate and enforce business-lead IT policy.
A more complete write up is available in the paper System governance maturity model.
Drawing
up the maturity model helped us understand system governance. So much
so that I would recommend maturity modelling to anyone trying to
understand or promote a new technique.
The system governance maturity model shows:
-
For organisations that carry out few, if any, system reviews, system
governance reduces risk in projects and delivers higher quality
systems. System governance is an effective, fast, and cheap project
review method. - In the medium term, system governance starts to become the basis for the long-term proactive management of IT systems.
- In the longer term, system governance can be used to define, communicate and enforce business-lead IT policy.
Most
organisations do not see the long-term management of IT as a priority.
To them, we can more clearly present system governance as a good way of
meeting their immediate needs for short-term project risk and cost
reduction.
Stressing the tactical benefits does not weaken the
strategic view. The maturity model shows how they are connected.
Businesses have to see the benefits of tactical use before they can
take on more strategic use.
Over the next couple of weeks, I
will explore these short-term uses of system governance more. Next
week, I will look at how system reviews deliver value into the IT
project management process.
To find out more about Metrici's approach to system governance, read our papers System governance: the missing link in IT governance and System governance maturity model.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
An effective system review reduces risk and cost in your project, and helps you make the best use of scarce technical staff.
When you run an IT project, you need to carry out three types of review.
- You need to review the project progress, timescales, and budgets.
- You need to review the project deliverables.
- You need to review the IT system itself.
The system review is often confused with the deliverables review. But the starting points are different.
The
deliverables review starts with the business requirements, and checks
that these have been taken forward effectively in the design.
The
system review starts with an idea of what a good IT system looks like.
It works back to check that your system will meet these more general IT
requirements. It makes sure you deliver a system that will be a good
citizen of you IT estate, not a delinquent.
A system review
needs to consider all characteristics of the system, whether or not
they are part of your design. This includes: responsibilities, data
integrity, performance, availability, security, recovery, test
availability, documentation, reporting facilities, fit to technical
standards, technical viability, and many more.
It helps to have
a standard template for your system reviews. The template should
clearly explain what a good or bad system looks like. If you have to
reinvent the review for each project, it will only contain the things
you have already thought about. It will not challenge your proposals
effectively.
A good review template lets you carry out an
effective review without having to assemble a panel of experts. The
template should show you where you need specialist assistance, helping
you make the best use of scarce resources.
The review needs to
be more than a simple checklist. It needs to ask searching questions.
For example, to review system availability you need to consider for
what hours the system will be available, if and when it will be
unavailable for routine maintenance, and what the business impact of
non-availability would be. This is different from a design review,
which might, for example, focus on the use of resilient hardware.
Run a system review three times in your project.
- In the early stages of design, to identify gaps in the overall solution.
- At the end of detailed design, as part of you quality assurance process.
- After implementation, to provide a baseline to ensure that ongoing support maintains and improves the quality of the system.
If
you are replacing or extending an system, review the existing system
before you start the new design. This helps build the case for change.
It makes sure that you repeat the successes of the existing system, but
avoid the pitfalls.
System reviews give benefits in the project
and in the deployed system. They help you identify omissions early in
the project, and to fix them before the project needs costly rework.
They help you make the most of scarce technical staff. They help you
deliver a higher quality system, which reduces long-term risks and
support costs. They help you avoid the built in obsolescence that
forces an early end to many IT systems.
Metrici provide tools and services to help you with system reviews. Our 30-day trial lets you try our system review template for free.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
by mrwizard10
I would recommend that on longer projects, conducting a review every 4th meeting or so just to keep everyone on track. This can be a short status check review but it can help to keep everyone focused on scope, budget, and schedule.
That is a good suggestions.
We need frequent, informal reviews of the project, as well as the more formal stage-end reviews. This helps build an environment of open communication, and helps avoid the big surprises that so often upset projects.
Andrew Clifford
When you are selecting a new software package, do
not rush the preparation of your vendor questionnaire. A well-prepared
questionnaire helps you review the impact of each option easily and
effectively, and saves you time in the long run.
Many business
have a process for selecting new software packages. This might include
an invitation to tender (ITT), request for information (RFI) or request
for proposal (RFP).
Within your process, you need to investigate
how well each option meets business requirements. You need to look at
commercial aspects such as cost and vendor viability. You need to
investigate whether each vendor can deliver to your plans.
You
also need to understand the technical issues of each option. This will
identify options that have such severe problems that you should not
select them. Whichever option you do finally select, a knowledge of the
issues will help you understand what you need to do to implement it
effectively.
Technical reviews usually involve sending a
questionnaire to each vendor, and reviewing their responses. I have
been involved in many of these reviews. They are often frustrating.
- Often you do not get back half of the information you need, because you did not ask the right questions.
-
Often you do not get back the sort of answers you expect. You get
one-line answers when you expected an explanation, or pages of
marketing fluff when you wanted a one-line answer. - Many questions are pointless. Questions like "Can the data be backed up?" always give the answer "Yes".
-
When you come to review the answers, there are arguments about what is
good and bad. The review descends into political infighting and which
vendor gave the best lunch.
These problems are surprisingly
common. They completely undermine the review. They stop you identifying
critical technical issues.
These problems are caused by a lack of preparation. A little preparation goes a long way.
-
Start with a standard questionniare template so that you know you have
covered all the important areas. Run a workshop with all relevant
parties (often different technical specialists from the IT department)
to refine the questions. - Think what you are looking for in
each answer. Think what a good answer would look like, and an
unacceptable one. Think about the limit of acceptability: an answer
that is OK, but only just. - Carefully word each question to ask
precisely for the answers and level of detail that you need. Never ask
a question to which everyone can answer "yes". - Agree a
weighting and scoring scheme before you send out the questionnaire. One
easy way is to take an average of the weightings from different
stakeholders.
This approach helps you understand the technical
issues with each option. It is effective, fast and cheap. It provides
an auditable process to show that you have investigated properly.
This approach is the basis for the system review method that we promote at Metrici, about which I wrote last week.
You can use the same approach, and similar templates, to help you
during system selection, and to review systems during projects.
It isn't rocket science. But it works.
Metrici
provide templates, tools and services to support system reviews,
including a service to carry out reviews on your behalf during a system selection.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
There's no such thing as a future proof IT
system. Good design can prolong the life of your systems, but what's
really important is that you care and know about the state of your
systems.
Over the years, I have often tried to sell advice on the promise that it would future proof the system. Here are some examples.
- Open systems let you change hardware and system software, without the lock-in of proprietary technology.
- Layered architectures let you change one part of a system without impacting other parts of the system.
- Decoupled integration lets you changes one system without impacting other systems.
- Data normalisation lets you extend a database without invalidating what is already there.
- Standards-based programming languages minimise the impacts of new versions, unlike many proprietary languages.
Looking
back, I was wrong to think that these could future proof systems. These
design decisions help minimise the impact of change, but they are never
enough. It only takes one bad decision to mess it up. I used to work
with large mainframe systems with well designed databases that could be
extended easily. But because the systems were not well modularised, the
programs became impossible to change. The good efforts on database
design were wasted.
And there are lots of things we just can't
design out. A system might fall out of favour with management, and not
be maintained. It might be much more successful than originally
assumed, and hit dreadful performance problems. Documentation and test
packs degrade because of constant maintenance. We can only guess what
technology changes will happen a few years from now.
There is a good body of knowledge on Software Evolution
that looks into why software declines through time, the impact of this,
and how to manage it. There's a lot of good stuff there. But just
understanding is not enough.
There are two things you really need to future proof your systems.
-
You need to care. Most businesses value new IT projects much more than
their existing IT. They presume obsolescence in a few years, and a lack
of management attention makes this self-fulfilling. But the opposite is
also true. If you believe your systems should last for 20 years, it
will drive you to manage them differently, and you have a good chance
that they will. - You need to know. When you are changing a
system, you need to know what to do to keep it viable. Whether or not
you are changing the system, you have to know how well it now meets the
evolving business and technical environment. If you know, you can do
something about it.
At Metrici, we have been developing ideas on system governance.
System governance captures what's important to you about your systems.
It enforces this when you implement or change your systems, so you
don't build in obsolescence. It monitors your existing systems to check
that they are keeping up with your business and your technology.
System
governance gives you a framework that helps you care for your systems.
It tells you what you need to know to keep your system viable. You
can't future proof your systems. But with system governance you can
give them a long and fruitful life.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
Projects are not investments, and "project portfolio management" is nonsense. Misunderstanding this leads to serious problems.
The word "investment" has two meanings.
- The act of investing money. A transaction.
- The property in which money is invested. An asset.
Projects are transactions. Projects are not assets.
We often use the phrase "projects are investments", but in which sense?
In
the sense that projects are transactions that acquire assets such as IT
systems, there is no problem in viewing projects as investments.
But without realising it, we are confused by the ambiguity of the word "investment". We see projects themselves as assets.
This leads to serious problems.
Thinking of projects as investment assets over emphasises the characteristics of the project.
Often
we put systems live because of project pressures, even though they are
not complete, untested, full of bugs, unusable, and fail to comply to
even basic standards. The transaction has been a success, but has not
delivered an asset and has not delivered value.
Thinking of projects as investment assets under emphasises the value of existing systems.
Existing
systems are significant assets because they underpin business activity.
Managing them proactively and extending their useful life improves
their value and reduces costs significantly. But when we think of
projects as assets, we blind ourselves. We embark on huge, risky, new
system implementations, rather than manage what we have.
Thinking of projects as investment assets stops us managing IT investments properly.
Within
IT, our main job is to supply IT. We have a vested interest in securing
funding for our work. We need to be aware of this conflict of interest.
When we advise our non-IT colleagues, we need to push against the
pressure to oversell IT.
But thinking of projects as investment
assets can blind us to this conflict of interest. We confuse project
spend (which is a transaction cost) with asset value. In good faith, we
put too much emphasis on justifying IT spend as an investment, and too
little into reducing its cost.
The confusion about the term "investment" is reinforced by project portfolio management (PPM).
PPM
is all about co-ordinating multiple projects, and ensuring they meet
business priorities. PPM is an excellent idea. But the name is
nonsense. A portfolio is a set of assets, but PPM deals with a set of
transactions. Our use of the term "project portfolio" perpetuates the
misunderstanding that projects are investment assets, and reinforces
the problems above.
I am not attacking project management or the idea of PPM. But we have to be clear.
- Projects are transactions. Of themselves they have no value. Their only purpose is to deliver.
- Existing systems are assets. With better long term management, including system governance, we can improve the business value of these assets and reduce costs.
-
We need to manage IT investment properly. We need to be alert to the
pressures to oversell IT projects. We must never confuse project spend
with value. We need to learn to be better advisers of our non-IT
colleagues.
When we say that projects are investments, we need to be crystal clear what we mean.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
IT managers are often enthusiastic for a broader business role. But this can undermine the value that IT can bring.
It
is really important that those of us who work in IT can work
effectively with our non-IT colleagues. We need to explain the
opportunities and limitations of IT, without confusing them with
technical detail. We need to make our contribution to business change.
Some
would take this further. They would say that IT is so significant that
IT managers should propose and lead more general business change. IT
should move on from its technical background.
I think it is dangerous if IT managers move away from the technical detail into a more general role.
The
most obvious reason is that someone, somewhere, needs to understand the
IT. If the person from the IT department does not, who does? The IT
contribution needs to be made by somebody who deeply understands the
opportunities and limitations of IT, not a general manager who just
happens to work in the IT department. You can not leave the IT
decisions to an outsourced IT supplier. They will recommend what is
profitable for them, not necessarily what brings best value to you.
Even
if they claim to have moved away from the technical detail, those with
an IT background are still tainted by IT. They speak the language of
IT. They see business change in terms of IT change. They find it hard
to recommend business change without an IT project.
Some would
say that IT managers should take a leading role because no one else is
as well positioned. Only IT can see the breadth of business activity,
and can change the information "life blood" of the business.
This
is folly. Businesses are run on commercial, political and social lines.
Finance and Human Resources (HR) have a much more accurate perception
of overall business forces. Despite their good position, finance and HR
managers do not dare to take a leading role in business change because
they understand that their specialism is only a supporting role.
Changes to business operations need to be lead by the operating
departments themselves, not by a specialist group, however well
positioned.
Some would say that IT managers should take a
leading role because no one else is as well qualified. IT is an
excellent training for business change because of the systematic
attention to detail and the need to run complicated projects.
This
is also folly. Businesses are not as systematic as IT. Business change
requires commercial and political skills, not systematic detail. A
business process model and project plan coming from the IT department
will not change the business.
Those of us who work in IT should
stop being so apologetic about our IT credentials. IT brings value
because the technology of information storage, transformation and
communication can greatly improve business efficiency. Our role is to
understand the opportunities and limitations of IT and to explain these
to our non-IT colleagues. We do not become more business focussed by
becoming less technical. We just become less valuable.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
We find it hard to save money in IT because big
cost savings threaten our jobs. But if we want long-term job security
we must reduce costs, even if it means we lose out in the short term.
Of
course we all want to reduce costs. We want to bring our project in
under budget. We want to get a good deal on our hardware. We want to
negotiate the best price with our outsourcers.
But these are
relatively small savings. Costs in IT come from two sources: from
running existing systems; and from running projects. Most projects fail
to live up to our expectations. We have lots of difficult legacy
systems. We have many systems doing the same thing, because we find it
hard to get rid of the old ones. We spend a lot of money fixing old and
incompatible technology.
The really big savings in IT come when
we can tackle this waste. When we identify which parts of which
projects are not going to deliver, and avoid doing them. When we manage
existing systems better so that there are no difficult legacy systems,
and no overlap. When all our systems follow the same technical
standards.
But then there is a problem. Some projects would be
cancelled. Other projects would be reduced in scope. We could slim down
our computer operations. We would not need as many support staff. We
would need fewer IT managers, project managers, IT architects, and
technical specialists.
To ask the question a different way,
would you like your IT budget cut in half (or that of your customers)?
Would you like half your colleagues made redundant? Would you like your
project cancelled? Would the IT department have as much influence if it
was not so expensive?
Put like this, few of us really want to
save money. We want to save a little here and there so that we look
good. But we do not think about big cost savings because we would be
the casualties.
I believe that these significant cost savings are possible. We should face up to the challenges for two reasons.
Firstly,
efficiency wins over inefficiency. If your business does not make these
cost savings, your competitors will. This applies whether you are an
end-user organisation, or an IT supplier. You have to choose between
risking your job in the short term, or definitely losing it in the long
term.
Secondly, there is a lot of IT work to be done. If we make
IT simple and cheap, the business case improves. We could apply IT to
many more business problems, and bring much more value. Cost savings
will be more than compensated by additional opportunities.
We
can learn a lot from retailing. Over the last 20 years, nearly
everything has become cheaper. Shops that have kept prices high,
pompously declaring that their customers are not driven by price, have
lost out. They have been overtaken by their cheaper competitors. But
people are spending more than they ever used to, and the cheapest shops
make the most profit.
The message is clear. We should not fear cost reduction. We should grasp it passionately. Next week I will set out how.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
There are six ways to cut IT costs. Two of them are well known. The other four are yours for the taking.
We
all pay attention to efficiency and price. We organise and control the
work. We consider our sourcing strategy. We negotiate good prices.
But
as well as efficiency and price, there are at least six more ways to
cut IT costs. These are not management processes, but ways of looking
at the world that help you see where you can make big cost savings. I
call them "orientations", and the six orientations are: people,
standards, systems, responsibility, value, and customer.
The first two orientations are well known.
A
people orientation recognises that we need to work in ways that match
our human nature. We need some structure, but we are not entirely
systematic. We are creative, and we often change our minds. Our
motivation makes a huge difference to our performance. In IT, much of
this is addressed by agile methods and similar movements, and many
organisations are already benefiting from these cost savings.
A
standards orientation avoids the costs of running multiple
technologies, and the costs of technology lock-in. Standards let you
change your suppliers, and reduces the number of technological dead
ends that force expensive redevelopments. The popularity of open
systems, open source and commodity hardware shows that many
organisations already have a standards orientation.
The other four orientations are much less common.
A
systems orientation clarifies IT structure by thinking of IT as a
series of discrete systems. It stops IT being seen as a sea of
functionality sitting on top of multiple architectural layers. This
simplifies IT management, and opens the way for cost saving techniques
such as system governance. A system orientation is also a precondition of the next three orientations.
A
responsibility orientation clarifies IT ownership by placing systems
within the responsibility structure of the organisation. IT is not an
unowned resource, shared amongst a loosely-defined set of stakeholders,
or owned by the IT departments. A responsibility orientation helps you
make better decisions on the value of IT, and avoid many business
change problems. It stops IT being so much of a political football.
A
value orientation clarifies IT value by focusing on the automation that
IT provides, and separating this from changes to business processes.
This helps identify where IT provides no value over manual methods, or
where IT gets in the way. It helps us build smaller, cheaper systems
that are easier to use.
A customer orientation clarifies the
role of the IT department within an end-user organisations. Currently,
most IT departments see themselves primarily as suppliers, selling IT
into the business. Turning this around, and realising that you are the
part of the business that buys IT helps you see where IT solutions are
excessive.
Over the next few weeks, I will describe these last
four orientations in detail, show how they cut costs, and how you can
adopt them. Next week I will continue by covering the mechanism by
which these orientations cut costs.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
If you want to cut costs, you have to be prepared
to descope and cancel projects. You have to avoid heroic project
management that battles on against all odds.
To cut costs, start with a simple calculation.
cost = quantity x unit price
There are two ways to cut costs: by reducing quantity, or by reducing unit price.
In
IT, we tend to concentrate on unit price. We manage projects carefully.
We select technologies with low cost of ownership. We employ skilled
staff. We negotiate good deals.
But we do not manage quantity well.
The
two main areas of IT quantity are projects, and existing systems. We
can cut IT costs by reducing the number, size and complexity of
projects; and by reducing the number, size and complexity of systems.
Of
course, we can not just abandon all our projects and systems. We need
to find a way to reduce quantity but maintain business value.
It
is easiest to see how with existing systems. Most large businesses have
generations of systems with overlapping functionality, and a lot of
functionality that is simply not used. This does not add to business
value, but is just "stuff" that we have to operate and support.
The systems and responsibility orientations I introduced last week
divide IT into smaller chunks that are more clearly related to business
activities. This makes it much easier to identify and remove
overlapping and redundant functionality. It helps remove the "stuff"
that adds cost but no value.
It is harder to see how to reduce
the quantity, size and complexity of projects without reducing business
value. But it is possible.
Projects are not black or white. They
are shades of grey. Most projects are not complete failures, but
neither are they a complete success. Many projects run into problems
with a lack of business case, lack of effective sponsorship, unclear
scope, difficult change management issues, or a lack of take-up.
Where
there are problems, projects do not deliver value. For example, weak
sponsorship indicates a lack of business buy-in, and will show itself
later by a reluctance to change the business and little effective
take-up of the system.
We can reduce the quantity of project
work, and avoid some projects completely, if we identify and avoid
those parts of the projects that will lead to these problems. Of
course, we have to distinguish between things that are difficult but
can deliver value, and those which will never deliver value. The
responsibility, value and customer orientations I introduced last week
do just that. They help cut project costs and deliver just as much
business value.
If you want to cut costs, you have to see some
issues in projects as signposts to better value. They are an
opportunity to revise projects to be simpler and cheaper, and cancel
projects that can not deliver any value. But a hero mentality, which
sees reductions in scope or project cancellation as failure, and which
will battle on against the odds, blinds you to these savings. If you
want to cut costs, you have to do without heroes.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
If you want to cut costs, you need to make your
IT easy to understand. You need to think of your IT as a collection of
business systems, not a collection of technologies.
Most
businesses think about their IT as a collection of responsibilities and
technologies. You might have an application development group, a
support group, and technical groups such as networks, databases and
servers. You might group IT by business area, such as sales,
distribution, and finance. Or you might group IT by technology, such as
PCs, Unix, the web, and mainframes. Most businesses use a mixture of
all these different viewpoints.
Having multiple viewpoints makes IT hard to understand and difficult to manage.
Some
business try to understand their IT better by using enterprise
architecture (EA) to model their IT. EA models can show logical
applications, system instances, data models, databases, business
processes, interfaces, and networks, all interrelated and
cross-referenced.
EA can model IT very effectively, but it does not make it easy for everyone to understand. Most people are put off by models.
A
systems orientation is a way of viewing your IT that is easy for
everyone to understand. A systems orientation breaks the IT down into
separate systems, where each system is a meaningful and complete unit.
By this definition, a system includes the business application
software, the systems software and hardware on which it runs, its
database, its network connections, and its support arrangements.
The
rationale for a systems orientation is that everything comes together
in the system. The business requirements, application software, server
environment, database, network and support team all come together in
the system. A systems orientation does not have the rigour of EA, it
hides technical details, and it does not tell you about business
processes. But it is simple enough for everyone to understand.
Object
orientation is a good analogy for systems orientation. A system is a
high-level object that encapsulates business requirements, technical
implementation, and support arrangements.
A systems orientation has many advantages.
- A systems orientation encourages decoupled systems with well-defined interfaces, which is the basis for effective systems integration.
- A systems orientation helps build a single list of systems, which makes it much easier to communicate and co-ordinate IT management.
- A systems orientation is the basis of system governance, which helps improve quality and reduce costs significantly in the long term.
- A systems orientation is a precondition of other cost-reducing orientations, particularly responsibility orientation, which I will cover next week.
A
systems orientation also helps reduce costs by making it easier to
decommission systems. Decommissioning is very hard because system
boundaries are too loosely defined and it is difficult to calculate the
business and technical impact of decommissioning. A system orientation
helps you see the boundaries and impact, which makes decommissioning
easier. Decommissioning reduces the functional overlap between systems,
and reduces the number of systems that need support. This reduces costs.
Systems
orientation is not the most exciting of management practices. But it
does help you understand your IT better, and is a foundation for many
other improvements. By making your IT understandable, a systems
orientation is a big first step towards reducing your IT costs.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
IT needs clear and strong business ownership. We
must structure IT so that ownership is possible, and avoid IT
structures that weaken ownership.
Last week I wrote about
systems orientation. Systems orientation divides IT into separate
systems, rather than a layered set of technologies. This makes IT
easier to understand and manage.
Systems orientation is a big
first step towards reducing IT costs. But you can achieve even greater
cost savings if you draw system boundaries in the right places.
Responsibility
orientation shows you where to draw system boundaries. Simply put,
responsibility orientation says that systems should live within, and
not cut across, management responsibilities.
Some would say that
this is a backward step. IT should cut across the inefficiencies of the
organisation, and create a more efficient business with automated
processes.
I disagree. When systems cut across management responsibilities, they run into problems.
-
Indifference. Indifference leaves the definition of the solution to the
IT suppliers, either in-house or external. The solution will not be a
good fit to business needs, and may be wildly extravagant, or totally
irrelevant. - Power struggles, using the IT system to pursue
political power. This burdens the already difficult business of IT with
political issues and organisational change that it can not deliver. -
Do-gooding. Well-meaning intentions cause havoc by filling projects
with requirements that are not backed up by effective sponsorship and
leadership.
People make much better decisions about things
that they own. They look more carefully at value and cost, and
understand impact more clearly. Our IT should be structured to
strengthen this sense of ownership, not undermine it. We must design IT
to fit within the existing management structures, and avoid IT systems
that cut across multiple areas of responsibility.
This reduces costs.
-
Project scope is reduced to what the responsible managers can directly
see will add value. Vague and unowned "improvements", that can not
deliver value because they are not followed through by management, are
avoided. - Business change problems are reduced by an order of
magnitude. Constraining IT within an area of responsibility makes
business change much easier to identify. Business change will be
smaller, clearer, and more effectively managed. - Traditional IT
problem areas, such as testing, migration and implementation, are much
simpler if limited to one area of management responsibility.
Responsibility
orientation does have challenges. Sometimes we build systems that
consolidate multiple responsibilities because this is, in the short
term, an easier way to build an integrated system. But in the long term
it leads to large unmaintainable systems, where IT imposes unnecessary
dependencies between business areas.
A responsibility
orientation replaces this with a more decoupled structure. Systems are
independent, and pass data that represents real flows of meaning and
responsibility. A responsibility orientation leads to a larger number
of smaller, more focussed, more richly connected systems.
Responsibility
orientation challenges our ideas on how we design IT, and our ideas on
the role of IT. But if we can meet these challenges, responsibility
orientation can help us provide systems with clear and strong business
ownership. We need to learn to be lead by the structure of business,
and not pretend we can lead business from the IT.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
If you want to increase IT value and reduce IT
cost, be realistic about what IT can do. Limiting your view of IT
to automation helps you spot unrealistic requirements that IT can
never deliver.
A value orientation says that IT only adds value when it
automates the storage, transformation and communication of
information. It adds value because it reduces manual effort,
increases speed, improves accuracy, or makes the infeasible
possible.
Some people disagree. They say that IT enables improved business
processes. Although IT can support improved business processes, in
a strict sense IT itself does not change business processes. Within
a business change project, the contribution of IT is limited to the
automation of the storage, transformation and communication of
information.
Value orientation helps business managers understand what their
systems do. They can view each system as a member of their team, to
which they can delegate information storage, transformation and
communication. Like all delegation, they do not abdicate
responsibility. They retain responsibility for everything the
system does, and must apply appropriate controls to the system. A
value orientation helps business managers understand the
opportunities and responsibilities of their IT.
A value orientation reduces a belief in IT magic.
We often come across situations like: "We had a problem with X.
We put in an IT system, but we still had a problem with X." X can
be anything: organisational structure, market position,
communication problems, control problems. These are human
management problems that can not be solved by IT alone. A value
orientation clarifies if and where IT can help. It stops IT being
seen as a panacea.
I once worked on a project to implement an IT system to support
a new department. The new department was formed by merging similar
departments from two different companies. After about a year we
were still gathering requirements and evaluating packaged
software.
To make sense of the project, we did some work to clarify
requirements. When we did, the sponsor cancelled the project. We
had showed that although we could put in an IT system to achieve a
lot of automation, IT could not tackle the underlying cultural and
organisational problems. It could not tackle the big problem of who
was going to be in charge in the merged department.
A value orientation helps you identify and avoid situations like
this. It identifies which business requirements can be met by IT,
and which need to be managed outside IT. It helps you slim down IT
projects to a smaller, more realistic set of requirements. It helps
you spot which projects should be cancelled, before you have spent
time and money.
Some would see a value orientation as an admission of defeat, IT
withdrawing to a purely technical role. I do not. IT never has had,
and never can have, any value other than the value of the
technology of information, which is all about automating
information processing. We undermine the position of IT if we
imagine otherwise. It we want a full role for IT, delivering
maximum business value at lowest cost, we have to be clear where IT
can add value, and where it can not.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
IT departments waste money by running themselves
as a business within a business, selling IT to their business
"customers". You can slash costs by turning this around, and seeing the
IT department as customers, who buy IT on behalf of their colleagues.
Over the past three weeks I have covered three ways of looking at IT which help you reduce cost and improve value:
- Clearly define separate systems, to make IT easier to manage.
- Structure systems so that they support, and do not cut across, business management responsibilities.
- Clarify how IT adds value, to remove from the IT domain business change that it can not deliver.
This
week I will cover the last of the orientations, customer orientation.
Unlike the others, which concern how you view IT, customer orientation
concerns how you view yourself and your role. This is, for end-user
organisations, the most important aspect for reducing cost.
A
customer orientation is about realising that you are the customer. You
are the buyer of the IT on behalf of your business. Customer
orientation only applies to IT departments in end-user organisations;
it is not relevant for IT supply organisations.
Most IT
departments would claim, "We already do that. We focus on the needs of
our customers, and work really hard to deliver what they want." But
that is exactly the opposite of what I mean.
Most IT departments
see their job as selling IT into the business, to encourage the take-up
of IT. They fulfil those sales either through in-house work, or by
passing it on to external suppliers. They see themselves as suppliers
to their business "customers".
There are significant conflicts of interest with this view. Painting an extreme picture:
- All IT spend is seen as good. The IT department measures its success by the size of its budget, where more is better.
-
The IT department feels closer to technology vendors than to their
colleagues. They work with vendors to sell IT into the business. -
If the IT department proposes expensive or risky solutions, nobody
within the business is qualified to review these. They might complain
about the cost, but in the end they have to accept the decisions of the
IT department.
The problem is not as extreme as this. IT
departments work as both supplier and buyer, and work in partnership
with both their business colleagues and external vendors.
But
even so, the prevailing mindset is that the IT department is a business
within a business. This is the most damaging of mindsets within IT. It
stops the IT department properly representing the interests of the
business' shareholders and customers.
Everyone within the IT
department must understand which business they are in. They are not in
the business of IT supply. They are part of the broader business. They
are functional experts in IT, the same way as the finance department
are functional experts in accounts. They are customers of IT supply, on
behalf of their colleagues. Their job is to help set requirements, not
just to get sign off so that they can supply.
This is a big
cultural shift for IT, but a crucial one. If we want to cut costs, we
must stop being sellers. We must start being customers.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
If you are starting a project, or even if you are
part way through, try some simple checks to see if you can cut out
costs. If you have not got time, or think they are not relevant, the
checks will bring you even more value.
If you structure your IT
so that it is easy to understand and aligns well with business
responsibilities, then you can see which bits add value and which do
not. You can cut out costs by cutting out the bits that do not add
value.
But where do you start?
Of course it would be easy
if you were setting up the IT for a new business. But life is not that
easy. Chances are you've got decades worth of systems with lots of
different technologies, intertwined and overlapping functionality, and
unclear ownership. You're probably part way through lots of urgent
projects, and are short of people and budget.
But you can start
from where you are. Like a great ship, a few little turns in the right
direction can change your final destination.
If you are already part way through a project, try a few checks to make sure that the project is focussed and can deliver value.
- Analyse your requirements to clearly separate why you are doing the project from how it needs to be done. See Classify requirements to separate the whys from the hows.
- Check that you understand how the IT will bring value. See How to check that IT is worthwhile.
- Check that the business will accept the new solution. See Use job descriptions to check business acceptance.
These checks should not take more than a few hours. If they do, your project is seriously oversized and needs to be cut down.
If
your project passes all these checks, well and good. Your project is
realistic about what it will deliver and can be accepted by its
business owners.
If any of these checks find issues, take the
time to consider them fully. You might be able to cut chunks out of
your project, and deliver the same value. Just what you need if you are
short of time and money.
If you are starting a project, try the Minimal IT analysis and design template.
This makes sure that the business opportunity, change and
responsibilities are defined before the IT is considered, and that the
IT is realistic. It should take less than a day to complete.
You
can use these techniques if you are starting a project, or if you are
half way through. They do not take very long. If you do not have the
time or money to do them, or if you think these sorts of checks are not
relevant, do them anyway. The more reasons you have to not make these
checks, the more valuable they are.
If you are looking more
widely across multiple IT systems, you need some more techniques to
start cutting costs. I will cover these next week.
? Copyright 2006 Minimal IT Ltd. See the Minimal IT website for the original newsletter and copyright information.
This discussion is closed to new replies.
Trending After Hours posts
Sort by Trending