Rescue the Problem Project – Identifying, Preventing, and Recovering from Project Failure

Todd WilliamsI had the distinct pleasure to sit down with Todd Williams and talk about his upcoming book Rescue the Problem Project: A Complete Guide to Identifying, Preventing, and Recovering from Project Failure. The book will be released in March 2011 by AMACOM Books.

Todd shares with us his Project Recovery framework that helps Project Manager’s rescue failing projects while focusing on root cause correction and prevention.

In this interview, we cover these 6 big ideas:

  • Understanding the Recovery Process and Realizing there is a Problem
  • Auditing the Project: Understanding the Issues
  • Analyzing the Data: Planning for Project Recovery
  • Negotiating a Solution: Proposing Workable Resolutions
  • Executing the New Plan: Implementing the Solutions
  • Doing It Right the First Time: Avoiding Problems That Lead to Red Projects

Todd’s experience, which covers many domains inside manufacturing and service industries, is drawn from working on internal and third-party projects, including integration of manufacturing systems, implementation of web-based collaboration systems, and large-scale business systems integration.

His cultural experience includes the Pacific Rim, Middle East and North America, coordinating teams dispersed in as many as five countries, three continents and countless time zones

As President of eCameron, Inc., located outside Portland, Oregon, he is considered an expert in rescuing projects and preventing their failure.  His popular blog Back from Red, which is getting over 400 hits per day, has been quoted on ZDNet, The Center for CIO Leadership, CIO Essentials, IT Business Edge, and Project Managers Planet.

The Interview:

Listen now:

Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.

Right click here to download the MP3


PART I Understanding the Recovery Process and Realizing there is a Problem

  • What are the basics of the project recovery process?
  • What measures should an organization consider when it realizes that a project has become Red?

    PART 2 Auditing the Project: Understanding the Issues

    • In auditing the project to understand the issues, you recommend that the project manager:
      • Assess the Human Role in Project Failure
      • Audit Scope on a Red Project
      • Determine Timeline Constraints
      • Examine Technology’s Effect on the Project
    • How to you assess the human factors in project failure?
    • When you audit the scope, what do you look for?
    • How do you go about determining the timeline constraints?
    • Why is it important to examine the Technical Expertise in the project and what are the typical issues you find when you examine the technology effect on the project?

    PART 3 Analyzing the Data: Planning for Project Recovery

    • What steps do you take to initiate remedial action?
    • How do you make sure the team is capable of turning around the project?
    • What should we consider when we need to deal with technology-related issues?
    • What’s the role of methodology in project failure and project recovery effort?
    • How can Agile methodology help in project recovery effort?

    PART 4 Negotiating a Solution: Proposing Workable Resolutions

    • What challenges a recovery manager faces when negotiating a Recovery Plan?
    • You warn against “Unprojects”, define for us “Unprojects” and how should we deal with them?

    PART 5 Executing the New Plan: Implementing the Solutions

    • What challenges the Recovery Manager faces during execution phase of the Recovery Plan?

    PART 6 Doing It Right the First Time: Avoiding Problems That Lead to Red Projects

    • To avoid problems that lead to Red Project, you focus on the following key elements:
      • Defining a Project’s Initiation
      • Assembling the Right Team
      • Properly Dealing with Risk
      • Implementing Effective Change

    Can you cover each of these 4 topics and your recommendation for how to avoid problems in each area that lead to Red Projects?

    About Todd Williams:

    For twenty-five years Presidents, Vice Presidents, and C-Level executives of manufacturing and service companies have asked Mr. Todd Williams to help them build leading-edge systems, improve organizational efficiency, and turn-around troubled projects.  From this experience, he has developed methods to streamline organizations, recover red projects and help prevent recurring failures.

    Todd’s experience, which covers many domains inside manufacturing and service industries, is drawn from working on internal and third-party projects, including integration of manufacturing systems, equipment integration, web-based collaboration tools, thick clients with automated internet update, and large-scale business systems integration.

    His cultural experience includes the Pacific Rim, Middle East and North America, coordinating teams dispersed in as many as five countries, three continents and countless time zones. Over the years, he developed a team philosophy that he finds critical in recovering projects.

    Find more information:

    Listen now:

    Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.

    Right click here to download the MP3

    Credits…

    Our opening and closing theme song is music by the wonderful Paul Hardcastle and www.paulhardcastle.com

    There are no comments yet. Be the first and leave a response!

    Leave a Reply

    Wanting to leave an <em>phasis on your comment?

    Trackback URL http://www.guerrillaprojectmanagement.com/rescue-the-problem-project/trackback

    Rescue the Problem Project – Identifying, Preventing, and Recovering from Project Failure

    Todd WilliamsI had the distinct pleasure to sit down with Todd Williams and talk about his upcoming book Rescue the Problem Project: A Complete Guide to Identifying, Preventing, and Recovering from Project Failure. The book will be released in March 2011 by AMACOM Books.

    Todd shares with us his Project Recovery framework that helps Project Manager’s rescue failing projects while focusing on root cause correction and prevention.

    In this interview, we cover these 6 big ideas:

    • Understanding the Recovery Process and Realizing there is a Problem
    • Auditing the Project: Understanding the Issues
    • Analyzing the Data: Planning for Project Recovery
    • Negotiating a Solution: Proposing Workable Resolutions
    • Executing the New Plan: Implementing the Solutions
    • Doing It Right the First Time: Avoiding Problems That Lead to Red Projects

    Todd’s experience, which covers many domains inside manufacturing and service industries, is drawn from working on internal and third-party projects, including integration of manufacturing systems, implementation of web-based collaboration systems, and large-scale business systems integration.

    His cultural experience includes the Pacific Rim, Middle East and North America, coordinating teams dispersed in as many as five countries, three continents and countless time zones

    As President of eCameron, Inc., located outside Portland, Oregon, he is considered an expert in rescuing projects and preventing their failure.  His popular blog Back from Red, which is getting over 400 hits per day, has been quoted on ZDNet, The Center for CIO Leadership, CIO Essentials, IT Business Edge, and Project Managers Planet.

    The Interview:

    Listen now:

    Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.

    Right click here to download the MP3


    PART I Understanding the Recovery Process and Realizing there is a Problem

    • What are the basics of the project recovery process?
    • What measures should an organization consider when it realizes that a project has become Red?

      PART 2 Auditing the Project: Understanding the Issues

      • In auditing the project to understand the issues, you recommend that the project manager:
        • Assess the Human Role in Project Failure
        • Audit Scope on a Red Project
        • Determine Timeline Constraints
        • Examine Technology’s Effect on the Project
      • How to you assess the human factors in project failure?
      • When you audit the scope, what do you look for?
      • How do you go about determining the timeline constraints?
      • Why is it important to examine the Technical Expertise in the project and what are the typical issues you find when you examine the technology effect on the project?

      PART 3 Analyzing the Data: Planning for Project Recovery

      • What steps do you take to initiate remedial action?
      • How do you make sure the team is capable of turning around the project?
      • What should we consider when we need to deal with technology-related issues?
      • What’s the role of methodology in project failure and project recovery effort?
      • How can Agile methodology help in project recovery effort?

      PART 4 Negotiating a Solution: Proposing Workable Resolutions

      • What challenges a recovery manager faces when negotiating a Recovery Plan?
      • You warn against “Unprojects”, define for us “Unprojects” and how should we deal with them?

      PART 5 Executing the New Plan: Implementing the Solutions

      • What challenges the Recovery Manager faces during execution phase of the Recovery Plan?

      PART 6 Doing It Right the First Time: Avoiding Problems That Lead to Red Projects

      • To avoid problems that lead to Red Project, you focus on the following key elements:
        • Defining a Project’s Initiation
        • Assembling the Right Team
        • Properly Dealing with Risk
        • Implementing Effective Change

      Can you cover each of these 4 topics and your recommendation for how to avoid problems in each area that lead to Red Projects?

      About Todd Williams:

      For twenty-five years Presidents, Vice Presidents, and C-Level executives of manufacturing and service companies have asked Mr. Todd Williams to help them build leading-edge systems, improve organizational efficiency, and turn-around troubled projects.  From this experience, he has developed methods to streamline organizations, recover red projects and help prevent recurring failures.

      Todd’s experience, which covers many domains inside manufacturing and service industries, is drawn from working on internal and third-party projects, including integration of manufacturing systems, equipment integration, web-based collaboration tools, thick clients with automated internet update, and large-scale business systems integration.

      His cultural experience includes the Pacific Rim, Middle East and North America, coordinating teams dispersed in as many as five countries, three continents and countless time zones. Over the years, he developed a team philosophy that he finds critical in recovering projects.

      Find more information:

      Listen now:

      Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.

      Right click here to download the MP3

      Credits…

      Our opening and closing theme song is music by the wonderful Paul Hardcastle and www.paulhardcastle.com

      There are no comments yet. Be the first and leave a response!

      Leave a Reply

      Wanting to leave an <em>phasis on your comment?

      Trackback URL http://www.guerrillaprojectmanagement.com/rescue-the-problem-project/trackback

      Rescue the Problem Project – Identifying, Preventing, and Recovering from Project Failure

      Todd WilliamsI had the distinct pleasure to sit down with Todd Williams and talk about his upcoming book Rescue the Problem Project: A Complete Guide to Identifying, Preventing, and Recovering from Project Failure. The book will be released in March 2011 by AMACOM Books.

      Todd shares with us his Project Recovery framework that helps Project Manager’s rescue failing projects while focusing on root cause correction and prevention.

      In this interview, we cover these 6 big ideas:

      • Understanding the Recovery Process and Realizing there is a Problem
      • Auditing the Project: Understanding the Issues
      • Analyzing the Data: Planning for Project Recovery
      • Negotiating a Solution: Proposing Workable Resolutions
      • Executing the New Plan: Implementing the Solutions
      • Doing It Right the First Time: Avoiding Problems That Lead to Red Projects

      Todd’s experience, which covers many domains inside manufacturing and service industries, is drawn from working on internal and third-party projects, including integration of manufacturing systems, implementation of web-based collaboration systems, and large-scale business systems integration.

      His cultural experience includes the Pacific Rim, Middle East and North America, coordinating teams dispersed in as many as five countries, three continents and countless time zones

      As President of eCameron, Inc., located outside Portland, Oregon, he is considered an expert in rescuing projects and preventing their failure.  His popular blog Back from Red, which is getting over 400 hits per day, has been quoted on ZDNet, The Center for CIO Leadership, CIO Essentials, IT Business Edge, and Project Managers Planet.

      The Interview:

      Listen now:

      Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.

      Right click here to download the MP3


      PART I Understanding the Recovery Process and Realizing there is a Problem

      • What are the basics of the project recovery process?
      • What measures should an organization consider when it realizes that a project has become Red?

        PART 2 Auditing the Project: Understanding the Issues

        • In auditing the project to understand the issues, you recommend that the project manager:
          • Assess the Human Role in Project Failure
          • Audit Scope on a Red Project
          • Determine Timeline Constraints
          • Examine Technology’s Effect on the Project
        • How to you assess the human factors in project failure?
        • When you audit the scope, what do you look for?
        • How do you go about determining the timeline constraints?
        • Why is it important to examine the Technical Expertise in the project and what are the typical issues you find when you examine the technology effect on the project?

        PART 3 Analyzing the Data: Planning for Project Recovery

        • What steps do you take to initiate remedial action?
        • How do you make sure the team is capable of turning around the project?
        • What should we consider when we need to deal with technology-related issues?
        • What’s the role of methodology in project failure and project recovery effort?
        • How can Agile methodology help in project recovery effort?

        PART 4 Negotiating a Solution: Proposing Workable Resolutions

        • What challenges a recovery manager faces when negotiating a Recovery Plan?
        • You warn against “Unprojects”, define for us “Unprojects” and how should we deal with them?

        PART 5 Executing the New Plan: Implementing the Solutions

        • What challenges the Recovery Manager faces during execution phase of the Recovery Plan?

        PART 6 Doing It Right the First Time: Avoiding Problems That Lead to Red Projects

        • To avoid problems that lead to Red Project, you focus on the following key elements:
          • Defining a Project’s Initiation
          • Assembling the Right Team
          • Properly Dealing with Risk
          • Implementing Effective Change

        Can you cover each of these 4 topics and your recommendation for how to avoid problems in each area that lead to Red Projects?

        About Todd Williams:

        For twenty-five years Presidents, Vice Presidents, and C-Level executives of manufacturing and service companies have asked Mr. Todd Williams to help them build leading-edge systems, improve organizational efficiency, and turn-around troubled projects.  From this experience, he has developed methods to streamline organizations, recover red projects and help prevent recurring failures.

        Todd’s experience, which covers many domains inside manufacturing and service industries, is drawn from working on internal and third-party projects, including integration of manufacturing systems, equipment integration, web-based collaboration tools, thick clients with automated internet update, and large-scale business systems integration.

        His cultural experience includes the Pacific Rim, Middle East and North America, coordinating teams dispersed in as many as five countries, three continents and countless time zones. Over the years, he developed a team philosophy that he finds critical in recovering projects.

        Find more information:

        Listen now:

        Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.

        Right click here to download the MP3

        Credits…

        Our opening and closing theme song is music by the wonderful Paul Hardcastle and www.paulhardcastle.com

        There are no comments yet. Be the first and leave a response!

        Leave a Reply

        Wanting to leave an <em>phasis on your comment?

        Trackback URL http://www.guerrillaprojectmanagement.com/rescue-the-problem-project/trackback