Making PPT, designing and drawing beautiful charts are necessary skills for project managers, and they are the most frequently used skills in their work. Using diagrams to visualize processes, concepts, and work plans will facilitate effective communication and understanding.
I used Edraw as a tool to draw some examples in the book, which is a review of project management knowledge and a training of drawing skills.
1. Start the workflow
2. Start the work plan
3. Project management plan
4. Project organization structure
5. Division of responsibilities
| Organization/Role | Duties and responsibilities |
|---|---|
| The project manager | Overall responsibility for the project, including project objectives, scoping, planning, organizing and assigning project tasks, controlling project progress, and regulating the working atmosphere of the project team |
| PMO | Responsible for developing and monitoring the project plan, coordinating project resources, communicating with relevant organizations inside and outside the project, and managing daily project affairs to ensure the project is implemented as planned |
| The quality group | Responsible for process and documentation standards, daily management of repository deliverables, change and defect management. Responsible for the review of deliverables and the audit of project process |
| The panel | Guide the development of project plans and identify technical and operational solutions; Review key delivery; Solve the difficult problems in the process of project implementation; Provide early warning information on project risks. Review the variance specification and requirement function specification |
| Business group | Be responsible for business requirement analysis according to project plan, cooperate with development and test, and finally be responsible for acceptance test |
| The development team | Responsible for application system, version automatic upgrade system, external interface development and testing, responsible for system knowledge transfer, ensure that the system team can eventually take over the system |
| Transform group | Responsible for switching between new and old systems, including switching scheme of new and old systems, data migration, business process transformation and personnel training |
| System group | Responsible for determining the configuration of software and hardware environment of the project, assisting in planning and purchasing, and responsible for installation and configuration; Provide hardware and software environment for the work of other groups; Ultimately responsible for production system operation and maintenance management |
6. Agenda for the project kick-off Meeting
- Introduce the agenda and guests
- Introduce project objectives, phase plan, and management methods
- Publish project organization charts and appointments
- Key roles identify responsibilities and make commitments
- Senior leaders of both sides make project mobilization speeches to motivate and boost morale
- Leaders of all relevant departments expressed their support for the project
The contents of the launching meeting are summarized into the Project Launching Meeting Minutes. The minutes record the initiation process of the project, the commitment of project team members, and the clear statement of leaders at all levels. This document was released as the first official announcement from the project team, announcing the successful launch of the project.
7. Differences in focus lead to different ways of thinking
Business people focus on how the system supports the business process, and the requirement behind it is to “achieve the business goals.” Technical people focus on sound technical solutions, and the requirements behind them are “effort,” “difficulty of implementation,” and “system performance.”
