Building Reusable Project Templates Montana

provided by: 
Originally published at Internet.com

As we all know, the Project Management Institute (PMI) definition of a project is a "[t]emporary endeavor undertaken to create a unique product, service or result." By definition a project is unique, meaning that no two are exactly alike. However, most organizations have projects that they repeat on a monthly, quarterly, or even more frequent basis. For these efforts, it makes sense to create a project template. To create a good project template, get your team together in a meeting room or virtual conference call, and encourage participation. The purpose of this meeting is to gather all of the tasks or work that the project requires. Each participant may have valuable information to add, which is why you want all team players involved. Plus, if you build a project schedule with everyone's input, you will earn more 'buy-in.' Activities or Tasks Write down all of the individual tasks on sticky notes and place them on a white board or wall. Initially, do not worry about the task order just get all of the required steps down. Once the team is satisfied they have listed all the activities or tasks that will comprise your project, then you can create the order or work breakdown structure (WBS). Do this by putting the sticky notes in outline format on the white board. It is helpful to use a work breakdown structure (WBS) format which is like an outline format for your project tasks. For example: 1.0 2.0 3.0 3.1 3.1.1 3.1.2 3.2 3.3 Group your tasks under appropriate ummbrella or summary tasks. Once you have ordered your tasks and the team agrees to the order and structure, you should then ask to what level do we want to manage the work? Some teams outline every miniscule task but then decide they do not want to manage at that level of detail. This seems particularly true of fast-paced environments. The faster the pace, the higher level the team should manage the work. Otherwise, the team will rapidly get bogged down in updating tasks, rather than performing work. Once the above is complete, you can build the tasks into a formal schedule, using either Microsoft Project desktop or enterprise project management solution. Resource Types or Skill Sets The next step is to associate the appropriate skill set or resource type with each task or activity in your WBS. Because you may vary the actual resources you end up assigning to tasks, a good template is built with resource types in them so you can make assignments at the last minute. If you do not have a standard list of skill sets required for your projects, you will first need to build consensus on what that list should contain. Once the list of skill sets is agreed upon, then you may associate each task with a skill set. The value of associating tasks with skill sets is when you turn to forecast your resource needs, you will know what types of resources you require prior to making assignments. Duration and Work The next step is to decide how much time in days each task should take. This is called duration, or the total timeframe given from start to finish. This is distinguished from the work or effort of a task. For example, a task might take eight hours to complete, but a resource may be given five working days to complete the work. Once approximate duration is given to each task, then move to adding in the amount of work or effort each activity requires. It is always a good idea to pad the estimates a bit, but not too much, so you build in a buffer into your template. Adjustments may be made later depending on the seniority of the ultimate resource assigned and the like. Dependencies