Project Insight Community
Sign in | Help
in
 

Project Management Software Implementation and Adoption Best Practices

October 2009 - Posts

  • Leverage the Intelligent Project Scheduling in your Project Management Software

    If you've finished the project template creation process discussed in the last post, then you are ready to start thinking about how your tasks and activities link together. If you have worked with Microsoft Project, then you know about task dependencies. If you are migrating from Excel, then the idea might be new. Basically, tasks have relationships. That is, often one task must be finished before another one can get started. This is called a finish-to-start task type.  There are four task types:

    1.Finish-to-start

    2.Start-to-start

    3.Finish-to-finish

    4.Start-to-finish

    If you set up your tasks with dependencies or relationships, then you can leverage what we call 'intelligent scheduling.' This allows a project manager to change the start date of the project and the tasks will automatically shift and correct (assuming you have not used any constraints, but we'll get into that later). The other advantage is that if you change the task duration or timeframe needed to perform the task, then the schedule will shift as well. The 'geeky' definitions of the task dependencies listed above are:

    Finish-to-start - The preceding task must finish before the successor task (task following it) can get started

    Start-to-start - The preceding task must start before the successor can start, but they can start in parallel

    Finish-to-finish - The preceding task must finish before the successor can finish

    Start-to-finish - The preceding task must start before the successor can finish A good project template will use these task types so that the projects created from the template will be as flexible as possible.

    You may link your tasks using drag and drop on our interactive Gantt chart, or you may add predecessors in the task list view. If you are migrating from Microsoft Project, then the easiest method is to add the 'predecessors by number' and 'task number' columns. This allows you to work as you would in Microsoft Project, simply adding the predecessor task number and the same abbreviations in Microsoft Project. For example, 3SS means that task 3 is the predecessor task to the current task and it is a start-to-start relationship type. You may need to sit with your team to determine what the right task flow is, but believe me it's worth the time to get a great project template that is available for continual re-use.

     

    Cynthia K. West, Vice President, Project Insight

    Cynthia West, Vice President, Project Insight

    West is Vice President at Project Insight where she oversees the sales and marketing efforts for the project management company. West is a ‘serial entrepreneur‘ with over 15 years of experience in IT. She specializes in building the sales infrastructure for new companies or divisions.

     

  • Develop Your Project Templates

    While every project is unique, many projects of a certain type have repeatable phases and tasks. If this is true for your project team, then it makes sense to sit down and develop your project templates. We recommend getting the people that belong to the team or department or group together for a meeting. We like to perform the 'sticky note' exercise as a method of capturing all activities or tasks on a project. What's this? The team meets and one person acts as the moderator, writing down all individual tasks on a 'sticky note' and putting it on the wall or white board. The team outlines all tasks and activities without judgment about the level of detail or what order the tasks should be in. Just brainstorm and collect all the tasks, one per sticky note.

    Once you are satisfied that you have outlined all activities that encompass that project type, then you may organize them in an outline or WBS (work breakdown structure) format. The first group of tasks is labeled 1.0 in your WBS. One rule of thumb is that phases or summary tasks should start with words that are nouns, whereas tasks start with verbs because they are things that you 'do.' A lively discussion usually ensues. Be patient and take the time to get the outline right. You are also building team agreement during the process. That is, you want 'buy in' from the project team about the steps that the project will take to complete. By participating in the process, the team members will offer less resistance, as they helped 'build the house,' so to speak.

    The next step is to look at the level of detail that you have outlined. Sometimes it is appropriate to build out more detail, but in our experience, it is more likely that you will want to trim out some of the detail. This makes your task list or WBS more manageable. More experienced project managers know that the more junior the staff, the more detail you need to have. If your team is experienced, you may still want to have details in the task description fields of your project management software solution. Steps may be outlined there, instead of making the steps individual tasks. This keeps the team members' burden of updating tasks down and you will get more adoption!

    We had a customer that had task lists initially built out to the 15 minute increment in Project Insight, project management software. That turned out to be too cumbersome for their fast paced environment. Imagine having to check off a task every 15 minutes! So they trimmed down the template and people were much happier. Another customer told me that she was out for surgery last year and because she had built out exact steps in the task description fields, the project manager that took over for her was able to complete the project on schedule without any hiccups. A great success story and wonderful use of project templates.

    Summary

    -Meet with the team

    -Write down all tasks on sticky notes

    -Arrange sticky notes into an outline

    -Decide how much detail you need

    -Then, put your results into your project scheduling software.

     

    Cynthia K. West, Vice President, Project Insight

    Cynthia West, Vice President, Project Insight

    West is Vice President at Project Insight where she oversees the sales and marketing efforts for the project management company. West is a ‘serial entrepreneur‘ with over 15 years of experience in IT. She specializes in building the sales infrastructure for new companies or divisions.

     

  • First Things First - Step 1 in Implementing a Project Management Solution - Global Settings

    Too often people purchase a new project management software solution and want to put their first project in right away, without doing the 'homework' first.  Before you enter in any information, be sure to follow your software provider's best practices.

    Attend the webinars

    The first step with Project Insight is to understand the global settings in the system administration. You may do this by attending one of our webinars. It's an hour well spent! It is very simple to enter data in our software, however, the key is WHAT data or information SHOULD you put in the solution? Once you have attended the webinar, you will have a foundation for doing the homework assignment.

    Read the Best Practices

    We have developed Best Practices on many subject areas. It is a good idea to read and understand these documents as step two. You will find these resources in our customer Community.

    Do your homework

    We provide you with an outline of questions that you need to ask yourself and quite possibly the entire team. I won't reiterate the whole list here, but as an example, let's take project types. You will need to populate your global settings with the list of project types that your team performs. In some cases, you may already know what the list is. However, it is also beneficial to ask the project team members, so that your list is complete and thorough, and you don't have to change it later. In our example of project types, this information is tied to the reports and dashboards. So, you will want to ask yourself, how would I, or my management team, like to see this data rolled up? Make sure the terminology is familiar and agreed upon. Do this for each of the global settings.  

    Input the information

    Now that you have an understanding of the functionality, you have read the best practice documents and met with your team, you are ready to input the information. This will lay the foundation for the project managers to input their projects and templates. When they go in to add their projects, all the pull down menus and select lists will be in place to make their jobs easier!

     

    Cynthia K. West, Vice President, Project Insight

    Cynthia West, Vice President, Project Insight

    West is Vice President at Project Insight where she oversees the sales and marketing efforts for the project management company. West is a ‘serial entrepreneur‘ with over 15 years of experience in IT. She specializes in building the sales infrastructure for new companies or divisions.

     

Copyright Project Insight & Metafuse, Inc., 2010. All rights reserved.