I commited the information below to report PDU of PMI. ^_^.
In this paper, the author introduces his good experience of project management. I list it below with my learning and understanding in our development.
- Be Agile
Learning: as a member of software development, we moved from water flow to agile, we involved customer in daily work, we can go to the correct direction with the customer involvement and fix it faster if there are any problems in our development.
- Do not Micromanage
Learning: the project manager is the leader, he or she shall not take more time in small/tiny activities like how to implement a function. As a project manager, you assign the responsibilities to individual team members, e.g. architect to control the technical topics.
- Keep Improving Your Project Management Practice
Learning: when a new method you learn, you shall apply to your daily work, yes, the adaption shall take. The management way shall change according to the environment e.g. the culture of company, the guider line of company.
- Ongoing Planning
Learning: the plan change all the time because the plan is very draft at the beginning of project, it may just have when to achieve the quality gate and when to release. The plan shall be more specify as the moving of project. But the plan shall keep the consistence. Otherwise, the time and quality cannot be controlled in a good way.
- Work with a Sense of Urgency
Learning: the project plan shall be urgent to make all team members contributes all the power to the projects. The weekly all temp project meeting, the daily standup meeting can move the project smoothly.
- Visualise and Communicate all Project Deliverables and Activities
Learning: to present the achievements and the progress to all team members or whole company, it can give the team member more sense of urgency. Kanban is a good method to present.
- Complete Deliverables Step-by-Step
Learning: in few years ago, we release software/firmware when project almost done, now we release the software in each sprint. And the test team can be involved early. In this development mode, the deliverables are tested and verified early, it reduces the risk. Any bugs or misunderstanding requirements can be soon changed.
- Healthy Risk Management
Learning: now we don’t have a risk officer, the role is taken by project manager. Next time we can take this to improvement.
- Open Communication
Learning: Open communication, it let you to hear different voices, and the project manager is not the expert of all areas. Different solutions/voices need to balance to achieve the time, budge and quality.
- Never Lose Sight of the 3-Factors: Time, Budget, and Quality
Learning: The project manager's main role is to keep all team members aware of these big three - Time, Budget and Quality.
The paper released at https://www.projectsmart.co.uk/10-rules-of-highly-successful-project-management.php