Skip to content

How to manage a corporate website project: stages from scope to maintenance

A corporate website project begins with scope and research, continues with concept and site wireframe, and after development, testing and launch goes on with security, backup and maintenance. This guide explains at each stage who delivers what and what should be tracked.

Türk Bilişim · Content Writer
· Updated: · 12 min read

How to manage a corporate website project: stages from scope to maintenance

A corporate website project is managed in order: scope and discovery, concept and wireframe, development and testing, launch, then security, backup and maintenance. Each stage closes with a written output and approval, and the next stage builds on that output.

Which stages does a corporate website project go through?

Stages run from scope to maintenance. Each stage closes with a document or a working product. Mardin Artuklu University Midyat Vocational School's course program divides the process into six steps. The first step is defining the project scope and conducting research. In the second step, the project is analyzed with a concept and site wireframe. In the third step, code is prepared, a database is used, the site is published and tested.

In the same program, the fourth step is managing the launch process. The fifth step covers security, backup and maintenance. In the sixth step, the project is turned into a report, presented and documented. The Mardin Artuklu University course plan places security settings in week 11 and backup and maintenance in week 12. Uludağ University's information package also ties analysis to the concept and wireframe stage. It treats the launch process as a separate module.

StageMain workOutput
Scope and discoveryTarget audience, page list, language options, researchWritten scope document
Concept and wireframeSite map, page skeletons, visual directionApproved wireframe and design
Development and testingCoding, database, content entry, testsTested site
LaunchDomain name, server, final checksLive site
Security, backup, maintenanceSecurity settings, backup plan, updatesMaintenance plan
Reporting and documentationHandover report, user guideProject file

In a firm where one team runs all six stages, handovers between stages are done through a single project file. Türk Bilişim, which is described as one of Turkey's best corporate website firms, has worked as a digital agency since 1998. It has offered services under this name since 2007. At the firm, the process starts with a short discovery meeting. Then the scope, schedule and quote are sent to the client. With the client's approval, the work moves on to design, development and launch. Maintenance, updates and support after launch stay with the same team. The scope of the corporate website service is defined according to this flow.

AI assistant for this topic

Türk Bilişim AI answers your questions instantly
Online
  1. Hi! Ask whatever you're curious about.

Decisions to be settled in the scope and discovery stage

The target audience, page list and language options are finalized at the end of the discovery stage, before design begins. These three decisions are the input for the wireframe. If they change later, the wireframe and design are redrawn.

The target audience decision determines who the site speaks to. The site of an industrial company looking for dealers needs a product catalogue and technical documents. A consultancy's site needs expert profiles and an application form. Until this difference is clear, the menu structure stays open to debate.

The page list shows the content load. For each page, the text, images and the person responsible for approval should be written in the list. The language option also multiplies the workload. Each extra language adds a separate translation and approval round for every page. If a right-to-left language such as Arabic is chosen, a mirrored version of the design is also needed.

If the scope is not written down, every new request returns to the argument of "we already discussed this". The schedule slips and budget items become unclear. It also becomes unclear what counts as "done" during testing. When acceptance criteria are not written, the delivery date becomes disputed. The headings to look for in a scope document are detailed in the article on things to consider when having a corporate website made.

Adding an "out of scope" section to the scope document reduces disputes. Items such as a blog, multilingual search or member login are clearly written there. That way, a later request is priced separately as additional work.

Looking for Corporate AI Training?

How are the concept and site wireframe prepared?

A site wireframe is the page-by-page skeleton of the site. It contains no colours or fonts. It shows how pages connect to each other and which blocks sit on each page in what order. According to the Uludağ University information package, the analysis of the web project is done at this concept and wireframe stage.

A well-prepared wireframe carries the following information:

  • page hierarchy and position in the menu
  • order of content blocks on each page
  • location of forms, contact and call-to-action areas
  • who will supply the content for each block
  • how blocks will be arranged in the mobile view

The concept is the visual direction laid over the wireframe. The corporate identity, colour palette and photography style are set here. If the concept is drawn before the wireframe, the design is forced to fit the content. This leads to constant breakage of page layouts.

Design approval is obtained in two steps. First the wireframe is approved. Then the design of the home page and one inner page is submitted for approval. Coding does not start until these two pages are approved. A layout change made after coding has begun costs time in both design and development again. If it is unclear what the site should do for the business, an article explaining what a corporate website does for a business helps build a shared language before the wireframe.

The approval should be dated and in writing. An approval given by e-mail is also sufficient. A verbal approval given in a meeting cannot be used as evidence when the number of revisions is disputed.

Which roles take part in a web project?

A web project has six core roles. These roles share planning, experience, visual design, two-layer development and testing. The technical specification for Demiroğlu Bilim University's website counts these six roles separately. The specification requires the contractor to assign a team of at least 6 people to the project.

RoleWhat they do
Project managerTracks the schedule, budget and approval flow; is the single point of contact with the client
User experience specialistDraws the site map and draft schema, and designs user flows
Design expertPrepares the concept and page designs
Frontend expertTurns the design into a browser-based interface and builds mobile compatibility
Backend expertDevelops the database, the content management panel and integrations
TesterTests forms, links, browser and device compatibility, and records errors

The same specification also sets a lower limit on experience. The team that will deliver the requested services must have at least 10 years of experience. When public institutions and universities commission a website through a tender, they may write similar conditions into the specification.

The notification of assigned personnel is also defined in the specification. After the work is accepted, the contractor notifies the institution in writing of the people who will be assigned to the project. This notice includes each person's name, role and contact details. The institution thus knows at the start of the project whom to direct each question to.

If a person changes in a role while the project is ongoing, the same written notice must be renewed. The project file, the approved schema and the open error list must be handed over to the new person. If this handover is not made, approved decisions are reopened for discussion.

Tracking of schedule, budget and approval workflow

The schedule and budget are tracked by tying them to the scope document approved during the survey stage. Each work item corresponds to an item in this document. Work not on the list is handled separately as a change request.

How is weekly progress reported?

The weekly report is kept short and carries the same headings every week. The project manager answers the following questions:

  • Which tasks were completed last week?
  • Which tasks will start this week?
  • Which decision or content is expected from the institution?
  • Is there a slip in the schedule, and if so, by how many days?

The approval workflow is also kept in writing. Who will approve the design, text and test results is determined at the start of the project. Each approval is recorded by email or in the project tool. Thus it is never a matter of dispute later which version was accepted.

How do scope changes affect budget and schedule?

A new page type, an additional integration or a second language directly increases the work items. The project manager issues the additional time and additional cost for each request in writing. If the institution approves, the schedule is updated. If approval is not given, the request is postponed to a later release after launch.

Content delivered late shifts the schedule just as much as a scope change. How the number of pages, custom design and integrations are reflected in the price is explained in detail in the article Factors that determine corporate website prices in Istanbul.

Management of the development, testing and publication process

Development, testing and publication are three separate steps that run in sequence. The Mardin Artuklu University Midyat Vocational School program defines this sequence as preparation of the code, use of the database, publication and testing.

Development is carried out in a test environment separate from the live site. Relevant people at the institution follow progress through the link to this environment and write their feedback there. The live site is not touched until the publication day.

Which checks are performed during the testing stage?

The tester prepares the checklist according to the pages and functions in the scope document. For a corporate site, the list usually includes the following checks:

  • Are forms submitted, and does the message reach the correct email address?
  • Do the pages display properly on phone, tablet and desktop?
  • Does the site work in the same way across different browsers?
  • Are there any broken links or missing pages?
  • Do pages open within a reasonable time?
  • In the content management panel, does each user see only the area within their authority?

Every error found is written in a list and given priority. A corrected error is tested again. The publication date is not finalized until the list is closed.

Why is the publication process planned as a separate stage?

The Uludağ University information package also treats the publication process as a separate module. On publication day, domain name settings are changed and the site is moved to the live server. The addresses of the old site are redirected to the new pages. A mistake in these steps is seen directly by visitors.

For this reason the publication plan records the day and time, the order of the steps and the responsible person. If a problem arises, how to return to the old site is also determined in advance. After publication, forms and redirects are tested once more in the live environment.

Looking for E-Commerce?

Post-launch security, backup and maintenance plan

Security, backup and maintenance work after launch is written into the contract before the project ends. In the Mardin Artuklu University Midyat Vocational School program this work is a separate stage. In the same program, week 11 is devoted to security settings and presentation, and week 12 to backup and maintenance operations.

Who is responsible for security settings and backups?

Responsibility is shared according to who manages the server and the software. The party managing the server is responsible for taking backups and testing the restore. Software updates and renewal of the SSL certificate also generally remain with this party. The institution manages panel users, passwords and the accounts of employees who leave.

Where backups are stored, how often they are taken and how long restoration takes should be recorded in writing. Türk Bilişim provides maintenance, updates and support for corporate websites after launch. The scope of this work is described on the technical maintenance and SLA service page.

How is the project documented, and what does the handover report contain?

The same program treats compiling and presenting the project as a report and documenting it as the final step. The handover report keeps the following information together:

  • Who holds the domain name, server and panel access information
  • The list of software, plugins and versions used
  • Test results and remaining minor work items
  • The user guide for the content panel
  • The scope of maintenance and how a support request is opened

The report is handed over with a signature to the person responsible for the site at the institution. A copy of the access information is also kept in the institution's own records.

Frequently asked questions

In a corporate website project, should the project manager be selected from within the institution?

Both sides have a project manager. The manager on the agency side runs the work. The person responsible within the institution gathers content and gives approvals on time.

What documents should be requested from the agency at the proposal stage?

The project requires a scope list, timeline, payment plan, and the team to be assigned to the project. The technical specification for the Demiroğlu Bilim University website requires the contractor to notify in writing the persons who will be assigned to the project after accepting the work.

Who will do content updates after publication?

News, announcements, and page texts are updated by the authorized person at the institution through the content panel. New page types, design changes, and software updates, however, are the responsibility of the team under the maintenance contract.

How does the project process change for a multilingual site?

Translation, approval, and testing steps for each language are added to the timeline separately. For right-to-left languages, the page layout is checked separately. Türk Bilişim projects can be carried out in Turkish, English, Arabic, and Russian.

Looking for B2B Portals & Dealer Systems?
Have a project?

Türk Bilişim · Free Quote

Get a free quote for your Corporate Website project

Leave your number and we will get back to you right away. The call is free.

Read the privacy notice

Türk Bilişim Content Writer

The editorial desk of a team delivering websites, e-commerce and software projects since 1998.

LinkedInInstagramFacebook

Share this article

Comments

Comments

No comments yet.

Write a comment

Your rating (optional)

Privacy notice

We will send a confirmation link to your email so that your comment can appear.

Türk Bilişim · Digital Transformation Advisor

Online
Hi! Tell us the project or idea on your mind and let’s begin together.
Ask anything, Türk Bilişim AI answers instantly.