The plan must adopt a review procedure which ensures that the final outcome meets user requirements according to service level agreements. A set of review criterion must be identified and adopted. These criterions must be used as benchmarks when determining is the installation achieved user requirements.
Given that the starting point of all requirements gathering is really a verbal interchange between the IT technician and client, good communication is crucial. Project managers must set the correct tone from the start of the project during the definition or exploratory phase. As a project manager, you must understand that user requirements must be captured correctly, and they have to be realistic and achievable.
One of the first things that must happen during this definition phase is the requirements-gathering meeting. This meeting usually includes representatives of all affected staff and could include the following members:
Project/development manager
The project/development manager should open up the meeting and act as the meeting facilitator. The relationship between the client and your team is formed during this meeting.
Client managers
Client managers are the functional managers working in the specific area seeking the solution; they will have specific business needs of the system and would be best able to relay this information to the analyst.
Users
Identified and knowledgeable users should attend this meeting to provide input about the project because they will be using the system regularly and will require different, more detailed functions from those at the management level.
IT department
It is crucial that members of the infrastructure, networking, security and technology groups also attend in order to help determine any system requirements that must be met and to ensure the necessary hardware is available and capable of running the solution.
Leave a Reply
You must be logged in to post a comment.