Tuesday, February 27, 2007

SharePoint Project Management

"Project Management"
Microsoft Office SharePoint Portal Services 2003
Use a List
Here is an interesting scenario.
A client wishes to move their internal development team to an effective project management system\process using SharePoint.

In a space of a few hours we built out a list with a few view; sync'd it with an excel file; developed some required field and process scenarios; and moved to review.

Will we use sub-sites to track project documentation /w versioning or just document libraries?
The clients existing HelpDesk system will be used to track minutia related to work in progress and current assigned developer - the client has tiered out their team DB Ops; DB Dev (procs; triggers;) DB Schema (tables; views; replication;) DB Index; Application Code Logic (UI; Messaging; GUI;); Reporting;

Base Project/Task List spec'd out in a tree format

  • Functional Area

  • Environment(s) Affected

    Multiple Choice check box

    Text list

    manual maintenance

  • Project ID

  • --> Project\Task Title

  • --> HelpDesk System ID

  • --> Task ID

    Default: Project ID

    Iterative - Project ID + .01, .02,

  • --> Project\Task Status

    Multiple Choice check box

    Text list

    manual maintenance

  • Project Lead

    Multiple Choice check box

    Text list - manual maintenance

    Ideal - Multiple Choice Active Directory Group List Lookup

  • --> Project\Task StartDt

  • --> Project\Task TargetDt

  • --> Project\Task CopleteDt

  • --> Project Human Resources

    Multiple Choice check box

    Text list - manual maintenance

    Ideal - Multiple Choice Active Directory Group List Lookup

  • --> Currently Assigned To

    Multiple Choice check box

    Text list - manual maintenance

    Ideal - Multiple Choice Active Directory Group List Lookup

No comments: