Execution begins, and this chapter is your control center. It details how to collect meaningful status data—not just "percentage complete" guesstimates, but objective metrics on milestones and deliverables. Portny teaches variance analysis, comparing actual progress against your baseline schedule and budget. Crucially, he introduces a formal Change Control Process to manage scope creep: how to submit, evaluate, and approve change requests without derailing the entire project. You learn the art of running effective progress review meetings that focus on problem-solving rather than finger-pointing.
Chapter 15: Keeping Everyone Informed
Communication is the lubricant of project machinery. This chapter helps you build a tailored communications plan
that specifies who needs what information, via which channel (email,
dashboard, meeting, phone), and at what frequency. Portny champions the
"one-page status report"—a succinct executive summary that respects
sponsors' time while providing enough detail for governance. You also
learn how to craft difficult messages (bad news, delays, budget
overruns) with honesty and diplomacy, ensuring that stakeholders are
never surprised and always trust your transparency.
Chapter 16: Encouraging Peak Performance by Providing Effective Leadership
This
chapter distinguishes between managing tasks and leading people. Portny
dives into motivational theories (Maslow, Herzberg, McGregor) and
applies them practically to project environments. He covers conflict
resolution modes (collaborating, compromising, competing, accommodating,
avoiding) and when to deploy each. You learn situational
leadership—adapting your style (directing, coaching, supporting,
delegating) based on team members' competence and commitment. The
ultimate lesson: your technical skills get you hired, but your emotional
intelligence, empathy, and ability to inspire get the project finished
successfully.
Chapter 17: Bringing Your Project to Closure
The
finish line is not the end; it's a learning opportunity. This chapter
ensures you don't abandon your project post-delivery. Portny details
formal closure activities: obtaining final acceptance from the sponsor,
handing off deliverables to operations, releasing team members
gracefully, and closing contracts with vendors. The most valuable
section covers the post-mortem / lessons learned
session—a structured retrospective that captures what went well, what
went wrong, and what could be improved. Archiving this knowledge ensures
your organization's collective intelligence grows with every single
project.
Comments
Post a Comment