Welcome to Project Management — You Poor Soul
Why Would Anyone Choose This Life? (Oh, You Didn’t? Too Late.)
- Project Manager: The Job You Thought You Signed Up For vs. The Reality
- The Five Stages of Project Grief
- The PM Starter Pack: Tools, Skills, and How to Fake Confidence
- The Unwritten Rules of Project Management
- Setting Boundaries Early (or Suffer Later)
- Why Your First Project Plan Will Fail (And How to Handle It)
- The Difference Between a Good PM and a Burned-Out One
- Welcome to the Madness—Why You’ll Keep Doing This Anyway
Stakeholders—A Fancy Word for “Your Future Nightmares”
How to Handle Indecisive Execs, Clueless End-Users, and the One Guy Who Disappears Until Launch Day
- Who Actually Has Power In Your Project? (And Who Just Likes to Send Emails?)
- The Three Stakeholder Types You’ll Deal With (Like It or Not)
- How to Manage Stakeholder Expectations (Without Losing Your Mind)
- How to Survive Stakeholder Feedback Without Losing Your Will to Live
- How to Handle Stakeholders Who Disappear Until the Last Minute
- The Stakeholder Who Wants Everything (But Won’t Make a Decision)
- The Stakeholder Who Always Wants “Just One More Thing”
- Stakeholder Survival Strategies
Business Requirements—Where Dreams Go to Die
How “Just a Small Change” Becomes a Six-Month Delay
3.1. Why Clients Never Know What They Actually Want
3.2. The Great Requirements Gathering Circus
3.3. Scope Creep: What It Is, Why It Happens, and How to Shut It Down
3.4. The MoSCoW Method vs. The FML Method
3.5. MoSCoW: Sorting “Must-have” from “Nice-to-have” before it’s too late.
3.5. Handling Conflicting Requirements Like a Pro
3.6. Managing Revisions Without Losing Your Mind
3.7. Business Requirements Common Problems & How to Survive Them
3.8. Business Requirements Survival Strategies
IT Project Tender Process — Vendor Hunger Games
How to Win Contracts Without Selling Your Soul (or Your Profits)
4.1. Why the Tender Process is Designed to Waste Your Time
4.2. How to Decode a Vague RFP Without Losing Your Mind
4.3. Should You Even Bid? (Or Are You Just Being Set Up to Lose?)
4.4. The Three Golden Rules of Writing a Winning Proposal
4.5. The Q&A Round: How to Ask Smart Questions Without Giving Away Free
4.6. Surviving the Client’s Vendor Evaluation Process
4.7. Negotiation Tactics to Protect Your Time, Scope, and Profits
4.8. Common Problems & How to Survive Them
4.9. Tender Process Survival Strategies
Project Contracts—Selling Your Soul, But Legally
How to Avoid Getting Screwed Before the Project Even Starts
5.1. Why Every Contract is a Trap (If You Don’t Read It Carefully)
5.2. The Hidden Clauses That Can Destroy Your Project
5.3. Why “subject to change” means you’re about to get scope creeped into oblivion.
5.3. Service Level Agreements (SLAs): What to Promise and What to Avoid
5.4. How to Handle the “Legal Team Review” Without Losing Your Mind
5.5. The IP Ownership Battle: Who Owns What, and Why It Matters
5.6. Payment Terms: The Only Clause That Really Matters
5.7. The Kill Clause: How to Escape a Dying Project Without Losing Everything
5.8. Common Problems & How to Survive Them
5.9. Contract Survival Strategies
Project Kickoff—Hope, Optimism, and the Beginning of the End
How to Smile Through the First Meeting While Internally Screaming
6.1 The Kickoff Meeting: The Only Time Everyone Pretends to Agree
6.2 The Kickoff Meeting Survival Kit: What to Prepare Beforehand
6.3 How to Set Expectations Without Sounding Like a Jerk
6.4 How to Handle Scope Before It Spirals Out of Control
6.5 Risk Management: Identifying Disasters Before They Happen
6.6 Communication Plans: How Often Should You Email?
6.7 When the Client Changes Their Mind Immediately After Kickoff
6.8 Common Problems & How to Survive Them
6.9 Kickoff Meeting Survival Strategies
Development Phase—Where Timelines Go to Die
Why “It’ll Take Two Weeks” is the Biggest Lie in IT
7.1 The Beautiful, Delusional Fantasy of a Perfect Development Cycle
7.2 Agile vs. Waterfall vs. “We Have No Plan, Just Start Coding”
7.3 Why Developers Always Say “It’ll Take Two Weeks” (And Why It Won’t)
7.4 The Code Review Conundrum: A Necessary Evil
7.5 The Dark Side of Technical Debt: What Happens When You Rush Development
7.6 Unit Testing: You’ll Regret Skipping This Step
7.7 Standup Meetings: A Daily Reminder That Everything is Behind Schedule
7.8 How to Handle Mid-Development Surprises Without Derailing the Project
7.9 Development Phase Common Problems & How to Survive Them
7.10 Development Phase Survival Strategies
Integration Testing—Congratulations, Nothing Works
Why APIs Never Connect on the First Try
8.1 Why Integration Testing is Where Projects Go to Die
8.2 The API Disaster You Didn’t See Coming
8.3 Data Migrations: Moving Information Without Losing Your Mind
8.4 Security Testing: Making Sure Your System Isn’t Wide Open to Hackers
8.5 Performance Testing: Will It Crash Under Load? (Yes.)
8.6 The Never-Ending Cycle of Bug Fixes
8.7 How to Get Clients to Actually Participate in Testing
8.8 Integration Testing Common Problems & How to Survive Them
8.9 Integration Testing Survival Strategies
User Acceptance Testing (UAT)—Where Users Break Everything You Built
Why End-Users Will Click the One Button They Shouldn’t
9.1 What is User Acceptance Testing (UAT) and Why Does It Always Go Wrong?
9.2 Why Clients Never Test the System Until the Last Minute
9.3 The User Test Cases That Will Save Your Sanity
9.4 Managing Bug Reports Without Losing Your Mind
9.5 The Art of Handling Feedback Without Derailing the Project
9.6 “It’s Not a Bug, It’s a Feature”: The Great PM Lie
9.7 The Last-Minute Panic Before UAT Sign-Off
9.8 Common Problems & How to Survive Them
9.9 User Acceptance Testing (UAT) Survival Strategies
Software Deployment—Or as We Call It, Panic Day
Why Your System Will Fail the Moment It Goes Live
10.1 Welcome to Deployment—Hope You Like Stress
10.2 Big Bang vs. Phased Rollout: Which One Will Ruin Your Life Less?
10.3 The Final Pre-Launch Checklist (a.k.a. The Last Chance to Fix Things)
10.4 The Rollback Plan: Because Something Will Go Wrong
10.5 Why Deployment Happens at 2 AM (and Why You’ll Be Up at 4 AM Fixing It)
10.6 The First 24 Hours: What to Monitor and How to Respond
10.7 The Client Freakout: How to Manage Panic Like a Pro
10.8 Deployment Common Problems & How to Survive Them
10.9 Deployment Survival Strategies
Post-Go-Live—Welcome to Production Hell
Why Everything is on Fire, and It’s Somehow Your Problem
11.1 The Myth of “Smooth Launches” and Why They Don’t Exist
11.2 Hypercare: The Few Weeks Where Everything is on Fire
11.3 Bugs, Hotfixes, and the “We’ll Patch It Later” Lie
11.4 User Complaints: How to Handle the Inevitable Backlash
11.5 Performance Monitoring: Keeping an Eye on a System That’s Live
11.6 Support Requests: How to Keep Clients from Treating You Like Their IT Helpdesk
11.7 When the Client Wants Post-Launch “Tweaks” That Are Actually Major Changes
11.8 Common Problems & How to Survive Them
11.9 Post-Go-Live Survival Strategies
Maintenance & The Never-Ending Nightmare
Why “Post-Launch” Doesn’t Mean “Done”
12.1 Welcome to the Maintenance Phase—Hope You Like Support Tickets
12.2 Why Bug Fixes Are Never “Quick”
12.3 Security Patches: A Necessary Evil
12.4 Feature Requests Disguised as “Minor Enhancements”
12.5 The Battle Over System Performance
12.6 Handling Support Contracts Without Becoming a Full-Time Babysitter
12.7 When to Walk Away: Ending a Maintenance Contract Gracefully
12.8 Common Problems & How to Survive Them
12.9 Maintenance Survival Strategies
Project Closure—Finally, You’re Free (Almost)
How to Escape Without Getting Pulled Back In
13.1 Why Closing a Project is Harder Than Starting One
13.2 The Final Deliverables Checklist: Wrapping Up Without Loose Ends
13.3 Lessons Learned: Will Anyone Actually Read This?
13.4 The Final Client Handoff: Making Sure They Own Their System
13.5 Invoices, Payments, and The Great Money Chase
13.6 When the Client Comes Back With “Just One More Thing”
13.7 The Final Email: How to Exit Like a Professional
13.8 Common Problems & How to Survive Them
13.9 Project Closure Survival Strategies