project governance avoiding administrivia l.
Skip this Video
Loading SlideShow in 5 Seconds..
Project Governance: Avoiding “Administrivia” PowerPoint Presentation
Download Presentation
Project Governance: Avoiding “Administrivia”

Loading in 2 Seconds...

play fullscreen
1 / 18

Project Governance: Avoiding “Administrivia” - PowerPoint PPT Presentation

  • Uploaded on

Project Governance: Avoiding “Administrivia”. Lisa Kosanovich Project Manager Center for Instructional Design Brigham Young University Copyright Information. Copyright Lisa Kosanovich 2005.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Project Governance: Avoiding “Administrivia”' - Mia_John

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
project governance avoiding administrivia

Project Governance:Avoiding “Administrivia”

Lisa Kosanovich

Project Manager

Center for Instructional Design

Brigham Young University

copyright information
Copyright Information

Copyright Lisa Kosanovich 2005.

This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the author. To disseminate otherwise or to republish requires written permission from the author.


reactive approach to problems that arise

  • “Who is the Boss?”
  • Design problems are being resolved in a vacuum
  • Complete project status and issues do not reside with one person or in a collective whole
  • Project Plans need “revamping” on a regular basis to clarify when the project will finish and what ‘really’ remains to be done, few know when their work should be done
project governance proactive approach to projects
Project Governance- proactive approach to projects
  • TEAM: Define Team Roles and their functions
  • SCOPE: Change Management and a Scope Steward
  • COMMUNICATION: Communication Framework
  • SCHEDULE: Scheduling Tools and Principles
  • No one is the “boss”
  • Everyone has a key role to contribute throughout the life of the project
  • Example:
    • Designer: steward of the scope for the project, technical design and resolution
    • Sponsor: Define what is needed, make decisions on behalf of the user
    • Production Staff: Provide technical solutions, build product
    • Project Manager: steward over project information

Change** Matrix

*Consultation with the ‘steward of the scope’ will clarify what size a requested change is.

**Changes should be based on a constraint matrix


Constraint/Flexibility Matrix

Directs change decisions that are made, in an attempt to protect that which is most constrained

  • Team listserv, alias, or group email
  • Weekly Team Email
  • Meetings:
    • Brainstorming
    • Consensus gathering
    • Changes that need negotiation
    • Issues that will require more than one conversation within the team
    • Almost NEVER for status
  • Define tasks at the level where issues occur and status is most meaningful
  • Do not plan past your next point of knowledge
  • Use the best tool for the job
    • Waterfall vs. iterative
    • Task driven vs. date driven
    • Checklist vs. Schedule
Date Driven:

Biweekly meetings during design phase of a project

Schedule is most constrained therefore dates will be drawn out by which to achieve certain features

Decisions need to be made even though research or work may not yet be complete

Task Driven:

Scope is most constrained therefore work will continue until all features are achieved

Many resources or outside vendors are involved, requiring coordination of deliverables

Many dependencies exist within the project requiring coordination for timely completion






Lisa Kosanovich

Brigham Young University