For more than a couple of decades, CBA has been involved with client implementations of Primavera applications. One would think after so much interaction with many different organizations that we have seen it all. Well, we have seen a lot, but certainly not all! We have worked with very large companies that had only a few users in one department and have worked with one person consultants who build schedules for very complex large projects for many different clients. We have worked for small, medium and large firms that want to track every project regardless of size – and other organizations that only want to track projects of a certain size or larger. Some are focused on documents and contracts, others on schedule, cost and resource tracking, still others on portfolio selection – and various combinations of those.
What I find interesting is some clients seem to know exactly what they want to do, and more importantly, why they want to do it. They have a compelling story of what their current problems and pains are, and the circumstances that led them to realize the need for a portfolio project management or document management solution. Other clients are complying with the request of an important client or meeting a contractual obligation. No matter what the reason, CBA is interested in helping organizations achieve their project selection and execution goals.
Implementations can take on various shapes and sizes. Some are simple and quick; install, train, advise and go. Others are much more involved with process and procedure development, custom user guides, dozens of template projects, and integration to more than one corporate application for cost, maintenance management or HR, and on-going mentoring. Some focus on complex independent projects for individual end customers, others focus on cash flow of an entire capital portfolio and still others are document and work-flow dependent engagements.
Our job is to “right size” your implementation to meet the current needs of your organization now and allow for meeting future goals. In order to right size your implementation it is important for us to understand what your company wants to accomplish and why. We also need to understand the capabilities and project controls maturity of the team you are deploying the solution to. This helps us understand the urgency and priorities, which in turn allows us to help focus the team on “why we came to drain the swamp”. Knowing the underlying reasons of why a team wants to do something is sometimes more important than knowing the industry or the details of how projects are accomplished in a specific organization.
We believe the success of an implementation is defined as putting a solution in place that accomplishes the objectives as identified by the organization within the desired (realistic) time frame and is adopted by the user community. Additionally the solution should remain in place and mature over time. We have accomplished this result most often when all of the following occurred:
- We were able to match the complexity of the solution with the skill sets of the team tasked with putting it in place
- There was a client organization responsible for the design and on-going execution of the solution
- Users were mentored until they have a firm grasp on the process
- Management of the client organization utilized the information gained from the team in a manner that showed they used it to make business decisions
Sometimes, this means phasing in deployment of all desired requirements over a period of time, initially incorporating the most critical subset of them based on what we mutually agree can be accomplished and carried out by the user community. For example, an organization may ultimately want to have fully resource and cost loaded schedules with Earned Value metric reporting on all projects over $5MM. What may be realistic is to begin with an approach of getting all of the projects identified within the database using a simplified template approach based on type of project, incorporating common milestones and establishing relationships between interdependent projects. Once the staff is used to creating, baselining and updating the schedules, they will naturally suggest modifications to the templates making them more accurate and granular. At this point, the concept of applying budgets, actuals and remaining forecasts into the process is ready to be introduced and upon familiarization with that process – the concept of EVMS reporting can be applied.
CBA wants your projects to win and your goals to be achieved. When you engage us, let’s be sure to discuss right-sizing your implementation to ensure its success for the long haul.read more