2. Steps To Follow A Benefits Realisation Approach To The Implementation
To recruit and advertise the professionals are required.
To document and analyze the specifications for the functionality which is required.
To acquire the hardware which is needed and the software that is considered to be a part of the infrastructure of the IT facilities.
To test, design, implement and run the whole system.
After this, there is a need to define human resources in the segments of seniority, hourly and category costs:
Technical support - Possesses technical knowledge of the product
Functional expert(s) - Possesses knowledge of the process of business
System Administrator- Maintains the workflow environment
Workflow Business Analyst - An expert of workflow tools
Business Analyst - Assists during the analysis of a business process
Nowadays, a project's cost is majorly fixed even before the designing is completed, and many times even before the designing starts. Approximation then turns into majorly guesswork which is founded on the experience which was gained by earlier mishap estimates. If there is no design, it becomes impossible to figure out the number of lines of functions /code/objects /components required . The estimator should depend on the documents and information which is at hand before starting the design, more instance the non-functional and functional needs, use-cases, and workflows. Hence gathering the requirements and anaylzing them is imperative for the estimation of the project (it's testing, design and development).
With the use such documents, the estimator may be able to create an object hierarchy tree at the same time. The object hierarchy tree may aid in the identification of different types/levels of objects that must be created, the expectation from these objects, as well as a few attributes of the said objects. So, if there is no application design in position, the scope of work that needs to be done; when talking in terms of the required functionality, can also be identified.
After that there is a need to figure out a typical team member's output. Some of the organizations like to divide the team members according to the pay scale, role and position of each member of the team. The output of the team member needs to be proportional to the salary, role, and position. The work of the team member is inclusive of suggestions, ideas research, coding, and discussions. However, their output also involves debugging, design, test case designs, documentation, testing, and coding. Generally an architect would not code, similarly a tester would neither, nor would the project manager. So, each of their deliverables is taken in a different manner, as shown below:
Number of Employees
400 hours @ £15,000 /month
250 hours @ £20/hour
200 hours @ £25/hour
50 hours @ £25/hour
100 hours @ £30/hour
15 hours @ £20/hour
250 hours @ £9/hour
There exist a few different roles for instance domain consultants, SQAs, deployment manager, etc. The problem which arises at this point is that a lot of approximations are done before there may be a determination of the numbeer of man-hours that are required by all of the above mentioned ...