In keeping up with these times of limited resources and high desires (if not expectations – which may also be running high!) it is critical that project priority be properly set. Many of us have been involved with projects which have many facets to them, and depending upon the environment those facets may be very clearly defined, or perhaps somewhat nebulous. They may be down on paper or in the developers and users heads. Either way, setting the proper priority for the project is critical.
While there are many criteria to focus upon I believe there are two areas in particular that warrant looking at very closely. Certainly the overall value of the application to the business is one critical criteria to be considered. Where does the application fit? What will it bring in the way of added value to the operation? Can this added value be quantified? Is this an application which when completed will result in the saving of time, labor or materials? If so, to what extent?
In addition to the added business value of the application I believe that the testing procedures being used with the project be clearly monitored. Test for value to ensure that the desired or expected return can be achieved. Test especially for data integrity, try to “break” it, ensure solid product through your testing. Be creative in the testing wherever possible in an effort to prove usability.
I believe that any project which can’t produce a high “value add” probably shouldn’t be done (at least at this time). However, any project given such high “value add” is worth taking the time required for testing which will produce a reliable and valuable application. Now more than ever, extensive testing should be the order of the day.