Back-end Process

From WebFocus Wiki Site
Jump to: navigation, search

Flowchart-production.jpg

Gathering of Materials

Gathering of materials must be done by the Project Coordinator. Said materials must be 100% complete before the project can be scheduled for the design. The Coordinator must also provide the project's design template and a design questionnaire fully accomplished by the client.

Input JO Details

The Job Order must be provided by the Web Consultant. This file contains the project scope and basic information about the client. Meanwhile, the PHP Collab is the management software used by the Production team to monitor each project's status.

Assignation of Project

Each project will be assigned to a team. This team will consist of Project Coordinator, Web Designer, Web Developer, Quality Assurance, and Web Consultant.

Project turnover for the Design

The Project Coordinator must turn over the project to the Web Designer. All materials, special instructions, or requests by the client must be properly and clearly relayed to the Designer. In the absence of the coordinator, Web Consultant can turn over the design details.

Modification / Revisions of Prototype

During the Design Phase, project revisions and modifications within the design template is possible and allowed. However, the Production Team must provide second design if the client requested for another template option. Two template option will be allowed on each project, but the second design will be upon request of the client. In addition, all revision or adjustment must be posted on the project management software which is PHP Collab. All revision turnover or mentioned verbally or through personal message will not be entertained.

Update Project Status

To keep everything documented, any progress with the project's status must be reflected in the PHP Collab. This will serve as a monitoring guide to measure the performance of each team member and their client coordination.

Functionality Testing

Each project must undergo a testing. Projects will be tested according to their scope. Here are some of the guidelines:

  • Aesthetics checking (typographical error, design consistency, and link validity)
  • Functionality checking
  • Security Penetration Test
  • Vulnerability Scanning
  • Browser Compatibility
  • User Interface (User friendly)
  • Database Indexing

Modification/ Revisions

During the project's Development Phase, any revisions or adjustments will be entertained as long as it is not about the project's template design. Any modifications or additional requests pertaining to its design will fall under a piecemeal.

Project Presentation

The project will be presented to the client the soonest it passed the Testing Phase. The presentation includes a training on how to manage the site's CMS. This must be done by the Project Coordinator, with or without the Web Consultant.

Update Project Status

To keep everything documented, any progress with the project's status must be reflected in the PHP Collab. This will serve as a monitoring guide to measure the performance of each team member and their client coordination.

Project Uploading

Before a project can be launched, the client must first submit a fully-accomplished Project Sign-Off Form. This will serve as a proof that the team has completed the project scope and has therefore met the client's expectations. Although, the Sign-Off Form has a clause stating that should there be a bug found during the project's warranty period, the production team shall fix it immediately. On the other hand, should the client modify the existing codes and try to fix the bug, the project's warranty will be automatically voided.