• Home
• News
• Resources
• Books
• Glossary
• Archives
• Blog
• About
• Contact

PM Cheat Sheet

January 22, 2006 from The Practical PM

(No Ratings Yet)

 Loading ...

This is a repost to allow LiveDocumentRSS to register this post.

Program Management Cheat-sheet
 By Edward Becker

• Clear Mission Statement/Objective(s)


• Clear Project Sponsor


• Clear Project Clients/Stakeholders


• Use Cases derived from Business needs


• Requirements derived from Use cases - Scoped to resources available - Scoped to immediate customer needs


• Assumptions


• Architecture is based on platform/system/business applications/visual interface support and interoperability requirements.


• High Level design is milestone-driven (not time-based or event based)


• Low level Design is milestone-driven (not time-based or event based)...Visual interfaces spec'd at this level


• Dependencies


• Task planning (event-based) (incorporates project processes (build/architecture/dev/test/ops - identify resources)


• Clear communication Plan (event* based)


• Task follow up (event* based) (measure of progress)


• Task follow up (time* based) (Schedule management)


• Feedback plan (event* based)


• Constraints


• Risk Plan


• Test Plan (measure!)


• Rollout plan


• Operational Plan


• End-of-life assessment frequency (exit/upgrade strategies)


• Post-Mortem

- Events can be time-based (day/week/etc), milestone-based (product-driven), event based (process driven -Milestones "are miniature objective/mission statements “
-A clear communication plan should imply additional informal relationship management strategy (luncheons, one-one's, after-hour events
-The Event-based task follow up gives you accurate measure of progress (based on reporting of events via feedback plan), whereas the new time time-based task follow up forces you to assess (via the perception of task owners adjusted with estimated vs. actual time) and manage the schedule.
-Company standards/templates are valuable for achieving clarity quickly, but don't be afraid to break those standards when they reduce clarity!
-All documentation resulting from steps above should be reviewed and subject to scrutiny by those impacted.

• Self-awareness (recognize your personal aspirations/goals/morals/strengths/weaknesses/confidence)


• Self-Management (Identify and fulfill owned tasks)


• Social-Awareness (Perception is everything/recognize business goals)


• Relationship management (guide everyone in right direction with resonance, consider their self as well as their self-awareness.)

Comments

Copyright © 2007 PMToolbox :: Tools and Resources for Project Management