xviii Contents
- Get Users Involved As Early As Possible Agile Methods
- Keep It Simple, Simon
- Scrolling Through Time
- How to Spot a Good IT Developer
- Don’t Skip Vacations for the Project
- Empowering Developers: A Man Named Tim
- How Do You Define “Finished”?
- Work in Cycles
- Introduce a More Agile Communication System
- The Fallacy of Perfect Knowledge
- Favor the Now Over the Soon
- Serve Your Team
- The Best Estimators: Those Who Do the Work
- Can Earned Value and Velocity Coexist on Reports?
- Increase Communication: Hold Frequent, Instant Meetings
- Get Users Involved As Early As Possible Software Development
- Avoid Whack-a-Mole Development
- A Word Can Make You Miss Your Deadline
- Favor the Simple Over the Complex
- Pay Your Debts xvi Contents
- Go Ahead, Throw That Practice Out
- Provide Regular Time to Focus
- Clever Code Is Hard to Maintain.
- Developers Unite—PMOs Are Advancing
- Software Failure Is Organizational Failure
- A Voice from the Other Side
- How Do You Define “Finished”?
- The 60/60 Rule
- Work in Cycles
- The Fallacy of Perfect Execution
- The Fallacy of Perfect Knowledge
- Align Vision and Expected Outcome
- Alice Doesn’t Live Here Anymore
- Favor the Now Over the Soon
- The Fallacy of the Big Round Ball
- Know Your Integration Points
- Scope Change Happens; Get Used to It
- Buying Ready-Made Software
- Flexibility Simplifies Project Management
- The Web Points the Way, for Now
- Developers Hate Status Reports, Managers Love Them
- Avoid Whack-a-Mole Development Managing People and Teams
- Add Talents, Not Skills, to Your Team
- You Aren’t Special
- How to Spot a Good IT Developer
- Developer Productivity: Skilled Versus Average
- Success Is Always Measured in Business Value
- Empowering Developers: A Man Named Tim
- Clever Code Is Hard to Maintain.
- Managing Human Factors in IT Project Management
- The Missing Link Contents xvii
- Estimate, Estimate, Estimate
- Value Results, Not Just Effort
- Software Failure Is Organizational Failure
- We Have Met the Enemy...and He Is Us
- Work in Cycles
- Meetings Don’t Write Code
- Chart a Course for Change
- One Deliverable, One Person
- Build Teams to Run Marathons, Not Sprints
- The Holy Trinity of Project Management
- Align Vision and Expected Outcome
- You Get What You Measure
- Building the Morale on Your Team
- A Project Depends on Teamwork
- The Best Estimators: Those Who Do the Work
- It’s the People, Stupid
- Teach the Process
- The Fallacy of Status
- Recognize the Value of Team Morale
- A Word Can Make You Miss Your Deadline International Issues or Distributed Teams
- Make Project Sponsors Write Their Own Requirements
- Requirement Specifications: An Oxymoron
- IT Program Management: Shared Vision
- Don’t Worship a Methodology.
- Alice Doesn’t Live Here Anymore
- Aggressively Promote Communication in Distributed Projects
- Communicating Is Key
- Developers Hate Status Reports, Managers Love Them
- You Are Not in Control
- Share the Vision
- Size Matters Managing Projects
- Document Your Process, Then Make Sure It Is Followed
- Project Management Is Problem Management
- Use a Wiki.
- How Do You Define “Finished”?
- The 60/60 Rule
- IT Program Management: Shared Vision
- Planning for Reality
- Responding to a Crisis
- Start with the End in Mind
- Documents Are a Means, Not an End
- Should You Under-Promise, or Over-Deliver?
- Important, but Not Urgent
- Effectively Manage the Deliverables
- Developer Productivity: Skilled Versus Average Communications
- Use a Wiki.
- Developers Unite—PMOs Are Advancing
- Meetings Don’t Write Code
- Introduce a More Agile Communication System
- Roadmaps: What Have We Done for You Lately?
- Aggressively Promote Communication in Distributed Projects
- Communicating Is Key
- It’s the People, Stupid
- Project Sponsors—Good, Bad, and Ugly
- Every Project Manager Is a Contract Administrator
- What Do They Want to Hear, Anyway?
- Engage Stakeholders All Through Project Life
- Don’t Always Be “The Messenger”
- Increase Communication: Hold Frequent, Instant Meetings