August 9, 2011
The first thing I hear from people when I discuss web project management is, “Ugh. How boring.” The web developers live in a world where technologies change every few weeks, and the thought of taking time to manage a project—versus diving into the tasks at hand and getting things done—doesn’t make initial sense. I like to explain it this way: “Everyone does project management. If you don’t know project management principles, then you are doing it wrong!”
For most people, the problem begins the very moment they get a new “project.” Before the work begins, you need to clearly define what is a project, so you know when to use project management principles. At the University of Wisconsin-Platteville, we use a simple rule in IT: a project is anything that will take over 120 hours or $10,000.
Once you know what is a project, you can then utilize the tools to help manage them.
That answer is simple: use project management to make order of the chaos. Using project management helps you establish priorities and manage expectations. They help keep things on task and projects within scope, so your shop can run more efficiently. The bottom line: they allow you to be more nimble.
A lot of the project management tools are forms, documents, communications, reports and discussions. It doesn’t seem to magical when it is described like that, but the results can be amazing. The first thing you need to understand is that if you are working on a current project, and you have not started to use these tools, you can’t do anything now. The only way to use project management is to start it off from the very beginning. So let’s review one of the most common project management tools: the Project Charter.
A project charter is a document used to identify the exact details and expectations of the proposed project. Identify who is the project sponsor, a.k.a. who’s paying for this or who is the end decision maker (NOT A COMMITTEE) for the project. Identify the problem, describe the project, and the end goals. From here, develop the scope of what the project will contain, and most importantly, what it will NOT contain. Have a section to list a few critical success factors, and what your assumptions are going into the project.
Next, identify the authority of the project. Find out who has control over the money, and who is responsible for the oversight of the project. Sometimes there are multiple people here. You also need to list what milestones exist for the project, but keep this at a very high level. You don’t need to get into details yet—that comes later with the work break down structure and the project plan.
Now that you have identified the problem in detail, and the authority, you need to define the team. Make a list of all of the people who are affected, and give them roles and responsibilities. You must have one (no more than two) project sponsor(s). You must identify the key stakeholders who will be able to affect your project, as well as the subject matter experts within the area who will do the work. List the technical team and identify their specific role for this project, as well as listing any required resources (software, hardware, meeting rooms, etc.).
The last part of your charter should include the project leadership’s points of contact—get all of the information together in one spot. If there are terms being used that your functional users won’t understand, add a a glossary. You also may need to add appendices of reports, forms, or anything else that is applicable to the project.
Take these first steps and get everyone on the same page with your project charter. It will make a huge difference when the project sponsor signs on the dotted line!
© 2014 LINK | Theme by Eleven Themes