This document describes a template for an activity list based on a project WBS, which is typical on the development of new products for the electromechanical industry like industrial automation equipment. The purpose of this document is to offer an activity list based on the key disciplines that distinguish a development of a new product for the electromechanical industry.
Do you struggle over the finish line with a gasping breath, or do you stride easily past it with the satisfaction of a job well done? Finishing well is just as vital as anything else on the project, but how do you get there?
This template has been designed to support the rollout of a program delivery within an agile framework based on a cloud-based product development. This template is specially designed to help the program management team to follow the development process from requirements gathering to rollout. You may want to use this template in conjunction with your backlogs and issues tracking system and any other project documents you may have.
How far away is the future? It’s the kind of philosophical question a curious child might ask as they ponder their growing sense of the elasticity of time. It’s also the kind of question a less philosophically minded project manager might ask as they try to estimate the point at which their project will achieve its goal.
What is it that makes a megaproject more than just an ordinary one on steroids? Certainly the challenges that megaprojects create make exceptional demands on project management expertise. But what are those challenges? And in what ways does expertise respond to those exceptional demands? A close look at a couple of examples--one ancient and one modern--might help us understand how megaprojects have responded to those questions.
Good project sponsorship is critical for success, but that accountability starts long before the project itself is approved. So why are sponsors frequently set up for failure by their organizations, and how can you change that?
One of the first questions when starting a new project is: What resources do you need? Outlining these needs to executive management is paramount in securing project success, so keep these four tips in mind.
What's the difference? From time to time, organizations find themselves in a dilemma trying to decide whether they should use an in-house PM or PM consultant to manage important projects. Being aware of the tradeoffs and making conscious decisions on each is the best way to minimize unintended consequences.
Many projects get stuck in the middle: the execution phase. Project managers need to be ready to fight that problem to help your project succeed all the way to the end. Keep these four recommendations in mind.
Question: We have a massive internal change coming, and lucky me…I get to head the project! We have tried this before and had to pull back because of negative employee reactions. I know that this time we need some change management processes, too, but who is responsible to do that part of the project?
The good news is, it’s you. You need to take the responsibility and coordinate the change processes in with your usual team activities.
The good news is, it’s not you. Focus on the project and on meeting your metrics of time, cost and quality as usual. Corporate management is responsible to make sure employees accept and use these new changes.
The PMO is “where the buck stops” when endeavors move from simple projects to create products or software and billow out to vague objectives like “employee acceptance” and “corporate compliance”..
Ask your manager. Your project charter is limited to producing the usual product or services and your team is not skilled or experienced in change management processes. Your manager can deal with getting the changes accepted and getting them to stick.
Starting a project is difficult. It's important as a PM to establish who you are as a person in the beginning, particularly with respect to how you will treat the project work and the individuals who will be involved in the process.
Question: My team is made up of people who work for several different functional departments. When not working on my project work, they also produce for other project teams. How can I estimate how long my project will take when I never know if people are available when I need them?
Add a +15% pad to the project estimate, then meet with functional managers to set up an on-demand workflow system.
Ask each potential team member to vow to put aside what is on their desk if your project work needs to be done.
Ask Human Resources to institute a 10% bonus for the workers if your project meets the original project estimate deadline.
Demand a dedicated team from upper management, as this is the only efficient way to do a project.
Document a business case to persuade upper management to fund your project. Keep it short and succinct enough that the busy executive management audience will read and digest it. It should directly convey the information they need to know with salient, hard-hitting, supporting evidence that addresses the bottom line. This is a basic instructional framework of the information you should include in your business case. Enhance it as you wish!
Finding sponsors to back your project is an art. Make a compelling case for the project to gain sponsor support when you are pitching your business case to executive management. Here is an example of a brief, direct project concept designed to lure sponsors into your camp.
Formulating a business case and proposing your project to senior management for buy-in can be tricky. Don't dive right in and start writing. Begin with a solid checklist of guidelines to ensure a business case that's more than buzzword hype.
Mission-critical projects need to be well-justified, with clear goals that can be referenced throughout the life of the project. This business case template offers an excellent approach to goal-setting and a way to communicate those goals effectively.
This is a high-level example of a Project Charter for implementing a methodology, but the structure and approach will work for many projects. This example is heavy on risks and assumptions, light on budgeting, role descriptions and conflict resolution.
The attached tool has been developed to assist you in generating some solid payback data to be used to evaluate the return potential of your proposed method. Not only will it help the gods of finance see the light, but will also help you to understand whether your project is a winner or loser before you ever put your signature on the purchase requisition.
This excellent project justification guide will provide sophisticated advice to maximize the impact of your business case, making it accurate, complete and persuasive. In addition, learn some handy tips, techniques and strategies to complement existing procedures, templates and spreadsheets that you already use.
Presenting a winning business case with the right amount of the right information for the right audience is the key to getting approval and funding for your project! Here is a presentation that will give you the fine points on how to do just that.
No project was ever completed on time and within budget. Identifying risks associated with a project and mitigating them is a crucial activity of project planning. Managers need to not only analyze project risks, but also must develop contingency plans to address those risks.
Building an application? This checklist outlines 52 potential risk areas in application development, defining low, medium and high risk levels for each. Classifying your project risk in each of these areas will not only guide you in forming mitigation strategies, but really help you focus your management attention during the course of the project.
What's the first step in looking at the risks you face in delivering your project? Before performing a full-blow assessment, you may want to ask yourself a few simple questions. This 10 minute, 27 question worksheet will help you quickly identify a number of risk factors common to many projects. It's a great first step in looking at the risks you may be facing at a macro level.
This template outlines a classic Project Charter with a focus on project definition and strategic ties. Risks and stakeholder needs are covered, but not in granular detail. It is appropriate for fairly low-risk projects where the goal is to get everyone on the same page up front.
"Anyone can become angry - that is easy, but to be angry with the right person, to the right degree, at the right time, for the right purpose and in the right way - that is not easy."