The current issue is basically meeting the requirements of the end user. Often when IT gather requirements for a specific system, users will not be clear on what they want exactly. So what happens is that when it’s ready for testing, the users will say no this should be like this way or no this should in a different way or this is a major requirement and function is missing.
This leads the IT department to go and rework on the system and the work becomes double and the timelines really get missed.
Some suggestions to solve the above issue are listed below:
- Requirements needs to be discussed in depth with the people that will use the application
- All requirements to be documented in details with everything that is needed in the application – this should be signed by high management of the dept and IT that they understand everything that is in the document so they can’t come say no we said we needed this and this
If it’s not in the document we can’t provide it - Before the development, we create a sample page of what it will look like in paint or photoshop so that the users can see before we start the work what it will look like and approve it – signed document by management also
Otherwise they will mess everyone up.
Requesting the writer to add one chart in the Result part.
Requesting the writer to elaborate more and may follow the below outline (table of content):
- Introduction
- History
- Tests and Measurements
- Treatment
- Results
- Discussion
- References