Question

Develop an imaginary project charter for a web development project. Assume you are going to develop a website from scratch for a small retail business of your choosing. Assume the web site will include a home page with links to information about products and services. It will also include a bulletin board, chat room, and provide information about the company and how to contact people in the company. Assume you are a self-employed software developer and your client is the owner and founder of the business. The owner wants a copy of the charter to circulate among her employees so they can be made aware of the project and prepare to support it. Use the format below.

Project Charter
Project Title:
Project Start Date: Projected Finish Date:
Budget Information:
Project Manager: Name, phone, e-mail
Project Objectives:
Main Project Success Criteria:
Approach:
Roles and Responsibilities:

Role
Name
Organization/
Position
Contact Information

Sign-off: (Signatures of all above stakeholders. Can sign by their names in the table above.)
Comments: (Handwritten or typed comments from above stakeholders, if applicable)

Answer 1

Find attached with this answer

Step-by-step explanation:

Common risk points in web projects

Schedule, budget, and scope of work: Let these drift and you’re doomed.

Quality assurance: qa becomes a problem when other schedules run long but the launch date doesn’t change and qa testing is squeezed into the last few days before the site goes live.

Content development: This is the most commonly underestimated factor in web publishing—ask any editor.

Application development: Web projects rarely fail because an application does not function properly. Instead they fail because the intended audience hates to use it or doesn’t find its features useful.