Frey Moon. Project Management. July 21st , 2021.
This is the very beginning of the project where you begin to brainstorm about what you think will need to happen in order for the project to come together. For example, using our wedding planning theme, we know that there are several things that need to occur in order to make this wedding come together seamlessly...so you begin listing them. There must be somewhere to have it, someone to open and close the facility, catering must be determined, what is the anticipated budget or cost that the family is looking to spend, etc. In fact, this can just be a list of items or bullet points that you know will need to be broken down more granularity later. Remember, this is just brainstorming to see what the main "things" are that need to occur for the project to be done correctly. This is where we look at how to begin adding shape to this wedding. We need to somehow bring it from conceptualization to reality, from thought process to paper. This is the rough framework of what we know will happen or at least what we think needs to happen. The planning phase is critical for getting started, but not critical for being 100% correct. We will refine as we go.
The development of project management capabilities in organizations, simultaneously with the application of information management systems, allow enterprise teams to work in partnership in defining plans and managing take-to-market projects by synchronizing team-oriented tasks, schedules, and resource allocations. This allows cross-functional teams to create and share project information. However, this is not sufficient, information management systems have the potential to allow project management practices to take place in a real-time environment. As a consequence of this potential project management proficiency, locally, nationally or globally dispersed users are able to concurrently view and interact with the same updated project information immediately, including project schedules, threaded discussions, and other relevant documentation. In this scenario the term dispersed user takes on a wider meaning. It not only includes the cross-functional management teams but also experts drawn from the organization's supply chain, and business partners.
This is where the activities and tasks are being completed according to the start and stop dates. You have moved out of the planning phase and into the executing (doing) phase. Here is where you, as the project manager, track others progress in completing their assigned tasks. Remember, even though you are not responsible for completing the tasks themselves, you may need to do some hand holding to help ensure that others are completing their tasks accordingly. Completion of the tasks, activities, milestones, and ultimately the entire project falls on you.
Once your project is underway and you have an agreed plan, you will need to constantly monitor the actual progress of the project against the planned progress. To do this, you will need to get reports of progress from the project team members who are actually doing the work. You will need to record any variations between the actual and planned cost, schedule and scope. You will need to report any variations to your manager and key stakeholders and take corrective actions if the variations get too large.
Some of the stages in implementing a project are quality control, progress control, change control and risk management. The first aspect we will discuss is risk management, as once you have planned the project it is important to assess any factors that could have an impact upon it. 'Risk' in this case is considered to be anything that could negatively impact on the project meeting completion deadlines. For example losing team members due to illness or attrition, not having taken team members' annual leave into consideration, the possibility of having to retrain new team members, equipment not being delivered on time or contractors going out of business. A risk log is used to record and grade risks and carries an associated action plan to minimize the identified risk. Issues management is an associated area and refers to concerns related to the project raised by any stakeholder. This phase also involves the Project Manager in quality control, whereby regular reviews are made in formalized meetings to ensure the 'product' that is being produced by the project is reviewed against specific pre-defined standards.
Think of this as the winding down phase. Tasks, activities, and milestones are almost all completed. The project is officially coming to an end...maybe there are some tasks still being performed to ensure that everything is running accordingly, but for the most part the project is coming to a close. This will usually be a fairly low resource constraint for you. You will be updating any necessary project materials and making sure that the deliverable match the Charter that you defined this project by. This is also where resources will go back to their usual daily activities as was normal before your project began.
A project is a temporary and one-time exercise which varies in duration. It is undertaken to address a specific need in an organization, which may be to create a product or service or to change a business process. This is in direct contrast to how an organization generally works on a permanent basis to produce their goods or services. For example the work of an organization may be to manufacture trucks on a continual basis, therefore the work is considered functional as the organization creates the same products or services over-and-over again and people hold their roles on a semi permanent basis.
Top Ten Posts
Any content, trademark/s, or other material that might be found on this site that is not this site property remains the copyright of its respective owner/s. In no way does LocalHost claim ownership or responsibility for such items and you should seek legal consent for any use of such materials from its owner.