New PM Articles for the Week of March 26 – April 1

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

  • Kiron D. Bondale talks about why a PM would take on multiple roles in a project and what the impacts can be.
  • Elizabeth Harrin interviews Ben Snyder, author of “Everything is a Project.”
  • Samad Aidane interviews Kate Nelson on Change Readiness Reviews.  Just 19 minutes, safe for work.
  • Sam Palani reviews “Rework,” by Jason Fried and David Heinemeier Hansson.
  • Mike Krutza focuses on the important topic of boosting employee engagement.
  • Vijay Vijayasankar walks us through balancing the blessing and curse of shiny objects, otherwise known as new technology.
  • Andy Jordan recounts the traumatic experience of integrating a PMO so that we can learn from his lessons.
  • Gary Hamilton, Gareth Byatt, and Jeff Hodgkinson address the question: should project managers be professionally licensed or chartered?
  • Steve Ranger summarizes research by Forrester Consulting that says “Two thirds of CIOs now believe their business sees cloud computing as a way to circumvent IT.”
  • Bruce Benson shares his thoughts on why we don’t “have to do something” when things are going badly.
  • Philip Carrizosa reports that California’s Judicial Council has finally put the brakes on their runaway Court Case Management System project. Hoping for lessons learned.
  • Bernadine Douglas suggests we use the same technology we’ve been using for virtual team meetings to conduct our lessons learned meeting.
  • Joel Bancroft-Connors considers the notion that Agile is becoming a fad, and maybe that’s a good thing.  Or, a bad thing.  Or maybe something else.
  • Tom Mochal explains a bit about iteration planning, using Scrum terminology without actually using the word “Scrum.”  Neat trick!
  • Ken Hardin has some tips for creating a successful deliverables-based statement of work.
  • Stuart James has another list of critical issues for the Agile development project SOW.
  • Todd Williams has an interesting example for resistance to change – a new way to tie your shoes.
  • Craig Brown shares a new tool – the Burn Up Chart.  No, this is not an April Fool’s Day gag.
  • Peter Saddington finds a truly “worst case scenario” for replacing a legacy system – the original developer died.  Check out Jordan’s comment at the bottom of the page!