Project Management for Technical Communication Professionals

14,873 views

Published on

Presentation to the members of the Indiana Chapter of the Society for Technical Communication, December 18, 2006. Delivered by Greg McCormick on the Project Management Institute methodology and how it can help technical communication professionals better plan and manage their technical documentation projects.

Published in: Business, Technology
5 Comments
33 Likes
Statistics
Notes
No Downloads
Views
Total views
14,873
On SlideShare
0
From Embeds
0
Number of Embeds
231
Actions
Shares
0
Downloads
0
Comments
5
Likes
33
Embeds 0
No embeds

No notes for slide
  • Project Management for Technical Communication Professionals

    1. 1. Project Management and the Technical Communicator STC-Indiana December 18, 2006
    2. 2. Rant Alert! <ul><li>IMO </li></ul><ul><ul><li>Technical Communications is not really about </li></ul></ul><ul><ul><li>Semi-invisible activities </li></ul></ul><ul><ul><li>Software tools </li></ul></ul><ul><ul><li>Content </li></ul></ul><ul><ul><li>TC should be mostly about </li></ul></ul><ul><ul><li>Applying the tools to communicate and manage content as useful business knowledge </li></ul></ul><ul><ul><li>Using visible KM activities to apply that business knowledge for business results </li></ul></ul><ul><ul><li>Technical Communications is a tool – a means to a business end – not an end unto itself! </li></ul></ul><ul><ul><li>STC hasn’t sold this to business management… </li></ul></ul>
    3. 3. A “Hard Sell” of Our Value <ul><li>I think: </li></ul><ul><ul><li>Business already recognizes Project Management </li></ul></ul><ul><ul><li>TechComm can “ride” PM to visibility and success </li></ul></ul>etc... Business Continuity Projects New Product or Service Development Technical Communications Project Management Regulatory Compliance Projects Customer / Quality Projects C-Level Management
    4. 4. Lessons from Failed Projects <ul><li>Projects may fail outright due to </li></ul><ul><ul><li>Incomplete Planning </li></ul></ul><ul><ul><li>Poor Execution </li></ul></ul><ul><li>… or may be perceived as having failed </li></ul><ul><ul><li>Poor quality of the project’s product (“better”) </li></ul></ul><ul><ul><li>Exceeding time (“faster”) </li></ul></ul><ul><ul><li>Exceeding cost estimates (“cheaper”) </li></ul></ul><ul><ul><li>Poor management of stakeholder expectations </li></ul></ul><ul><li>PMBOK Guide says: pay serious attention to: </li></ul><ul><ul><li>Project Charter and Scope Statement (documents!) </li></ul></ul><ul><ul><li>Stakeholder management (communication!) </li></ul></ul><ul><li>TC’ors can improve project success, if </li></ul><ul><ul><li>We can talk the PM talk </li></ul></ul><ul><ul><li>We can walk the talk (or at least support it) </li></ul></ul>
    5. 5. Purposes Tonight <ul><li>Provide overview of formal PM techniques, enabling technical communicators to: </li></ul><ul><ul><li>Apply these techniques to your own projects </li></ul></ul><ul><li>Suggest some specific ways for TC’ors: </li></ul><ul><ul><li>Value you can add to projects (to help “talk your way” onto project teams </li></ul></ul><ul><ul><li>Work effectively with other team members </li></ul></ul>
    6. 6. Part 1: Understanding Formal Project Management Techniques <ul><li>Goals: </li></ul><ul><li>Learn techniques applicable to your own projects </li></ul><ul><li>Enable you to communicate effectively with project teams </li></ul>
    7. 7. Project Management Institute <ul><li>Guiding Documents: </li></ul><ul><ul><li>“ PMBOK Guide”® </li></ul></ul><ul><ul><ul><li>Is ANSI Standard for project management </li></ul></ul></ul><ul><ul><ul><li>Provides generic PM techniques for all project types/sizes </li></ul></ul></ul><ul><ul><li>“ Practice Standards” for PM-related activities </li></ul></ul><ul><li>Professional PM Certification – PMP® </li></ul><ul><ul><li>4500+ hours of experience in project leadership role </li></ul></ul><ul><ul><li>Passing four-hour exam with 82% score or better </li></ul></ul><ul><ul><li>Continuing education requirements (PDUs) </li></ul></ul><ul><li>Code of Conduct and Ethical Standards </li></ul><ul><li>Organizational ProjMgt Maturity Model – OPM3® </li></ul><ul><li>5 Chapters in Indiana, including “Central IN” (Indy) </li></ul>
    8. 8. PMI Definitions <ul><li>Project </li></ul><ul><ul><li>“ A temporary endeavor, undertaken to create a unique product, service, or result” </li></ul></ul><ul><ul><li>Ex: building new Walgreen’s on the corner </li></ul></ul><ul><li>Portfolio </li></ul><ul><ul><li>Collection of projects grouped together to facilitate effective management </li></ul></ul><ul><ul><li>Ex: building 3 new Walgreen’s in FW at same time </li></ul></ul><ul><ul><li>Ex: Business Continuity (FRP, RRP, WRP, DRP, etc.) </li></ul></ul><ul><li>Program </li></ul><ul><ul><li>~Centralized management of related work outside of discrete projects (implies an on-going effort) </li></ul></ul><ul><ul><li>Ex: customer satisfaction program </li></ul></ul><ul><ul><li>Ex: QMS registration program (e.g., ISO-9000) </li></ul></ul>
    9. 9. “ Project” vs. “ Product of Project” <ul><li>Project (a cloud) creates product (a tangible) </li></ul><ul><li>1. Activities related to managing project – are somewhat independent of the product </li></ul><ul><ul><li>Bringing team members onto project, training them, and releasing them when their work is done </li></ul></ul><ul><ul><li>Identifying and resolving issues </li></ul></ul><ul><ul><li>Monitoring project schedule and budget </li></ul></ul><ul><ul><li>Communicating project results and information </li></ul></ul><ul><li>2. Activities related to creating the product – this project’s unique deliverable or results </li></ul><ul><ul><li>Estimating RTO and RPO of a business process </li></ul></ul><ul><ul><li>Determining the MARC of the business process </li></ul></ul><ul><ul><li>Establishing “business recovery box” </li></ul></ul>
    10. 10. Knowledge Areas <ul><li>Consider all 9 of these for every project, including TechComm projects </li></ul><ul><li>Integration Management </li></ul><ul><ul><li>Ensure all pieces “fit together” without gaps / overlaps </li></ul></ul><ul><ul><li>Ensure that changes in one component cause proper review and/or adjustment in all others </li></ul></ul><ul><li>Scope Management </li></ul><ul><ul><li>Define project’s “target” </li></ul></ul><ul><ul><li>Define what work is required and what’s not </li></ul></ul><ul><ul><li>Control proposed changes in project scope </li></ul></ul><ul><ul><li>Obtain stakeholder approval for scope (and changes) </li></ul></ul><ul><li>Time Management </li></ul><ul><ul><li>Create project work schedule </li></ul></ul>
    11. 11. Knowledge Areas <ul><li>Consider all 9 of these for every project, including TechComm projects </li></ul><ul><li>Cost Management </li></ul><ul><ul><li>Create project budget (time-phased spending plan) </li></ul></ul><ul><li>Quality Management </li></ul><ul><ul><li>Identify relevant quality standards </li></ul></ul><ul><ul><li>Ensure quality of project activities </li></ul></ul><ul><ul><li>Ensure quality of project deliverables </li></ul></ul><ul><li>Human Resources Management </li></ul><ul><ul><li>Acquire appropriate resources at correct time </li></ul></ul><ul><ul><li>Define, develop, and provide orientation and training </li></ul></ul><ul><ul><li>Release resources when their work is completed </li></ul></ul>
    12. 12. Knowledge Areas <ul><li>Consider all 9 of these for every project, including TechComm projects </li></ul><ul><li>Communications Management </li></ul><ul><ul><li>Identify stakeholder information needs </li></ul></ul><ul><ul><li>Provide status reports and info when/how needed </li></ul></ul><ul><li>Risk Management </li></ul><ul><ul><li>Identify risks to project success </li></ul></ul><ul><ul><li>Develop risk mitigation and monitoring plan </li></ul></ul><ul><li>Procurement Management </li></ul><ul><ul><li>Plan purchases </li></ul></ul><ul><ul><li>Qualify sellers and products/services </li></ul></ul><ul><ul><li>Conduct bidding, negotiation, etc. </li></ul></ul><ul><ul><li>Administer contracts </li></ul></ul>
    13. 13. ITTO Model Helpful to document Inputs, Tools&Techniques, and Outputs (ITTO) of each process or task I nput(s) T ools & T echniques O utput(s) Activity Outputs of one process often become Inputs to others
    14. 14. Process Groups <ul><li>Formalizing Process Groups for a project: </li></ul><ul><ul><li>Provides high-level project perspective </li></ul></ul><ul><ul><li>Identifies major Inputs and Outputs of each </li></ul></ul><ul><ul><li>Offers go/no-go decision gate </li></ul></ul>Phases in project life-cycle 2 processes Closing 5 7 processes Monitoring and Controlling 4 7 processes Executing 3 26 processes Planning 2 2 processes Initiating 1
    15. 15. 1. Initiating Processes <ul><li>Define and authorize the project </li></ul><ul><li>Inputs: </li></ul><ul><ul><li>Business “trigger” – legislation, BOD resolution, feasibility study, customer contract, SOW, etc.) </li></ul></ul><ul><li>Tools & Techniques: </li></ul><ul><ul><li>Organizational resources (PMO, PM “culture”, etc.) </li></ul></ul><ul><ul><li>Project Management Information System (PMIS) </li></ul></ul><ul><ul><li>Glossary [hellooo, opportunity calling…!] </li></ul></ul><ul><ul><li>Expert opinion / assistance </li></ul></ul><ul><li>Outputs: </li></ul><ul><ul><li>Project Charter </li></ul></ul><ul><ul><li>Preliminary Scope Statement </li></ul></ul><ul><ul><li>If your company does a lot of projects, you could offer to create some templates for these documents [hellooo again…!] </li></ul></ul>
    16. 16. 1A: Project Charter <ul><li>Three purposes: </li></ul><ul><ul><li>Formally establish project’s existence </li></ul></ul><ul><ul><li>Officially authorize start of project activities – spend time and $$$ </li></ul></ul><ul><ul><li>Provide common understanding of purpose (resolves “disputes”) </li></ul></ul><ul><li>Identifies: </li></ul><ul><ul><li>Why– business driver, need, opportunity, or justification </li></ul></ul><ul><ul><li>What– chief result or deliverable, and its customer(s) </li></ul></ul><ul><ul><li>When– project time-line (usually shown as milestone chart) </li></ul></ul><ul><ul><li>How much– cost estimate </li></ul></ul><ul><ul><li>Who– project leadership </li></ul></ul><ul><ul><ul><li>Sponsor – provides resources </li></ul></ul></ul><ul><ul><ul><li>Champion – acts as executive “cheerleader” </li></ul></ul></ul><ul><ul><ul><li>Project Manager – directs activities and controls resources </li></ul></ul></ul><ul><ul><li>How– Assumptions and Constraints [documentation calling…] </li></ul></ul><ul><li>Should include signatures of: </li></ul><ul><ul><li>Sponsor, Project Manager, and chief Customer </li></ul></ul>
    17. 17. 1B: Preliminary Scope Statement <ul><li>Should include: </li></ul><ul><ul><li>Description of result / deliverable(s) </li></ul></ul><ul><ul><li>Activities needed to produce result / deliverable </li></ul></ul><ul><ul><li>Entities involved in performing project (internal & external) </li></ul></ul><ul><ul><li>Known project boundaries – results, activities, resources, etc. that are specifically out-of-bounds </li></ul></ul><ul><ul><li>Risks that may affect success of project </li></ul></ul><ul><ul><li>Stakeholder matters: </li></ul></ul><ul><ul><ul><li>List of stakeholders and their roles – active participants, non-participants who are affected, interested observers, etc. </li></ul></ul></ul><ul><ul><ul><li>Expectations, stated and unstated! </li></ul></ul></ul><ul><ul><ul><li>Issues and concerns </li></ul></ul></ul><ul><ul><ul><li>Acceptance criteria </li></ul></ul></ul>
    18. 18. 2. Planning Processes <ul><li>I separate planning into: </li></ul><ul><ul><li>A. Administrative Planning </li></ul></ul><ul><ul><ul><li>Creates a plan to control project (“forest”) </li></ul></ul></ul><ul><ul><li>B. Execution Planning </li></ul></ul><ul><ul><ul><li>Creates a plan to produce result/product (“trees”) </li></ul></ul></ul><ul><li>These different planning types usually performed by different team members or sub-teams … </li></ul>
    19. 19. 2A. Administrative Planning <ul><li>Creates plan that controls project </li></ul><ul><li>Inputs: </li></ul><ul><ul><li>Project Charter </li></ul></ul><ul><ul><li>Preliminary Scope Statement </li></ul></ul><ul><li>Tools & Techniques: </li></ul><ul><ul><li>Organizational resources (PMO, PP&Ps, culture, etc.) </li></ul></ul><ul><ul><li>Project Management Information System (PMIS) </li></ul></ul><ul><ul><li>Glossary </li></ul></ul><ul><ul><li>Expert opinion / assistance </li></ul></ul><ul><li>Outputs: </li></ul><ul><ul><li>Project Management Plan – how each of the 9 Knowledge Areas will be managed </li></ul></ul>
    20. 20. Project Management Plan <ul><li>Covers Knowledge Areas </li></ul><ul><ul><li>Scope Management: </li></ul></ul><ul><ul><li>How actual project scope will be monitored for “creep” and shrinkage </li></ul></ul><ul><ul><li>How proposed changes in scope will be submitted, approved, controlled, and communicated </li></ul></ul><ul><ul><li>Time Management: </li></ul></ul><ul><ul><li>How begin- and end-dates will be monitored </li></ul></ul><ul><ul><li>How task durations will be monitored </li></ul></ul><ul><ul><li>How schedule tracking will be performed </li></ul></ul><ul><ul><li>Cost Management: </li></ul></ul><ul><ul><li>How costs variances will be monitored </li></ul></ul><ul><ul><li>How budget tracking will be monitored </li></ul></ul><ul><ul><li>How contingency/reserve funds will be administered </li></ul></ul>
    21. 21. Project Management Plan <ul><ul><li>Quality Management: </li></ul></ul><ul><ul><li>Identify regulations, standards, and guidelines </li></ul></ul><ul><ul><li>Define/clarify acceptance criteria </li></ul></ul><ul><ul><li>How Quality Assurance (QA) will be provided </li></ul></ul><ul><ul><li>How Quality Control (QC) will be performed </li></ul></ul><ul><ul><li>How Corrective & Preventative Actions will be handled </li></ul></ul><ul><ul><li>Human Resources Management: </li></ul></ul><ul><ul><li>How appropriately skilled individuals, groups, or organizations will be identified </li></ul></ul><ul><ul><li>How team members will be brought onto the team </li></ul></ul><ul><ul><li>How members will be oriented, trained, and qualified? </li></ul></ul><ul><ul><li>How work performance will be measured / monitored </li></ul></ul><ul><ul><li>How members will be released when their work is completed, or when it is unsatisfactory </li></ul></ul>
    22. 22. Project Management Plan <ul><ul><li>Communication Management: </li></ul></ul><ul><ul><li>Identify content required/requested by stakeholder </li></ul></ul><ul><ul><li>Identify timing of delivery (daily, monthly, as-needed) </li></ul></ul><ul><ul><li>Identify format and media preferences </li></ul></ul><ul><ul><li>Risk Management: </li></ul></ul><ul><ul><li>How project risks will be identified </li></ul></ul><ul><ul><li>How risks are analyzed </li></ul></ul><ul><ul><li>How risks will be mitigated </li></ul></ul><ul><ul><li>What risk measures and triggers will be used, and how they will be monitored </li></ul></ul>
    23. 23. Project Management Plan <ul><ul><li>Procurement Management: </li></ul></ul><ul><ul><li>What regulations, standards, and/or guidelines are relevant </li></ul></ul><ul><ul><li>How specifications for goods and services will be developed </li></ul></ul><ul><ul><li>How sellers will be qualified/approved </li></ul></ul><ul><ul><li>How product/service sourcing will be decided – RFI/RFQ, price comparison, value analysis, etc. </li></ul></ul><ul><ul><li>How contracts will be administered </li></ul></ul><ul><li>PM Plan tells how we’ll run the project </li></ul>
    24. 24. 2B. Execution Planning <ul><li>Creates work-plan that produces product </li></ul><ul><li>Inputs: </li></ul><ul><ul><li>Project Charter </li></ul></ul><ul><ul><li>Preliminary Scope Statement </li></ul></ul><ul><ul><li>Project Management Plan </li></ul></ul><ul><li>Tools & Techniques: </li></ul><ul><ul><li>Work Breakdown Structure (WBS) </li></ul></ul><ul><ul><li>Expert opinion / assistance </li></ul></ul><ul><ul><li>Project Management Information System (PMIS) </li></ul></ul><ul><ul><li>Glossary </li></ul></ul><ul><li>Outputs: </li></ul><ul><ul><li>Project Schedule </li></ul></ul><ul><ul><li>Resource Plan </li></ul></ul><ul><ul><li>Project Budget </li></ul></ul>
    25. 25. Work Breakdown Structure (WBS) Can be presented graphically… Create a Manual 1 Define 2 Design 3 Develop 4 Deliver 1.1 Audience 1.2 Purpose 2.1 Scope 2.2 Structure 2.3 Level of Detail 3.1 Write 3.2 Add Graphics 3.3 Index 3.4 Edit 4.1 Copy 4.2 Post 4.3 DMS
    26. 26. WBS … or as a numbered outline: Creating a Manual 1 Define 2 Design 2.1 Design Scope 2.2 Design Structure 2.2.1 Front Matter 2.2.2 Main Body 2.2.3 Back Matter 2.3 Level of Detail 3 Develop 4 Deliver MS-Project uses this scheme
    27. 27. Applied to Processes w/ ITTO <ul><li>4 Project Cost Management </li></ul><ul><ul><li>4.1 Cost Estimating </li></ul></ul><ul><ul><li> 4.1.1 Inputs </li></ul></ul><ul><ul><li> 4.1.1.1 Work Breakdown Structure </li></ul></ul><ul><ul><li> 4.1.1.2 Project Management Plan </li></ul></ul><ul><ul><li> 4.1.2 Tools & Techniques </li></ul></ul><ul><ul><li> 4.1.2.1 Estimating Techniques (analogous, etc.) </li></ul></ul><ul><ul><li> 4.1.2.2 Vendor Bid Analysis </li></ul></ul><ul><ul><li> 4.1.3 Outputs </li></ul></ul><ul><ul><li> 4.1.3.1 Activity Cost Estimates </li></ul></ul><ul><ul><li> 4.1.3.2 Supporting Detail [hellooo…!] </li></ul></ul><ul><ul><li>4.2 Cost Budgeting </li></ul></ul><ul><ul><li> 4.2.1 Inputs </li></ul></ul><ul><ul><li> 4.2.2 Tools & Techniques </li></ul></ul><ul><ul><li> 4.2.3 Outputs </li></ul></ul>
    28. 28. 3. Executing Processes <ul><li>Do work needed to produce result/deliverable </li></ul><ul><li>Inputs: </li></ul><ul><ul><li>Project Work Plan </li></ul></ul><ul><ul><li>Project Management Plan </li></ul></ul><ul><li>Tools & Techniques: </li></ul><ul><ul><li>Project Management Information System (PMIS) </li></ul></ul><ul><ul><li>“ People skills” </li></ul></ul><ul><li>Outputs: </li></ul><ul><ul><li>Product, service, or results (e.g. a deliverable) </li></ul></ul><ul><ul><li>Work performance reports and information </li></ul></ul>
    29. 29. 4. Controlling Processes <ul><li>Monitor performance, and compare it to plan </li></ul><ul><li>Inputs: </li></ul><ul><ul><li>Product, service, or results (e.g. a deliverable) </li></ul></ul><ul><ul><li>Work performance reports and information </li></ul></ul><ul><li>Tools & Techniques: </li></ul><ul><ul><li>Risk triggers </li></ul></ul><ul><ul><li>Project Management Information System (PMIS) </li></ul></ul><ul><ul><li>Issues tracking system </li></ul></ul><ul><li>Outputs: </li></ul><ul><ul><li>Raised issues/concerns/problems </li></ul></ul><ul><ul><li>Corrective or preventative actions </li></ul></ul><ul><ul><li>Requested changes in scope, schedule, quality, etc. </li></ul></ul>
    30. 30. 5. Closing Processes <ul><li>Formally end the project </li></ul><ul><li>Inputs: </li></ul><ul><ul><li>Product, service, or results (e.g. a deliverable) </li></ul></ul><ul><ul><li>Work performance reports and information </li></ul></ul><ul><ul><li>Invoices and receipts </li></ul></ul><ul><li>Tools & Techniques: </li></ul><ul><ul><li>Project Management Information System (PMIS) </li></ul></ul><ul><ul><li>Expert opinion / assistance </li></ul></ul><ul><li>Outputs: </li></ul><ul><ul><li>Released resources </li></ul></ul><ul><ul><li>Project records, including “lessons learned” [hellooo!] </li></ul></ul><ul><ul><li>Contract close-outs and settlements </li></ul></ul>
    31. 31. PMBOK Guide <ul><li>ANSI Standard for projects of all kinds/sizes </li></ul><ul><li>That includes TechComm initiatives… </li></ul><ul><ul><li>Can be applied in total or in part, formally or informally, in general or in detail – whatever is practical </li></ul></ul><ul><ul><li>Techniques work for big team and team-of-1 </li></ul></ul><ul><ul><li>Knowledge Areas remind you of things to consider when quoting time and cost </li></ul></ul><ul><ul><li>Process Groups can serve as milestones in time-line, and may assist in schedule estimation </li></ul></ul><ul><ul><li>WBS helps identify work and the resources needed to perform it, assisting in cost estimation </li></ul></ul><ul><ul><li>ITTO Model clarifies what you need, what you do, and what you produce for each phase, activity, or task </li></ul></ul><ul><ul><li>Outputs can serve as sign-off documents </li></ul></ul>
    32. 32. Part 2: Adding Value to Project Teams <ul><li>Goal: </li></ul><ul><li>Persuade Management to let you out of writer/editor box </li></ul><ul><li>Enable you to work effectively on project teams </li></ul>
    33. 33. TechComm Opportunities <ul><li>Projects often fail due to </li></ul><ul><ul><li>Poor documentation of specifications </li></ul></ul><ul><ul><li>Poor communication of project information </li></ul></ul><ul><ul><li>Poor creation and management of project records </li></ul></ul><ul><li>PMBOK Guide has 117+ Inputs & Outputs! </li></ul><ul><ul><li>Many are project “working documents” such as forms, records, lists, reports, charts, communications, etc. </li></ul></ul><ul><ul><li>Not usually done by TC professional = ?usability </li></ul></ul><ul><li>“ FallWorld 2004” </li></ul><ul><ul><li>Largest conference of Business Continuity industry in world </li></ul></ul><ul><ul><li>2000 attendees, speakers, exhibitors </li></ul></ul><ul><ul><li>No person with ProjMgt certification </li></ul></ul><ul><ul><li>No person who described him/herself as a TC’or </li></ul></ul><ul><ul><li>No company with TC’or on BC project team – but everyone said it was great idea! </li></ul></ul>
    34. 34. A. Represent The Organization <ul><li>Goal: Help safeguard business interests </li></ul><ul><ul><li>Correlate project to organization Mission and Goals </li></ul></ul><ul><ul><li>Facilitate integration of project with other programs, such as Sarbanes or ISO-9000 </li></ul></ul><ul><ul><li>Correlate project results/deliverables to existing policies, processes, and procedures </li></ul></ul><ul><ul><li>Help define and facilitate information exchange between project team and the organization </li></ul></ul><ul><ul><li>Maintain “outside editor” perspective – watch “forest” while team works on “trees”, especially scope creep </li></ul></ul><ul><ul><li>Help identify project risks and critical success factors </li></ul></ul><ul><ul><li>Add project vocabulary to company Glossary </li></ul></ul><ul><ul><li>Define, design, develop, and deliver training </li></ul></ul><ul><ul><li>Grow and manage template library </li></ul></ul>
    35. 35. B. Represent The Project <ul><li>Goal: Support project team and its success </li></ul><ul><ul><li>Facilitate development of important documents, such as Charter, Scope Statement, Project Mgt. Plan </li></ul></ul><ul><ul><li>Identify risks, and help mitigate and monitor them </li></ul></ul><ul><ul><li>Clarify tasks, milestones, and deliverables </li></ul></ul><ul><ul><li>Handle Change Management </li></ul></ul><ul><ul><li>Maintain Issues Log and help resolve items </li></ul></ul><ul><ul><li>Assist information communication within team </li></ul></ul><ul><ul><li>Capture and record work performance information </li></ul></ul><ul><ul><li>Update Project Management Info. System (PMIS) </li></ul></ul><ul><ul><li>Create/capture project records, including “lessons learned”, and make sure they get updated into KMS </li></ul></ul>
    36. 36. C. “Suggest” Changes ASAP Initiation T i m e & C o s t Execution Planning Closure
    37. 37. PMI Resources <ul><li>Project Management Institute (international) </li></ul><ul><ul><ul><li>www.pmi.org </li></ul></ul></ul><ul><ul><li>Indiana Chapters: </li></ul></ul><ul><ul><ul><li>Central – www.pmicic.org </li></ul></ul></ul><ul><ul><ul><li>Michiana – www.?????.org </li></ul></ul></ul><ul><ul><ul><li>Northeast – www.pmi-neic.org </li></ul></ul></ul><ul><ul><ul><li>Northwest – www.pmi-calumet.org </li></ul></ul></ul><ul><ul><ul><li>Southwest – www.pmiswic.org </li></ul></ul></ul>
    38. 38. Questions <ul><li>= </li></ul><ul><li>Greg McCormick , PMP </li></ul><ul><ul><li>Cedar Canyon Consulting </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul>

    ×