New project management articles published on the web during the week of July 23 – 29, 2012.  Dave and Sandra read all of this stuff so you don’t have to!  Recommended:

• Peter Saddington shares five tips for building relationships at a client.
• Vincent McGevna applies risk management to developing the project schedule.
• Gary Nelson considers shampoo, telescopes, sunbathers, and skiing on the way to telling us we should periodically re-plan our projects.  Quite a journey!
• Jesse Fewell says, “If you want successful projects, do less work.”
• Elizabeth Harrin identifies four reasons your project board (or steering committee) isn’t working.
• Andy Jordan addresses the leadership aspects of managing a large project.
• Rick Freedman notes that the confusion created by having project team members filling multiple roles can be mitigated, with a little management.
• Shim Marom explains the terms earned value, earned value management, and earned value management system.
• Glen Alleman points out the missing element in our project management methods: we don’t define and manage the delivery of capabilities.
• Christine Otis describes the synergies achieved by program managers and project managers working together.
• Kevin Korterud shares some practices for developing the program management mindset.
• Gareth Byatt, Gary Hamilton, Jeff Hodgkinson and Duke Okes explain how to measure the value of a program management office.
• Taralyn Frasqueri-Molina just finished Scrum Master training, and learned that it’s not either Scrum / or traditional approaches – you do what’s appropriate.
• Jordan Bortz argues that we should return to the pre-Snowbird conference terminology of “lightweight methodologies,” instead of “Agile.”
• Joel Bancroft-Connors and Hogarth take a look at Agile development from a financial accounting perspective.  Agile lets you start capitalizing sooner?  Who knew?
• Hass Chapman is convinced senior management will never “get” Agile.
• Derek Huether wants us to think in terms of a qualified user story.
• Tom Mochal  looks at various cases for the duration of an Agile iteration – from 30 days to two weeks or less.
• Johanna Rothman wants us to manage technical debt – both current and legacy – in our Agile projects.

Enjoy!