Kocak! Istri Setuju Dipologami Tapi Tak Ikhlas
Sumber : https://www.youtube.com/watch?v=a1m2_t0YIm8
Seven Reasons Why Software Isn't Making Work Easier
The reason companies invest in software is to make work easier - right? Then why do so many users laugh at the idea?
After reviewing a large project I came up with seven reasons why the software wasn't making work easier. Looking at the list I realised that it wasn't just limited to this one project, but were common in many organisations and in many programs.
1. Processes and procedures are not written in conjunction with the software
The person writing the procedures does not incorporate the specific software in the flow. This then results in the software being an obstacle to the work flow.
In the project being investigated, the people writing the procedures had not used the software and were not aware of the features available. In fact what happened was that someone was focusing on procedures while another person was delegated with making the software do what was required. This split in responsibility is a false concept.
2. Configuration
The larger the software package, the more it will need to be configured or customised for the client. Time configuring the system correctly is an investment in the success of the project.
As an extension of the first point, it was found that the software wasn't actually configured to meet the requirements of the user, business or customer. It's not that it couldn't, but that no-one had invested the time to fully set up the system.
When rolling out a large project, there is a strong emphasis on being "on time" and "on budget". When it comes to "on quality" the focus is often on ensuring the software works - that is, it isn't buggy. The full test of "on quality" needs to expand to include being correctly configured.
The great aspect of configuration is that it can be done relatively easily. To clarify, it is easier than modifying the actual program code and releasing it. Configuration is meant to be the way to tweak software to really meet the user's needs.
Which means that as the program is rolled out, and users start to use it, the program can be adapted to meet the true requirements. It means that after being in use for some time and requirements change that the software can adapt with it.
Article Source: http://EzineArticles.com/7851941
