Overview
During the Development/Integration phase, the system developers take the detailed logical information documented in the previous phase and transform it into machine-executable form. They ensure that all the individual components of the system/application function correctly and interface properly with other components within the system/application. The Development phase should conclude with a stage gate review to determine readiness to proceed to the System Integration Test (SIT) phase. The Project Manager, coordinating with the development lead, is responsible and accountable for the successful execution of the Development phase and leading the integrated project team that accomplishes this phase's activities and deliverables.
Process
During the Development phase of a project, the Project Manager may be tempted to believe it is a good time to breathe easy, since the planning and design efforts are in the rear view mirror and the technical people are now seemingly in "autopilot" mode during what is typically the longest SDLC phase. This is not a wise approach. There are several key best practice activities for the Project Manager, who must remain vigilant and engaged during the Development phase, to perform.
- Monitoring status of development progress (for more details, see Status Tracking) and unit testing. Remember the "80 hour rule" when creating and updating the project plan, i.e. anything that takes longer than two work weeks should be broken down into component parts in order to ensure accurate progress tracking and early escalation in case things get off track.
- Managing escalation and issues, e.g. clearing intra-department roadblocks or resolving communication problems.
- Driving corrective action decision by Project Sponsors and Executive Sponsors as required.
- Facilitating regular Development/QA team meeting. For more details, see Team Meetings.
- Managing scope using a predefined and agreed upon change control process. For more details, see Scope Management.
- Ensuring the Practice Area Director policies on access by the business to the SIT environment are communicated clearly to the business and managing any rules or conditions regarding such access.
- Planning and facilitating Conference Room Pilots (CRPs) and/or demos.
- Planning and monitoring execution of specific tasks in the project plan — with enough time for unit testing.
- At the conclusion of development, hold a development/QA hand-off meeting. As with SIT exit, UAT exit, and project closeout, verify scope by reviewing and confirming development work is complete:
- Review all unit test data against the approved specification
- Identify and resolve any discrepancies
- Validate all supporting documents
- Verify all deliverables are available
Obtain formal approval from the Practice Area Director and QA Director to proceed with SIT.
