Bell Project Management

Chicago, IL 60610
ph: 312-752-8660

My Approach

 

I use Microsoft Project as a default, but I have used other programs as well.

 

 

  • To avoid the Quagmire Syndrome and align stakeholder expectations, I break the larger project down into modules
    • Module 1 is a rough budget and schedule for each succeeding module; a detailed plan and budget for Module 2 is produced in Module 1
    • Each subsequent module, as it is carried out, produces a detailed plan and budget for the next module

 

  • To reduce or eliminate mismatched expectations, all development and/or process re-engineering is driven by end-user documentation

 

    • This is the same documentation, in substance and detail, that the end-users will receive upon completion of development or re-engineering
    • If compromises are necessary, we agree on those compromises before taking the next step in the project.
    • All parties, whether technical or end-user, are referring to the same, and only, document(s) that is meaningful and unambiguous for all parties.

 

    Education

     

    PhD, Indiana University

    • Research Methodology
    • Organization and Public Administration Theory
    • Political Science

     

    AB, Wabash College

    • English
    • Political Science

    PM Experience

     

    Director, Change Management

    WebScheduler, LLC

     

     

    Senior Consultant

    PricewaterhouseCoopers

     

     

    Senior Project Manager

    Shared Medical Systems Inc.

     

     

    Director, Health Systems Division

    CompuNet, Inc.

     

     

    Head Technical Writer and Editor

    Systems Applications Inc.

     

     

    Project Management Faculty Instructor

    University of Phoenix

     

     

    Chicago, IL 60610
    ph: 312-752-8660