WEB Project Manager manual-Project Manager's work content

WEB Project Manager manual-Project Manager's work content

I. Objectives of the Project Manager
1. meet the different needs of project stakeholders.
Clearly and clearly understand the needs and expectations of each project stakeholder and give it to others.
Project stakeholders include: project team members and members outside the project team (such as department managers and customer service personnel of each department ).
2. Ensure that the development project is completed on time and in good quality.
2. Responsibilities of the Project Manager
1. Establish an effective process to ensure the smooth development of the project.
2. Develop a detailed project plan.
3. Track and promote the project as planned.
4. Actively resolve problems and conflicts in the project process.
5. mobilize the enthusiasm and creativity of the development team to promote the continuous growth of team members in the project process.
Iii. Specific work of the Project Manager
1. Early Stage of the project
Technical feasibility analysis, technical evaluation, cost assessment, and risk assessment for the project.
Discuss requirements with Demand Side Representatives, clarify the objectives and values of the project, and determine the scope, functions, and priorities of the project.
. Set up a project team, especially clarify the key person of the project (persons who have the right to decide the product ).
. Project kickoff meeting.
Generally, project members include: Project Manager, architect, Technical Manager, Product Manager, Development Engineer, DBA, test engineer, Requirement Analysis engineer, UI, copywriting, SQA, SCM.
Stage outputs: final requirement documents after confirmation
2. Analysis and Design Stage
. Develop the project progress plan and break down tasks (WBS ).
. Resource application-development resources, test resources, and design resources involved in the project.
. Database design.
. System design.
. Document (including UC, demo, TC, etc.) Review Meeting
Stage outputs:
(1) User case
(2) demo
(3) System Design Documents
(4) Database Design Documents
(5) User case and other document reviews
3. execution stage (development and testing)
Prepare the development environment and test environment.
. Track and promote the project as planned.
. Report the progress of the project, usually in the form of a weekly report.
Evaluate the project's stage results to ensure the quality of the stage, including code review and SQL review.
. Control and manage demand changes.
. Manage project risks.
. Customer Acceptance and feedback during testing.
4. Release Phase
Develop a project release plan.
. User training.
. Publish online.
5. Post-release monitoring
. Data Monitoring (log, server status ).
. Bug fix and improvement.
6. End Stage
. Project Summary meeting.
. Product Delivery.