Should You Try for a PMI Certification
•
0 likes•105 views
This document discusses whether a technical communicator should pursue a Project Management Professional (PMP) certification. It outlines the prerequisites for PMP certification, including 4,500 hours of project management experience and 35 hours of education. It then provides examples of how a technical communicator could document their experience across the five process groups to meet the experience requirement, including managing documentation projects. It notes the benefits of certification, such as career advancement opportunities, but also acknowledges it comes with more responsibility.
Recommended
Recommended
More Related Content
Similar to Should You Try for a PMI Certification
Similar to Should You Try for a PMI Certification (20)
Recently uploaded
Recently uploaded (17)
Should You Try for a PMI Certification
- 1. SHOULD YOU TRY FOR A PMI CERTIFICATION? Wendy Barnhart Ross http://www.linkedin.com/in/wendybarnhartross
- 3. #Spectrum16 Certifications PMP – Gold Standard PgMP PfMP – Portfolio Management CAPM – Certified Associate PMI-PBA PMI-PBA PMI-ACP – Agile PMI-RMP PMI-SP
- 4. #Spectrum16
- 5. #Spectrum16 4,500 hours experience 35 hours of project management education ~200 hours of studying PMP – Prerequisites
- 6. #Spectrum16 4,500 hours leading and directing projects as a Technical Communicator!? EXAMPLE New hardware project documentation set • 13 months • 630 hours spread over the 5 PM process groups • Initiating • Planning • Executing • Monitoring and Controlling • Closing
- 7. #Spectrum16 4,500 hours as a Technical Communicator!? Initiating (55 hours): • Gather historical data (legacy manuals) • Review lessons learned • Identify stakeholders • Identify basic requirements
- 8. #Spectrum16 4,500 hours as a Technical Communicator!? Planning (200 hours): • Determine detailed requirements • Create a list of activities • Estimate # of writers, # of hours/days per activity • Develop a schedule • Identify project risks
- 9. #Spectrum16 4,500 hours as a Technical Communicator!? Executing (200 hours): • Work the plan! • Manage time (yours, other writers) • Mentor others on the project • Manage stakeholder expectations • Mitigate and exploit risks
- 10. #Spectrum16 4,500 hours as a Technical Communicator!? Controlling (125 hours): • Control project costs • Control quality of documents • Manage review/approval of documents
- 11. #Spectrum16 4,500 hours as a Technical Communicator!? Closing (50 hours): • Release the documents (print/web/SAP/to sw team, etc.) • Archive those documents • Create lessons learned • Archive lessons learned and other documents
- 12. #Spectrum16 4,500 hours as a Technical Communicator!? 630 hours NOT including the act of researching and writing the documents themselves, and while running other projects. It does add up, but…
- 13. #Spectrum16 4,500 hours as a Technical Communicator!? Other job-related projects • Volunteer to manage a special project • Create, plan, deliver, evaluate co-worker training • Run a department project to improve a procedure
- 14. #Spectrum16 4,500 hours as a Technical Communicator!? Outside of work? Volunteer to manage projects in your favorite organization, such as…
- 16. #Spectrum16 Instant PMP! (The system tells you on the spot whether you passed or failed.)
- 17. #Spectrum16 Accolades from friends and family! Oohs and ahhs from co-workers 3 more letters to squeeze into my LinkedIn heading
- 18. #Spectrum16 The opportunity to: • meet new people • learn new things • represent the PMO in project meetings and to executive management • more accolades from friends and family!