The Project Management Tool Kit: 100 Tips and Techniques for Getting the Job Done Right
288The Project Management Tool Kit: 100 Tips and Techniques for Getting the Job Done Right
288Paperback(Third Edition)
-
PICK UP IN STORECheck Availability at Nearby Stores
Available within 2 business hours
Related collections and offers
Overview
Shifting priorities, budget cuts, unexpected interruptions….the obstacles that project managers face daily are sometimes relentless and always burdensome. Now, the average project is only growing more complicated.
The Project Management Tool Kit is filled with step-by-step guidance that will enable managers to complete even the most complex projects both on time and on budget. The book also offers 100 powerful, practical tips and techniques in a variety of areas, including:
- Scope planning
- Schedule development and adjustment
- Cost estimating and control
- Defining and using project metrics
- Decision-making and problem solving
- Motivation and leadership
- Stakeholder engagement and expectation management
- Risk identification and monitoring
Extensively updated and revised to reflect the latest changes to A Guide to the Project Management Body of Knowledge (PMBOK® Guide), the checklists, charts, examples, and tools for easy implementation in this invaluable resource will help project managers of all types tackle any challenge that comes their way.
Product Details
ISBN-13: | 9780814433454 |
---|---|
Publisher: | AMACOM |
Publication date: | 12/19/2013 |
Edition description: | Third Edition |
Pages: | 288 |
Product dimensions: | 7.20(w) x 8.80(h) x 0.30(d) |
Age Range: | 18 Years |
About the Author
Read an Excerpt
1 Activity Definition (PMBOK® 6.1, Define Activities)
What: Documenting the activities resulting from the lowest level of the project work breakdown structure (WBS)
and assigning an owner to each.
When: Project planning.
Results: Clear descriptions of all identified project work and delegation of responsibility.
Verify Activities
Activity definition is a key step in project plan development. After developing the work breakdown structure (WBS), verify that all work listed is necessary. If the work at the lowest level will probably require more than a month to complete or more than 80 hours of effort, strive to break it down further.
People often overlook work related to organizational, business, or legal requirements.
Examples include preparation for project life cycle checkpoints a methodology requirements, project and other reviews, scheduled presentations, and specific documents the project must create. Add any missing work you discover to the WBS and scope baseline.
Describe Activities
Convert the lowest-level WBS entries into project activities that can be estimated a scheduled, and tracked. Check that each represents a discrete, separate piece of work that has a starting and a stopping point. For each piece of work, capture and document any assumptions.
Describe each lowest-level work package concisely in terms of the work to be done and the task deliverable (examples: install power, edit user documentation).
These verb-noun descriptions ensure clarity and make planning and tracking easier.
Identify one or more specific deliverables for each lowest-level activity. For each deliverable, specify the acceptance or test criteria. Be able to describe any requirements relating to standards, performance, or specific quality level.
If no one can clearly define the deliverable for an activity, the work may be unnecessary; consider deleting it.
Assign Owners
Seek capable, motivated owners for each lowest-level activity. Staff all work possible using willing volunteers, and remember that the project leader remains responsible for all tasks without an owner.
For each activity, assign one and only one owner, delegating responsibility for the work. Owners will be responsible for planning, estimating, monitoring a and reporting on the activity, but they will not necessarily do all the work alone. In some cases, owners will lead a team doing the work, or even serve as a liaison for outsourced tasks. For each activity, identify all needed skills, staff, and any other resources.
Identify Milestones
In addition to project activities, which consume time and effort, project schedules also have milestones—events used to synchronize project work and mark significant project transitions that have no duration. Uses for milestones include:
• Project start
• Project end
• Completion of related parallel activities
• Phase gates or life cycle stage transitions
• Significant decisions, approvals, or events
• Interfaces among multiple dependent projects
• Other external activity dependencies and deliverables
List all project milestones.
Document Activities
Document all activities and milestones in a database, software tool for project management, or some other appropriate format. Include activity names, owners, assumptions, deliverable descriptions, and other important information. The activity list (often part of a WBS Dictionary) serves as the foundation for project planning, risk analysis, execution, and control. Provide all activity owners a summary of their work.
Use activity definitions as a foundation for many other planning processes a including activity duration estimating, activity resource estimating, activity sequencing, schedule development, cost estimating, risk identification a required skills analysis, and responsibility analysis.
As the project planning and execution proceeds, keep activity information current. Periodically update the activity list to add work identified during the project.
Table of Contents
Introduction1. Activity definition (PMBOK® 6.1)
2. Activity duration estimating (PMBOK® 6.3)
3. Activity sequencing (PMBOK® 6.2)
4. Administrative closure (PMBOK® 10.4)
5. Brainstorming
6. Canceling projects
7. Cause and effect analysis
8. Coaching and mentoring
9. Communicating informally
10. Communications planning (PMBOK® 10.1)
11. Conflict resolution
12. Consensus building for your ideas
13. Constraint management and plan optimization
14. Contract administration (PMBOK® 12.5)
15. Contract closeout (PMBOK® 12.6)
16. Cost budgeting (PMBOK® 7.3)
17. Cost control (PMBOK® 7.4)
18. Cost estimating (PMBOK® 7.2)
19. Creative problem solving
20. Customer interviews
21. Decision making
22. Delegating responsibility
23. Delphi technique
24. Earned value management
25. Global teams ? crosscultural communication
26. Global teams ? crosscultural work styles
27. Influence without authority
28. Information distribution (PMBOK® 10.2)
29. Integrated change control (PMBOK® 4.3)
30. Leadership
31. Lessons learned
32. Market research
33. Matrix teams (crossfunctional teams)
34. Meeting preparation
35. Meeting execution
36. Motivation
37. Multiple dependent projects
38. Multiple independent projects
39. Negotiating contracts
40. Negotiating project changes
41. Organizational change
42. Organizational planning (PMBOK® 9.1)
43. Organizing for project management
44. Performance problem resolution
45. Performance reporting (PMBOK® 10.3)
46. Plan variance analysis
47. Presentations
48. Problem escalation
49. Process improvement
50. Procurement planning (PMBOK® 12.1)
51. Project baseline setting
52. Project charter
53. Project infrastructure
54. Project initiation (PMBOK® 5.1)
55. Project metrics ? diagnostic
56. Project metrics ? predictive
57. Project metrics ? retrospective
58. Project metrics ? selecting and implementing
59. Project objective (mission)
60. Project office
61. Project plan development (PMBOK® 4.1)
62. Project plan execution (PMBOK® 4.2)
63. Project priorities
64. Project review
65. Project vision
66. Qualitative risk analysis (PMBOK® 11.3)
67. Quality assurance (PMBOK® 8.2)
68. Quality control (PMBOK® 8.3)
69. Quality planning (PMBOK® 8.1)
70. Quantitative risk analysis (PMBOK® 11.4)
71. Required skills analysis
72. Resource leveling
73. Resource planning (PMBOK® 7.1)
74. Responsibility analysis
75. Return on investment analysis
76. Rewards and recognition
77. Risk identification (PMBOK® 11.2)
78. Risk management planning (PMBOK® 11.1)
79. Risk monitoring and control (PMBOK® 11.6)
80. Risk response planning (PMBOK® 11.5)
81. Schedule control (PMBOK® 6.5)
82. Schedule development (PMBOK® 6.4)
83. Scope change control (PMBOK® 5.5)
84. Scope definition (WBS) (PMBOK® 5.3)
85. Scope planning (PMBOK® 5.2)
86. Scope verification (PMBOK® 5.4)
87. Software tools for project management
88. Solicitation (PMBOK® 12.3)
89. Solicitation planning (PMBOK® 12.2)
90. Source selection (PMBOK® 12.4)
91. Sponsorship of projects
92. Staff acquisition (PMBOK® 9.2)
93. Start-up workshop
94. Status collection
95. Team development (PMBOK® 9.3)
96. Teamwork building and maintenance
97. Time management
98. Transitioning to project leadership
99. User needs assessment
100. Virtual teams ? technical tools