1 / 29

Project Management for Technical Communicators

Project Management for Technical Communicators. Tim Bombosch, PMP bombosch@hotmail.com San Francisco STC June 16, 2004. Project Management for Technical Communicators. Why project management Project management basics Planning your project Next steps Resources. Why PM? Core TC Skill.

monty
Download Presentation

Project Management for Technical Communicators

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Management for Technical Communicators Tim Bombosch, PMP bombosch@hotmail.com San Francisco STC June 16, 2004

  2. Project Management for Technical Communicators • Why project management • Project management basics • Planning your project • Next steps • Resources

  3. Why PM? Core TC Skill • How do we define ourselves? • Writers • Technology • Tools • Design • Project Managers?

  4. Why PM? A Few Questions How often do you experience • Quality concessions late in a project? • Delays and other changes because of unplanned changes from your development team?

  5. Why PM? More Questions Are these changes due to poor • Tool or technology skills? • Project management?

  6. Why PM? Sustainable Quality • The best staff and tools do not guarantee quality. • Project shortcomings result most often from poor project management.

  7. Why PM? Project Control Sound project management promises better control over: • Quality • Schedule • Budget

  8. Why PM? Organizational Power • Outsourcing • Negotiation • Strategic value to enterprise • Less conflict, less stress

  9. Basics: Triple Constraints Time Resources Scope/Quality

  10. Basics:Five PM Processes Execute Plan Activity Control Close Initiate Time

  11. Phase Initiate Plan Output Broad plans, specs, estimates, resources Project plan, supporting detail, plan approval Basics: Project Life Cycle

  12. Basics: Project Life Cycle

  13. Basics:Project Baseline Project Baseline is Your Bible • Detailed plan for who, what, where, when, how long, and how much • Requires sign off from all necessary stakeholders • Changes to baseline must be approved by relevant stakeholders

  14. Basics:Project Baseline • Project Baseline is Your Bible • Measure progress against baseline • Variance from baseline requires corrective action

  15. Basics:Project Baseline Project Baseline is Your Bible • Quality = Conformance to requirements. • No gold-plating!

  16. Basics: Projects are Iterative Initiate Plan/Baseline Control Execute Close

  17. Basics:Five PM Processes Execute Plan Activity Control Close Initiate Time

  18. Basics: PMI vs. Hackos

  19. Plan: Info Plan vs. Project Plan

  20. Information Plan • Preliminary budget, schedule, resources • Project goals • Descriptive, not prescriptive

  21. Information Plan Analyze: • Audience • Needs • Tasks

  22. Information Plan Decisions to make: • Media selection • Deliverables

  23. Project Plan: Main Components

  24. Project Plan: First Draft Info Plan Sequence Schedule WBS Duration Est. 1st Draft Resource Planning Cost Est. Budget

  25. Project Plan: Second Draft Other Planning Factors: • Risk • Quality • Change Control • Outsourcing

  26. Project Plan: Approval • May go through several iterative phases before all parties approve • Once approved • Move on to execution and control • Plan is declared the project baseline, requiring strict change control for further amendments

  27. Next Steps: Major Activities Plan Execution Project Control • Status reports • Change control • Approve baseline changes

  28. Next Steps: Major Activities Quality Control • Measure results against requirement quality standards • Qualityassurance testing Risk Management • Monitor risk factors • Make contingency plans

  29. Resources • Project Management Body of Knowledge (PMBOK) • www.pmi.org • UC Santa Cruz Extension • JoAnn Hackos: Managing TechnicalDocumentation Projects

More Related