The Construction Phase of an IT Project

The construction phase of an IT project involves building the application using the agreed-upon environment and specialized tools. Developers create the application by using the design document as their guide.

During the construction phase, the project manager (PM) doesn't actually take part in conducting the components, but must have an understanding of each, so that he or she can oversee the project in a monitoring role. The components of the construction phase of the IT project life cycle are described below.

1. Inputs
The only input needed for the construction phase is the design document created during the design phase of the life cycle. The design document input is used as an outline for the development team to follow. It identifies what the final product should do, how it should function, and any necessary technical details.

2. Key activities
The key activities for the construction phase are preparing the detailed design and performing the programming. To complete the first key activity, which is to prepare the detailed design for each work unit, you should use the technical design as your guide. The steps for completing the detailed design are listed below.

• Complete the technical design. Complete any outstanding design work and estimate the impact of any design changes.

• Design the work units. Review the technical design and plan the individual work units for the application. A work unit is a logical portion of the project that can be designed and developed independently from another part of the project and then integrated as needed later.

• Complete the database design. Document the logical data structures and data areas used in each programming work unit and make this documentation available to the project's programmers.

• Review the performance design. The complete project team, along with end users, conduct a review of the programming work unit design to ensure that the design meets functional and quality requirements. This review helps ensure that the programmers understand the requirements and that the design is feasible.

• Iterate the detail design. After the design review, the preceding steps are conducted as many times as necessary to enable the project team to refine the design.

• Prepare the common test data. Construct a master test database with which to test each work unit. The database may contain the testing methods, test data, expected results, user instructions, and possible sample documents for use in the testing.

3. Tools
The primary tools needed to conduct the construction phase of the IT project life cycle are the specific programming languages and compilers that the programmers will use to create and test the programming code.

4. Outputs
The outputs of the construction phase of the IT project life cycle are the code, programming work units, test database, and unit/string test results. Once the outputs of the construction phase are complete, you will have a working application that can be tested during the next phase of the IT project life cycle. More information about the outputs is provided below.

• Code. Using a programming language, programmers write a sequence of instructions that translates the product design into a language that a computer can understand. The instructions are referred to as the program source code or the executable code.

• Programming work units. Programming work units are an output of the detailed design key activity and are used as the basis for the development of the code.

• Test database. A set of common test data is developed to provide quality control for unit testing.

• Unit/string test results. The actual test results from unit tests—and if applicable, string tests—need to be documented and preserved as part of the project documentation.

5. Milestones
The final component of the construction phase for the IT project life cycle, the milestones, must be met before the project can move on to the next phase of the life cycle. The milestones that must be reached during the construction phase of the IT project life cycle are the code review complete form and the string test sign-off.

• Code review complete. Once the review of the code developed during the construction phase is complete, the PM can sign off the code review complete milestone.

• String text sign-off. The PM signs the string test sign-off to indicate acceptance of the string test results and implies the completion of unit testing.

Using the design document as a guide, developers construct the application that meets the requirements of the user. Once the milestones of the construction phase have been met, you are ready for the next phase: testing the application.

Outputs to the IT Project Phases

Think back to the last time you were in a bakery where the aroma of freshly baked bread teased your senses. Making bread may be less complicated than administering an IT project, but it follows a similar development process with inputs (ingredients), tools (oven), and outputs (a loaf of bread).

Using a recipe and the necessary tools, the baker expects outputs at each stage—a ball of dough made from various ingredients, a larger ball of raised dough, and finally a perfectly formed and delicious loaf of bread.

An IT project also produces outputs, which are known as deliverables. These outputs are the results derived from each of the IT project's six phases—planning, analysis, design, construction, testing, and rollout.

Outputs, or deliverables, can help your team keep a project on track. Well-planned outputs are also an effective way for managers, IT organizations, sponsors, and users to learn effective lessons from a project. Remember to focus on achieving benefits and objectives when determining the outputs that will be generated during each phase of your project.

There are a number of major outputs for each phase in an IT project. Not all phases have the same number of outputs, but all deliverables help you and your team achieve success with the end product. Examples of outputs for each of the six IT project phases are listed below.

Planning phase. An example of a planning phase output is the business case, which provides validation for any project decisions made. It acts as the framework for performing all evaluations and as the starting point for guiding the management of the project.

Analysis phase. An example of an analysis phase output is the requirements specification, which contains or refers to the definition and details about the data, event, and process models, as well as the project quality requirements.

Design phase. An example of a design phase output is the design document, which contains or refers to the application architecture and flows, database and user interface designs, and the workflow diagram.

Construction phase. An example of a construction phase output is a programming work unit. Programming work units lay the base for the development of project codes for testing aids and application and conversion programs. Other nonprocedural codes are also included when applicable.

Testing phase. An example of a testing phase output is the operating instructions, which can be in the form of manuals, installation procedures, or instructions for using the new system. These instructions would be accessible to all end users.

Rollout phase. An example of a rollout phase output is the post-conversion review document, which can contain specifics on the scope of the conversion process and details about any problems that have occurred during conversion.
It is important to be aware of the outputs for each phase of your project. As you move through each phase, you will begin to understand the relevance of the role of each output for the particular phase to which it belongs.
Outputs can help your team tremendously by providing direction and valuable methods of recording the processes followed throughout your project.

Inputs to the IT Project Phases

Have you ever heard the term "garbage in, garbage out (GIGO)"? This is a term used to describe the results you would receive if you entered insufficient or incorrect data into a computer, for example. It also applies to your IT project.

You should ensure that all of the information you use in your project is of good quality. Any project can be detrimentally affected by the use of poorly researched information.

With thorough planning, you will be better able to determine and gather the information you will need for your IT project. By documenting this information, you will have a road map for developing an effective IT project plan.

In project management, the documents or documentable items that are produced and will be acted upon are called "inputs." These documents contain all the information your team has researched to make the project run smoothly and efficiently.

There are a number of inputs to consider for each phase of an IT project. Not all phases have the same number of inputs, but all inputs are beneficial to the success of the end product. Examples of inputs for each of the six IT project phases are listed below.

Planning phase. An example of a planning phase input is the information plan, which contains an extensive description of the company's present systems and the objective of the project.

Analysis phase. An example of an analysis phase input is the conceptual design, which describes the scope, architecture, and other aspects of the new system in detail.

Design phase. An example of a design phase input is the business process prototype, which depicts the working functions of the new system or product. It also highlights crucial or problematic areas.

Construction phase. An example of a construction phase input is the design document. The design document of the construction phase can include references or details on application flow, database design, and a workflow design.

Testing phase. An example of a testing phase input is user documentation. This documentation includes user instructions and procedures that the end users will require. It also is appropriate to test the user documentation during this phase. This will help uncover and eliminate documentation errors that could result in the delivery of inappropriate instructions to the end user.

Rollout phase. An example of a rollout phase input is the current systems description. When designing a new system, it is necessary to document any changes that must be made to the old system to accommodate the new structure. These details are included in the current systems description.
By being familiar with the inputs of each phase of an IT project, you and your team can be more confident that you have given adequate consideration to all required tasks in the development of your new system or product.

The Six Phases of an IT Project

Have you ever heard the saying "putting the cart ahead of the horse?" If you wanted to move your cart forward, having the cart in front would not really help. In order to make progress, you would want to put the horse ahead of the cart.

Performing tasks in sequence is also an important aspect of IT projects. The phases of an IT project, also known as a software development lifecycle, make up the framework of an IT project. These phases, which are listed below in sequence, will help you to address the business needs of your project, and better define the activities that will occur throughout the project's entire life span.

1. Planning
First, you must look at the information technology needs of your company. These needs are determined during the planning phase of an IT project by using an information-gathering technique such as a questionnaire.

Keep in mind that the objective must address and remedy an issue or a problem within the company. Once you define the objective, you can put an action plan into place. A description of the development approach that the IT team will take and the estimation of the overall cost are factors that are determined during this phase.

2. Analysis
The analysis phase is the second phase in the software development lifecycle. This phase focuses on the functions the end system will need to perform.

Once you establish the performance needs, you will be able to develop and formalize a more detailed description of the system. The use of business, data, event, and process models during the analysis phase will ensure that both the development team and the end user are on the same track.

3. Design
The third phase of an IT project is the design phase. In it, the plan for the end system is developed. This plan should accurately define the implementation of the project without actually executing the project.

4. Construction
During the fourth phase of the project, the IT team actually constructs the project or system. In this construction phase, the team uses a process map that identifies the procedures that need to be completed to duplicate the agreed-upon plan.

5. Testing
The testing phase is possibly the most critical of all the IT project phases. It is in this phase that the team determines which tests to implement to ensure that the system being produced will be of the highest quality.

6. Rollout
The final phase in an IT project is rollout. It is during this phase that the team begins the activities for releasing the finished product to the end user. Planning for the rollout activities can help the process progress more smoothly.

For example, if another system is already in place, your team will need to thoroughly review the conversion process to ensure the smooth transition from the previous system to the new one.

Every organization should have a structure in place to deal with processes, principles, and guidelines for every IT project. The phases described above can provide a useful framework for the effective development and completion of your next IT project.