Many companies have policies, procedures, and training for a uniform approach to project management. One of the major reasons for poor project uniformity is the proposal which is the foundation for the project. Whether you are a beginner or an experienced project manager, project management standards and procedures, if followed consistently would benefit you to achieve your objectives better. However some revisions are required for better control of the project.
Some project management ideas that needs amendment are
- The idea that “all projects are like mine”.
- Project management is applicable in software development projects only.
- Manage the project by email. But there are other better project management tools. In large organizations with dispersed offices where security conscious doesn’t allow you to run non-standard software. This is something a project manager can control.
- To have longer meetings -Cut down the length of your meetings, and adhere by time strictly. By clearly defining the meeting agenda and communicating what would be covered and also what is not be covered in that meeting can set the right expectation and result in cutting it short and to the point.
- Only hire local people to work onsite- This actually makes sense if you take it literally. It is not recommended for an individual to spend hours in commuting. And it is applicable to all kind of jobs, including project management.
- Try to stick to the project management plan, at any cost. Describe tasks very loosely and wing it. Complete every project brief or task description and communicate with the team in the initial stage of the project.
Generally project manager expect the team to describe the detailed tasks in early stages of the project. A program manager said, you’re building the factory at the same time as your building the cars, but businesses keep this one alive by saying they are doing agile (and not in software development).
Communications are not always under the control of the project manager. Identify the correct set of communication channels. Most organizations focus on documentations where lessons leaned on a completed project are listed. This helps the new project to get started in the right direction and reduce the need for too many meetings and minimize the time spent on requirement gathering. In fact communication is never fully under control of the project manager.
The project should be defined up front with enough context to understand the actual goal and objective. Plenty of projects fail because they are trying to stick to an arbitrary WBS (Wok Breakdown Structure) template rather than trying to deliver the needed capabilities. This requires a balancing that will differ with each project. Change may be needed in a project. Sticking to the plan is a good practice but practically changes must also be entertained. There are various reasons, internal and external factors that results in changes. The key to successful project in spite of unplanned or emergency changes in the project is that all stakeholders know about the change well in advance. A strong change control board with solid communication plan can be of great help.
- Top 45 Fresher Java Interview Questions - March 9, 2023
- 25 Free Practice Questions – GCP Certified Professional Cloud Architect - December 3, 2021
- 30 Free Questions – Google Cloud Certified Digital Leader Certification Exam - November 24, 2021
- 4 Types of Google Cloud Support Options for You - November 23, 2021
- APACHE STORM (2.2.0) – A Complete Guide - November 22, 2021
- Data Mining Vs Big Data – Find out the Best Differences - November 18, 2021
- Understanding MapReduce in Hadoop – Know how to get started - November 15, 2021
- What is Data Visualization? - October 22, 2021