Tuesday, July 15, 2008

Best Practices for IS/IT

When I searched the internet for the topic, the results showed several links. I chose the second one and it led me to this page where they enumerated 23 best practices for IS/IT:

http://www.portlandonline.com/Auditor/index.cfm?a=bdacg&c=chbac

I am not going to post the 23 practices here but rather, I chose 5 practices which I think are simple yet essential. Here they are:

Practice 2: Try to keep projects small and modular.
- Effective information systems are not those which are very large but those which are small, functional and easily manageable. I think it would be very difficult to maintain a system which has a very large scope. If this cannot be avoided, at least try to divide the processes into smaller ones.

Practice 13: Don’t be afraid to stop and reevaluate if things are not going well.
- Professionals have the tendency to hide bugs or errors in their output because of the fear of staining their pride. This is actually a big mistake in a professional's part. Nobody's perfect and mistakes cannot be avoided. If ever a situation calls for a reevaluation of things, do not hesitate. It doesn't matter that much to be delayed a little if the final output is efficient instead of going straight even though there are still problems with the system. If mistakes or bugs are overlooked, this could affect the users in the long run.

Practice 16: Keep risks visible and managed.
- We should not deny or cover up for possible risks or problems with the system. These should be faced head on and solved as early as possible to avoid further complications or problems. Risks should not be hidden from the users because they also need to be aware of these.

Practice 19: Test
- Whatever output we produce, we must first test it several times to single out all the potential errors and mistakes. Also, testing the output gives us the chance to improve or change some sections of it. I believe that no output should be released and be made available to the users without thorough testing. This could confuse and even handicap the users' processes so it is desirable to test before implementing anything.

Practice 23: Conduct a post-implementation review.
- As future IS/IT professionals, we must not forget our work once it's done. After we produce the final output, we have to make sure that everything is working according to its function and that the system is working like a well-oiled machine. Conducting post-implementation reviews of our work gives room for improvement in future projects and criticisms should be taken constructively to produce more efficient projects for the days to come. study

So, the five practices I listed above are just a few of the many practices in IS/IT that help us produce better output and become more efficient professionals. These are very simple practices, yet these are the ones that are commonly overlooked or taken for granted. Wink

2 comments:

  1. Good combination of choices, Kate! I bet that if you will learn to master the art of these core values...( I mean, these practices) you will definitely become a better and effective professional.

    Your post is a big help for those who need study tips and guidelines for professionalism. :-)

    Good luck!

    ReplyDelete
  2. hi kate tnx sa imu post, nka kita kog links na pwede nko kuhaan ug ideas sa atong assgn... hehehe

    comment sa ako art ha??? tnx

    ReplyDelete