Tag Archives: Project Budgeting

New PM Articles for the Week of April 16 – 22

Posted on by
Reply

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

  • Shim Marom reviews the difference between accountability and responsibility.
  • Michael Krigsman considers the question: Who’s accountable for IT failure?
  • Joel Bancroft-Connors wants us to consider not just the probability of a failure, but the impact it will have.
  • Dhanu Kothari shares some sample criteria for troubled projects, and his roadmap for project recovery.
  • Don McAlister talks about when it is appropriate to re-baseline your project.
  • Jorge Valdes Garciatorres advocates getting mad.  When it’s justifiable, and professional.
  • Kenneth Hardin presents the thoughts of Mike Duensing, VP of Engineering at Mindjet, on ensuring your team understands risk, first-hand.
  • Todd Williams summarizes his thoughts on driving change, based on a white paper by Deanne Earle, “Principles for Intelligent Transition. “
  • Elizabeth Harrin interviews Microsoft’s Richard Gordon on the role of Sharepoint and the apparently slow rate of adoption of Project 2010.  Three minutes, safe for work.
  • Glen Alleman shares a fishbone diagram of some common sources of variance in project cost.
  • Steve Denning addresses ten perennial management-level objections to the adoption of Agile methods.  Including several pretty good ones.
  • Mike Griffiths looks at a Forbes article that argues Agile’s unlikely origins in software development may make it unlikely to be accepted in other management areas.
  • Matt Simpson explains the benefits of using Kanban in a software development project.
  • Meanwhile, Peter Saddington looks into reports that Kanban is failing Japanese industry.
  • Steve Ranger summarizes the findings of TechRepublic’s CIO Jury on the question of whether there is really a technical skills crisis.  Answer: no, but …
  • Jahna Berry reports on the “skills gap” between what employers are looking for and what they’re seeing in the applicant pool.
  • Paul Schoemaker reveals four secrets of great critical thinkers.
  • Josh Nankivel re-learns the old lesson: Just because you can doesn’t mean you should.
  • Kiron D. Bondale shares why and how you should develop a good relationship with Functional Managers.

Enjoy!

New PM Articles for the Week of March 12 – 18

Posted on by
Reply

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

  • Todd Williams  shares the lessons behind “pushing string” to lead your leaders to the right solution by changing the problem definition.
  • Jorge Valdés Garciatorre advocates seeking optimistic team members for project successes.
  • Mark Mullaly explores the risks of using social media in Project Management.
  • Chris Niccolls takes an in-depth look at outsourcing lessons learned.
  • Kiron D. Bondale advocates and explains the benefits of downtime between project assignments.
  • Mike Krutza explains why good managers give instructions, instead of orders.
  • Elizabeth Harrin collected causes of conflict in project management from the audience at her recent presentation at the Pink Elephant conference.
  • Dennis McCafferty presents his PowerPoint on five enterprise-level project management mistakes to avoid.
  • Ben Work talks with Tom Petrocelli: “Project management is a discipline, and task management is a skill.”
  • Bruce McGraw sees a disturbing trend – the devaluation of the professional project manager (as opposed to the PMP holder).
  • Geoff Crane offers some tips on how to find a job in the modern, post-job board world.
  • Premanand Doraiswamy and Premi Shiv have a new book out: “50 Top IT Project Management Challenges.”
  • Guy Smith and his team at Diageo (Guinness, Smirnoff, and others) have a new book out: “if It’s Not Impossible, It’s Not Interesting.”
  • Joel Bancroft-Connors and his gorilla, Hogarth, take a look at story estimating via the team estimation game, as an alternative to planning poker.
  • Derek Huether finds an example of a visual management system (mieruka, for you Toyota management system fans) while driving through a school zone.
  • Mike Griffiths looks at interruptions, flow, quiet time, and instant messaging.
  • Terry Rankin has coined the best new word of the month – “technosterone.”  Remember “sniglets?”
  • Ken Ritchie liked a story on the news about Sara Blakely and her father’s views on the value (!) of failing … and learning.

Enjoy!

New PM Articles for the Week of March 5 – 11

Posted on by
Reply

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

  • Ty Kiisel looks at motivation.  “Foster a sense of making progress on meaningful work.”
  • Geoff Crane recounts a dialog with his new friend, Emma Reynolds, of E3 Reloaded.  They believe that the recruitment process is broken.
  • Elizabeth Harrin picked up five tips on managing information overload while she was at the Pink Elephant conference last month.
  • Todd Williams tells us about his less than satisfying interaction with the head of a technology professional organization, on what might be a topic of interest for his membership.
  • Katia Sullivan continues her series on applying traditional project metrics, namely earned value, to Agile projects.
  • Joel Bancroft-Connors and his gorilla, Hogarth, take a look at the “slippery slope” that leads from ethical to Bernie Madoff.
  • Shim Marom looks at ethical issues as possible reason for high failure rates on software projects.
  • Greg Balestrero, former President and CEO at PMI, has joined IIL as a senior advisor to the team developing new training in Corporate Consciousness, Leadership and Sustainability.
  • Stacy Higginbotham believes the new iPad will have significant ramifications for corporate networks.
  • Johanna Rothman is finding one problem with distributed teams is time zones and daylight savings times.
  • Jordan Bortz shares (and comments on) a post he found from a frustrated coder on the perils of unrealistic expectations, even in an Agile approach.
  • James Grinnell looks at the difference between stretch goals and snap goals.
  • Ken Ritchie considers the difficulty in explaining what we do to people who aren’t in our line of work.
  • Bruce McGraw recounts the history of estimating project costs, and how it’s done these days on a project using Scrum.

Enjoy!