Information Technology Reference
In-Depth Information
proportionately with the distance you are separated from the level where work is
carried out. It is more accentuated in large organizations. The people working on
the job and the first level management would always be knowledgeable about the
progress and quality of requirements implementation. It is the senior management
and other stakeholders that would be in the dark unless we have a proper reporting
system that keeps all stakeholders with the relevant information. Organizations
normally use a weekly status reports in which the project management team
prepares a comprehensive report on the project and communicates it to all
stakeholders. This report would contain all aspects of the project under execution
and provide the stakeholder with all that they need to know.
It is an exception rather than a rule to include the detailed progress achieved in
the implementation of requirements in the weekly progress reports generated by
the project management team. The weekly status reports contain the overall project
progress, issues, items needing special attention from the senior management,
change requests and so on but not the implementation of requirements. The change
requests would be normally be reported as part of the weekly status report. The
number of change requests received, rejected, accepted, completed, and under
resolution would be normally reported. Sometimes, the effort spent on resolving
the change requests and the corresponding impact on schedule would also find
place in the weekly status report.
The argument for not making a special mention of the requirements imple-
mentation is that:
1. Their implementation is quantitatively monitored using the traceability matrix.
2. The qualitative aspect of implementation is monitored using the quality control
activities.
3. The change request resolution is tracked using the change register and the
weekly status report.
4. When you carefully consider, the progress of the project itself is the progress of
implementation of requirements in the software artifacts (code as well as
information artifacts) of the project. So, reporting project progress itself is
progress of requirements implementation.
Therefore, it is felt that no separate reporting of requirements implementation is
necessary in the project status report or monitoring activities.
9.8 Reconciliation of Requirements
It is necessary to finally reconcile the number of requirements originally accepted
for implementation and the final number of requirements implemented at the
completion of the project.
However, the first priority is to ensure that all customer requirements as
amended by the accepted change requests are implemented comprehensively. This
is accomplished by the acceptance testing. The main objective of acceptance
 
Search WWH ::




Custom Search