3.2 Tasks Completed During Project Development

During Project Development, IT executes the plans identified in the design document, QA develops test procedures, Documentation begins developing manuals and help files, and, if applicable , the Project Manager reviews vendors .

Activities of IT, QA, and Documentation

Using the design in the Design Document, IT develops the project. This development may include purchasing prototype hardware and software or installing software that will be test run before existing systems are cut over. Additionally, IT is responsible for developing and running an initial test to ensure quality. QA develops test procedures and sample tests based on the test plans developed in Phase 2. As sections of the project are created, IT starts delivering these completed sections to QA so they can begin early testing. Documentation uses the Doc Plan as the basis for developing user documentation. IT provides Documentation with any relevant notes that project developers have written to explain what they are developing. If IT is writing software or interfacing software with company applications, they should provide Documentation with access to early applications. This allows Documentation to review the project and to begin developing the documentation.

Project Manager and IT Identify Possible Vendors

Many times projects are created based on a vendor s recommendation or industry trends. It is wise to develop projects without bias ”that is, identify your user and company requirements, design the project based on these requirements, and then look at possible vendors solutions. The downside to waiting until Phase 3 to identify the vendor is cost and fit. IT may come up with a design that no vendor can fulfill, or existing solutions that fit the company s needs may be too expensive. The upside of waiting is that solutions not considered earlier may now be considered , the solution will meet the needs of the end user and the company, and time and money won t be wasted developing a solution that doesn t meet these needs. If it is impossible to find a solution that fits, it is important to look at the prioritization outlined in the Feature/Functionality Report. The IT and Project Manager should create a matrix using the Feature/Functionality List, then plot which vendors solutions provide which features. The solution that meets the highest number of ˜ ˜A priority features is usually the best candidate.

Business Development and QA Plan for Beta

After QA tests the project but before the full rollout, the project is given to a select group of end users; this is called beta testing. The plan for beta testing is created during Phase 3.

3.2 in a Nutshell

At the Phase 2 review, the Project Manager presented the project s design, its features/functionalities, any changes from project concept to actual project design, and any updates to the end-user positioning. He also presented the planned costs, the integrated schedule, and the baseline costs. In Phase 3, the team turns their plans into deliverables.

• IT executes on the Design Document.

• QA develops test procedures.

• IT and Project Manager choose vendors.

• The Beta Plan is created.

  Tip  

  Wait until the design process is over before choosing a vendor. This way your final solution will better fit company and user needs.