10th years of Anabatic Technologies is not a short term to work in IT world that has had major principle partners, supporting all the strategic medium scale up to large projects.
Therefore, in running the projects until reaching its success, it will need the project management to support all the project process life cycle. Based on Tech Republic article, I would like to share 10 Best Practices for Successful Project Management which will be grouped into 6 BIG parts as below:
- Planning
- Project Work Plan
- Project Management Procedures
- Managing Scope
- Managing Risk
- Managing Issues
Studies prove that most projects, especially large ones, do not end successfully. You might think that companies would be happy to just have their project finish with some degree of success. However, in spite of the odds, organizations also expect projects to be completed faster, on schedule and with higher quality. The only way that these objectives can be met is through the use of effective project management processes and techniques. Consider the size, complexity, and other characteristics of your project, and build the right project management processes to manage and control your project.
1. PLANNING
A. Plan the work by utilizing a project definition document.
There is a tendency for IT infrastructure projects to shortchange the planning process, with an emphasis on jumping right in and beginning the work. This is a wrong approach. The time spent properly planning the project will result in reduced cost and duration and increased quality over the life of the project. The project definition is the primary deliverable from the planning process and describes all aspects of the project at a high level. Once approved by the customer and relevant stakeholders, it becomes the basis for the work to be performed. For example, in planning an Exchange migration, the project definition should include the following:
- Project overview: Why is the Exchange migration taking place? What are the business drivers? What are the business benefits?
- Objectives: What will be accomplished by the migration? What do you hope to achieve?
- Scope: What features of Exchange will be implemented (i.e., e-mail, chat, instant messaging, conferencing)? Which departments will be converted? What is specifically out of scope?
- Assumptions and risks: What events are you taking for granted (assumptions), and what events are you concerned about? Will the right hardware and infrastructure be in place? Do you have enough storage and network capacity?
- Approach: How will the migration project unfold and proceed?
- Organization: Show the significant roles on the project. Identifying the project manager is easy, but who is the sponsor? It might be the CIO for a project like this. Who is on the project team? Are any of the stakeholders represented?
- Signature page: Ask the sponsor and key stakeholders to approve this document, signifying that they agree on what is planned.
- Initial effort, cost, and duration estimates: These should start as best-guess estimates and then be revised, if necessary, when the workplan is completed.
2. PROJECT WORK PLAN
B. Create a planning horizon.
After the project definition has been prepared, the work plan can be created. The work plan provides the step-by-step instructions for constructing project deliverables and managing the project. You should use a prior work plan from a similar project as a model, if one exists. If not, build one the old-fashioned way by utilizing a work-breakdown structure and network diagram.
Create a detailed work plan, including assigning resources and estimating the work as far out as you feel comfortable. This is your planning horizon. Past the planning horizon, lay out the project at a higher level, reflecting the increased level of uncertainty. The planning horizon will move forward as the project progresses. High-level activities that were initially vague need to be defined in more detail as their timeframe gets closer.
3. PROJECT MANAGEMENT PROCEDURES
C. Define project management procedures up front
The project management procedures outline the resources that will be used to manage the project. This will include sections on how the team will manage issues, changes of scope, risks, qualities, communications, and so on. It is important to be able to manage the project rigorously and proactively and to ensure that the project team and all stakeholders have a common understanding of how the project will be managed. If common procedures have already been established for your organization, utilize them on your project.
D. Manage the workplan and monitor the schedule and budget
Once the project has been planned sufficiently, execution of the work can begin. In theory, since you already have agreement on your project definition and since your work plan and project management procedures are in place, the only challenge is to execute your plans and processes correctly. Of course, no project ever proceeds entirely as it was estimated and planned. The challenge is having the rigor and discipline needed to apply your project management skills correctly and proactively.
- Review the work plan on a regular basis to determine how you are progressing in terms of schedule and budget. If your project is small, this may need to be weekly. For larger projects, the frequency might be every two weeks.
- Identify activities that have been completed during the previous time period and update the work plan to show they are finished. Determine whether there are any other activities that should be completed but have not been. After the work plan has been updated, determine whether the project will be completed within the original effort, cost, and duration. If not, determine the critical path and look for ways to accelerate these activities to get you back on track.
- Monitor the budget. Look at the amount of money your project has actually consumed and determine whether your actual spending is more than originally estimated based on the work that has been completed. If so, be proactive. Either work with the team to determine how the remaining work will be completed to hit your original budget or else raise a risk that you may exceed your allocated budget.
E. Look for warning signs.
Look for signs that the project may be in trouble. These could include the following:
- A small variance in schedule or budget starts to get bigger, especially early in the project. There is a tendency to think you can make it up, but this is a warning. If the tendencies are not corrected quickly, the impact will be unrecoverable.
- You discover that activities you think have already been completed are still being worked on. For example, users whom you think have been migrated to a new platform are still not.
- You need to rely on unscheduled overtime to hit the deadlines, especially early in the project.
- Team morale starts to decline.
- Deliverable quality or service quality starts to deteriorate. For instance, users start to complain that their converted e-mail folders are not working correctly.
- Quality-control steps, testing activities, and project management time starts to be cut back from the original schedule. A big project, such as an Exchange migration, can affect everyone in your organization. Don’t cut back on the activities that ensure the work is done correctly.
If these situations occur, raise visibility through risk management, and put together a plan to proactively ensure that the project stays on track. If you cannot successfully manage through the problems, raise an issue.
To be continued…
Source : Tech Republic Article
by Hendra Halim – Head of Project Management Office (Infrastructure Team)
You can follow him on his twitter @takhada
Anabatic Technologies Blogs 