It is important to recognize that mobile software applications for handheld PDAs are not just developed by 1 person in a dark room with a computer. The business unit manager can order a mobile software application to be developed, but someone must design it, develop it, test it and approve it. Do you really want the programmer to complete the entire application on his/her own, or do you want a person who understands the business to be involved? Here are some considerations:
- Do you want the mobile software application to look exactly like the paper form in use today? If you don't specify differently, the programmer may design it to look like a small piece of paper on a mobile handheld PDA.
- Do you want the programmer to dictate your business process, or do you want to tell the programmer how the business process should work?
- Do you want the programmer to tell the field workers how, when and where they should sync the mobile application, or do you want the business users to tell the programmer.
- Do you want the programmer to select the mobile handheld PDAs, or do you want the business unit to describe their requirements to the programmer?
- Do you want the programmer to tell the business unit when the mobile software application is complete and final, or do you want to test it and approve it?
Most of these questions have obvious answers. The business unit, the organization that will benefit or suffer from the mobile application, needs to have active input into the design, development, testing, deployment and support of the application. It is not a 1 programmer job.
The problem many development projects suffer from is this active involvement was not anticipated or planned, therefore, it either does not happen or comes as an inconvenient surprise. However, you have now been warned in advance so this will not happen on your project, right?
No comments:
Post a Comment