Project Implementation Plan with Timelines and Milestones

A proposal should include a detailed and solution specific project implementation methodology. If there isn't none, this section compels you to devise a plan, a strategy according to requirements and spread it over different milestones and budgets available.

“An implementation plan is a document that outlines the steps your team should take to accomplish a shared goal or initiative. Implementation planning is the requisite of a strategic plan. The purpose of an implementation plan is to ensure that your team can answer the who, what, when, how, and why of a project before moving into the execution phase.”

This includes various phases:

Stages of implementation

Requirement/Initiation Phase

Understanding requirements for the project begins at the time planning begins for the project. All the basic requirements are actually part of the RFP documents, but to make sure that all the requirements are well-defined and complete, every project has a requirement-gathering phase, to avoid blind spots. The deliverables at the end of this phase are the business requirements documents which serve as references for development as well as quality assurance teams.

Design Phase

This is the phase in which “How to achieve what is required” is planned. Software requirement documents are transformed to the system design document which has a detailed and comprehensive set of specifications, referred to as the Design Specification. One or more designs are developed according to specifications. Depending on the subject of the project, the products of the design phase can include dioramas, sketches, flow charts, site trees, screen designs, prototypes, photo impressions and UML schemas. Only the proposals which fit requirements completely are chosen.

Implementation Phase

At this stage the proposed solution is transformed into the actual system. Building the platform based on the technical requirements. Proponents team of user experience designers will create the layout and key flows. There may be customer requirements for which some customization would be required. The developers start to code these customizations as per the signed-off requirements and the proposed design. All the other required setups are also completed in this phase. Along with coding, the developers prepare unit test cases for their parts of the application.

Testing Phase

It has two purposes: 1) to see if a solution meets the business requirements and 2) to catch errors and defects. The testing team, which is usually the same team which worked on the construct, determines requirements, configures a prototype, transfers knowledge and makes adjustments following testing and feedback.

During test case execution, all the defects are logged in a quality assurance management tool. Each defect goes through the defect life cycle before being fixed or rejected.

UAT Phase

Once the deployed application is passed by the testing team, User Acceptance Testing (UAT) is performed by the customer to verify the project requirements.

It is typically carried out by end users in an environment that closely models the real world production environment. A well-managed UAT process will give the project initiator, project team and end users confidence that the solution being delivered meets the requirements. The benefit of UAT is that there will be no surprises to the customer when the application goes live. A detailed account of requirement, schedule and participants is prepared.

Deployment Phase

The final phase sees that products are put into production i.e. working in the real environment. After the screens are finalized, and upon receipt of the proposed user acceptance criteria, a live demonstration is provided of how the flows will work and how users will use the system. The demonstration will show how the requirements described in the RFP will be met by the solution.