BrainDump
  Home arrow BrainDump arrow Page 4 - Codes and Packages in Microsoft Project 20...
ASP Free Forums 
.NET  
ASP  
ASP Code  
ASP.NET  
ASP.NET Code  
BrainDump  
C#  
Code Examples  
Database  
Database Code  
IIS  
Microsoft Access  
MS SQL Server  
Silverlight  
Visual Basic.NET  
Windows Scripting  
Windows Security  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
ASP Web Hosting  
ASP.NET Web Hosting 
Windows Web Hosting
 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
BRAINDUMP

Codes and Packages in Microsoft Project 2007
By: O'Reilly Media
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 1
    2008-06-05

    Table of Contents:
  • Codes and Packages in Microsoft Project 2007
  • Documenting a WBS in Another Program
  • Importing a WBS into Project
  • Documenting Work Package Details
  • Linking Work Packages to the Project Schedule

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Codes and Packages in Microsoft Project 2007 - Documenting Work Package Details


    (Page 4 of 5 )

    If you’ve ever asked a teenager to do a chore, you already know the importance of clearly specifying the work to perform and the results you expect. Otherwise, the dishes in the dishwasher might be placed in the cupboards—unfortunately, before they’re washed. Providing project team members with clear guidance is equally important, but the task names in Project are too short to get into detail. For that reason, separate documents that describe work packages are a great way to tell team members how to do their assignments completely and correctly. And you don’t even have to worry about keeping track of lots of loose documents: You can link them to the Project schedule, as described at the end of this section.


    Figure 4-10:  As you map the fields, the Preview area shows how the values in your text file map to Project fields. In this example, the Name field will hold the values Planning, Identifying Requirements, Documenting Assumptions, and so on. If the mapping isn’t correct, then modify the fields in the To: Microsoft Office Project Field cells until you’re satisfied.

    Ideally, a work package document describes the work to perform, how to tell when the work is done, and how to tell whether it’s done right. A work package for baking a loaf of bread might include the steps for mixing, kneading, forming, and baking the bread. The document could specify that the bread is done when tapping the loaf delivers a hollow thump. Similarly, the work package might state that a successful loaf of bread is an attractive brown color, twice as tall as the unbaked dough, and full of evenly sized holes.

    Building Work Package Documents in Word

    Even small projects require dozens of work package documents. You can speed up your work by creating a Word template for work packages, as basic or as fancy as your knowledge of Word. That way, you can open the template and have a document all labeled and ready for you to fill in. For example, you might set up a basic work package template with the following information:

    1. WBS number. The WBS number that Project assigned to the task in your Project schedule.
    2. Work package name. The task name from the Project schedule.
    3. Description of work. You can use paragraphs or bullet points and provide as much detail as you need to ensure success. If you know an experienced resource is going to do the work, the document can be brief. For trainees, you can provide detailed checklists of steps, or, perhaps, the name of the person who can mentor the assigned resource.
    4. Result. Describe the final state when the work is done as well as how to verify that the work is done correctly. For a work package for setting up a computer, you might include the list of programs that should launch when the installation is complete.
    5. Reference materials. Projects use many types of documents to specify deliverables: requirements, specifications, blueprints, and so on. If additional detailed documentation exists, include the location of those documents, like the folder on the network drive or the project notebook.

    Making a Word template

    Creating a Word template is no harder than creating a Word document. However, finding and using a template takes some setup. Here’s how to create a Word template and save it for reuse:

    1. Create a Word document with the labels you want to include.

      If you want to get fancy, then insert a logo, add instructions to help others fill in work packages, and so on. 
    2. In Word 2007, choose Office button -> Save. In Word 2003, choose File -> Save.

      The Save As dialog box appears. 
    3. Navigate to the folder you use for your custom templates.

      For example, create a folder called Templates in the My Documents folder. 
    4. In Word 2007, in the “File name” box, type the name of the template, and in the “Save as type” box, choose Word Template. In addition, in the navigation bar on the left side of the dialog box, click Trusted Templates. Click Save.

      In Word 2003, in the “Save as type” box, choose Document Template. 
    5. To set up faster access to your template, Click the Office button and then, at the bottom of the Office menu, click Word Options.

      Telling Word where to find your custom templates makes it easier to find and open this template later. That way, you can see these templates right in the New Document dialog box every time you start a new project, as described in the next section. 



      Tip:  
      If you don’t specify a folder for templates, then you can always use Windows Explorer to navigate to the folder that contains your template files. When you double-click a Word template file, Word launches and creates a new document based on the template. 

    6. In the Word Options dialog box, click Advanced. Then scroll to the bottom of the window to the General section, and select File Locations.

      You want to tell Word where to find your templates. 
    7. Select “User templates” or “Workgroup templates”, and then click Modify. In the Modify Location dialog box, navigate to your template folder, and then click OK.

      Choose the folder you created in step 3. 
    8. Click OK again to close the Options dialog box.

    Tip:  The box below explains how to find the File Locations feature in Word 2003. 


    DON'T PANIC

    Setting File Locations in Word 2003

    If you’re still using Word 2003—and plenty of folks are—you’ll find File Locations in a radically different location than in Word 2007. To specify where you store your custom templates, do the following:

    1. Choose Tools -> Options, and then click the File
      Locations tab.
    2. Select “User templates” or “Workgroup templates”, and then click Modify.
    3. Navigate to and select the folder you created in step 3 on page 88, exactly as for Word 2007.

    Opening a Word template

    In Word 2007, click the Office button, and then choose New. In the New Document window, click “My templates.” The New dialog box appears showing the templates in your Trusted Templates folder. Select the template, and then click OK.

    To use a template in Word 2003, choose File -> New. In the New Document task pane, under the Templates heading, click “On my computer”. The Templates dialog box appears open to the General tab, which displays the templates in your User templates or Workgroup template folders (whichever you chose in the previous steps). Select the template, and then click OK.

    More BrainDump Articles
    More By O'Reilly Media


       · This article is an excerpt from the book "Microsoft Project 2007: The Missing...
     

    Buy this book now. This article is excerpted from chapter four of the book Microsoft Project 2007: The Missing Manual, written by Bonnie Biafore (O'Reilly, 2007; ISBN: 0596528361). Check it out today at your favorite bookstore. Buy this book now.

    BRAINDUMP ARTICLES

    - Introduction to Office Live Workspace
    - Using MS Excel for One-way Analysis of Varia...
    - Comparing Data Sets Using Statistical Analys...
    - Import Blogger Posts into WordPress Using Wi...
    - Download WordPress from an FTP Server and Ru...
    - Install and Run WordPress in XAMPP Local Host
    - What Windows 7 Brings to the Table
    - Virtualization and Sandbox Detection
    - Advanced Firebug Techniques in Windows XP Ho...
    - Editing CSS with Firebug in Windows XP Home
    - Using Firebug in Windows XP Home
    - Migrating to Exchange Server 2007
    - Using System Restore on a Non-Bootable PC
    - Finding Logged on Users and More Scripting S...
    - Developing Macro Commands in MS Excel





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 5 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek