Review: The Software Project Manager's Handbook

The Software Project Manager's Handbook by Dwayne Phillips

My rating: 0 of 5 stars



• "Visibility and communication are more important than [choice of technology]"
• "[Handle] maintenance projects so that no one feels like a second-class citizen"
• One of my favorites: "Choose the best people, keep the team small, minimize distractions, train them, meet together as a team regularly, know them, and set an example"
• Cherry-picked from 1.3.2 Best Practices “a best practices list compiled from the best practices lists of many well-known authors:
o Reviews, inspections, and walkthroughs
o Binary quality decision gates
o Milestones
o Visibility of plans and progress
o Defect tracking
o Testing early and often
o Fewer, better people
o Opposition of featuritis and creeping requirements
o Documentation for everything
o Change management
o Reusable items
o Project tracking
o Users - understanding them
o Buy in and ownership of the project by all participants
o Requirements
• “Avoid having team members work in isolation”
• “Keep…notes of everything you learn”
• “use standards judiciously”
• “You cannot build a more difficult product without increasing capability”




View all my reviews