Figure 4.13 below illustrates the timing of project estimation and sizing activities. Regardless of the ICT Project Lifecycle it is involved in, the IV&V Provider must support sizing estimation efforts as part of its scope of IV&V Engagement.
Note: Please refer to Section 4.4 Project Lifecycle, on page 79 for full description and diagrams depicting the ICT Project Lifecycles.
Project estimation and sizing is particularly useful at each Quality Gate milestone before moving to the next Quality Gate. By calculating the Function Points (sizing) of the System Under Test (SUT) at each Quality Gate, examination of its fluctuations will indicate the degree of functional (scope) variances occurring during the lifecycle.
4.6.1 Function Points Analysis (FPA)
Function Points Analysis (FPA) measures the functional size of an ICT software product, and the unit of measure is called “Function Point count”.
FPA measuring techniques are standardised internationally (via international standards bodies like ISO/IEC) and can be used with other measurements to understand progress of activities and analyse the health of the ICT project.
FPA is used to:
- quantify the software deliverable based upon the user view point,
- quantify the amount of functions the product can provide to the user,
- inform teams of the level of work effort involved with a certain ICT implementation,
- be the reference point for changes in scope occurring if measured throughout the milestones of the project, and
- Be the comparison points of reference across projects and across Government agencies.
The Function Point count for Production System ICT project lifecycle is also known as a “benchmark Function Point count” because it reflects the true size of the software whose development is completed and operational in production environment.
In summary, FPA focuses on five (5) functionality perspectives of the software product which are:
- User interface (UI) screens – example, measuring adds, changes, deletes,
- Internal Logical Files (ILF) – including tables, files with data, control files,
- External interface Files (EIF) - including tables and referenced files from other applications,
- Input and Output files and transactions, including batch interfaces,
- Other outputs – reports, files, error messages.
Training for Function Point Analysis (FPA) are publicly available. The Agency may also request assistance from MyTCoE with regards to such training.
4.6.2 Integrated Project Plan (IPP)
Integrated Project Plan (IPP) is developed and finalised before the start of the Engagement Phase and driven by The Agency.
The purpose of IPP is to ensure harmonised and synchronised activities by all stakeholders (The Agency, Development Team, IV&V Provider and MyTCoE) throughout the lifecycle of the ICT project. If synchronisation is not achieved, it may cause:
- Non-productive engagement and utilisation of IV&V Provider’s resources,
- Ineffective utilisation of IV&V findings,
- Inability to achieve product quality goals,
- Wastage of resources.
Mechanisms within the IPP that enforces the synchronisation are as follows:
- Establishment of the PMO-TMO relationship to be adopted,
- Establishment of the ICT project lifecycle adopted,
- Defining the start and end dates of the IV&V engagement
- Finalising the need for QS Product Certification for COTS product acquisition, as required,
- Finalising the Quality Gates for Ground-Up, Legacy Disposed and Legacy Enhanced lifecycles, as required
- Finalising the test types to be executed by the IV&V Provider.
To ensure continuous harmonization and synchronization before and after kick-off, and throughout the development lifecycle, it is especially important that both The Agency’s PMO and IV&V Provider’s TMO continuously monitor, communicate, and update not only the Integrated Project Plan (IPP) but its facets of integration between the Development Team and IV&V Provider as plans evolve and change.
Thus, project issues and risks need to be collectively discussed and addressed.
To assist The Agency in finalising the IPP during the Pre-Engagement Phase, the considerations below can be used as a quick guide to initiate the scoping for IV&V Engagement
