• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 377
  • Last Modified:

Early involvement in IT projects and cost benefits

Our IT section say it is more cost effective for auditors to get involved in new IT projects early on rather than post implementation. My question is, is that true, why is it cheaper to act on audit recommendations to say a new sharepoint installation during design as opposed to issues found and recommendations made post implementation. Can anyone explain the cost process and why during design is cheaper than post implementation. And do you agree with the view its cheaper to act of audit issues/concerns during design than post implementation?
0
pma111
Asked:
pma111
  • 3
  • 3
  • 2
2 Solutions
 
Matt VCommented:
It is almost always less expensive in both time and dollars to identify deisgn and implementation problems before they become a reality.  It takes twice as long and costs much more to go back and re-do things.
0
 
Paul SauvéCommented:
Snother point: if there have been audits on past projects with recommendation on how to improve the development process, implement them as soon as possible - I used to audit IT development projects...
0
 
pma111Author Commented:
>>It takes twice as long and costs much more to go back and re-do things.

Can I just ask from a real novice stand point, why that is?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Matt VCommented:
Because you end up undoing things to re-do them correctly.   You often end up having to purchase extra hardware/software/licenses that are out of budget.  You also risk looking like you don't know what you are doing if the resulting changes are major.
0
 
pma111Author Commented:
paulsauve,

Did you have any specifci document to work off when auditing IT dev projects, what kind of issues were you instructed to look for, I appreciate that each project will be different, but there must be some common ground. wasnt sure if you could recommend a book or set of reference material for such audits?
0
 
Paul SauvéCommented:
What I looked at was the development methodology vs. the actual developemnt process and the system specs vs what was delivered to the users. So you work from internal documents in your own organization...
0
 
pma111Author Commented:
So essentially seeing if "as designed" ultimately became "as built" ?
0
 
Paul SauvéCommented:
Also, to see if "the design" was done respecting the "design methodology", if there is a methodology!

Steps:
Preliminary analysis (possible solutions)
Cost/benefit analysis
Architecture
Business analysis
Thechnical analysis
Programming
Testing
and the appropriate documentation all throughout the process.


It is always more cost effective to make changes during the design process than in the finished project. Not only should the auditor be involven in design process, but the end user as well.

Have a look at this article: V-Model (software development)
0

Featured Post

Put Machine Learning to Work--Protect Your Clients

Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as the high-speed power of the cloud.

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now