Leading Culture Change in Software Organizations: Delivering Meaningful Results Early

  • View
    42

  • Download
    1

Embed Size (px)

DESCRIPTION

Leading Culture Change in Software Organizations: Delivering Meaningful Results Early. Rita Hadden February 2004 ASEE Conference. We will look at:. Why is culture change important to software organizations? How to effectively lead culture change? How to deliver meaningful results early? - PowerPoint PPT Presentation

Text of Leading Culture Change in Software Organizations: Delivering Meaningful Results Early

  • Leading Culture Change in Software Organizations:Delivering Meaningful Results EarlyRita HaddenFebruary 2004 ASEE Conference

    Proprietary - Do not use without written permission

  • We will look at:Why is culture change important to software organizations?How to effectively lead culture change?How to deliver meaningful results early?Questions?

    Proprietary - Do not use without written permission

  • Why is culture change important to software organizations? Increasing project complexity.Software jobs are going overseas.Many software process improvement (SPI) efforts in U.S. have failed, often due to inability to produce quick and meaningful results.Mandated change is expensive to sustain.

    Proprietary - Do not use without written permission

  • How to effectively lead culture change?

    Proprietary - Do not use without written permission

  • Who is a Change Leader?

    A change leader can be a practitioner, a manager, a customer, a stakeholder, a software user, a process engineer, or an executive.

    When an individual inspires others to apply best practices intelligently in a way that delivers results more effectively or efficiently, this individual is a leader in your change effort.

    Proprietary - Do not use without written permission

  • Effective Change Leaders: Software Practitioners

    Proprietary - Do not use without written permission

  • Effective Change Leaders - Software Practitioners: Actions They TakeBelieve positive change can happenLearn and apply best practicesFocus on actions that produce results earlyReact to critical incidents effectivelyAct as role model and coach others

    Proprietary - Do not use without written permission

  • Effective Change Leaders - SoftwareProject Managers

    Proprietary - Do not use without written permission

  • Demonstrate visible and active involvement in change initiative Encourage participation and let the people drive the change Focus on actions that produce results early Estimate time and effort realistically Act as role model and coach staff Make it safe and rewarding to adopt best practices Use professional judgmentEffective Change Leaders - Software Project Managers: Actions They Take

    Proprietary - Do not use without written permission

  • Effective Change Leaders - Software Executives

    Proprietary - Do not use without written permission

  • Effective Change Leaders - Software Executives: Actions They Take Create a climate where change can succeed Limit number of top priorities Be realistic about funding and time Demonstrate visible involvement and ownership Communicate benefits of change often React to critical incidents effectively Reward improvements Believe it can happen Stay the course for the long term

    Proprietary - Do not use without written permission

  • How to deliver meaningful results earlyInsist on five best practices for any projectProactively remove barriers to successful software process improvement (those you can affect)

    Proprietary - Do not use without written permission

  • Insist on five best practices for any project

    1.Work with your customers to clearly define, validate, prioritize, agree on requirements and perform change control.

    2.Carefully plan before executing your project, developing specific strategies to address key concerns early in your project lifecycle.

    Proprietary - Do not use without written permission

  • Insist on five best practices for any project (2)3.Track your progress by key work products, not just milestones. Take early corrective actions. Promptly resolve issues, external dependencies, and risks, escalating proactively.

    4.Perform effective peer reviews for your key work products. 5.Manage your configuration items throughout your project lifecycle.

    Proprietary - Do not use without written permission

  • Proactively remove barriers to successful software process improvementVision-related barriersSkills-related barriersRewards-related barriersResources-related barriersAction Plan-related barriers

    Proprietary - Do not use without written permission

  • Industry findingsCommercial companies survival is critically dependent on developing and fielding software in a predictable and disciplined manner.Benchmarking revealed that successful commercial companies are bottom-line driven and focus improvement activities on the big cost and schedule driversWhile process improvement serves as a floodlight on what can be done, best practices are the laser beam, pinpointing high-leverage activities directly coupled to the bottom-line.

    Proprietary - Do not use without written permission

  • 17

    Proprietary - Do not use without written permission

  • For More InformationContact Rita HaddenDirector of Software DevelopmentDatatel, Inc.Fairfax, VA703-802-2927rch@datatel.com

    Proprietary - Do not use without written permission

    Dallas2004, v.0.1Dallas2004, v.0.1Dallas2004, v.0.1Dallas2004, v.0.1Dallas2004, v.0.1

    Dallas2004, v.0.1Dallas2004, v.0.1

    Dallas2004, v.0.1Dallas2004, v.0.1

    Dallas2004, v.0.1Dallas2004, v.0.1

    Dallas2004, v.0.1

    Dallas2004, v.0.1

    Dallas2004, v.0.1Dallas2004, v.0.1

    Dallas2004, v.0.1Dallas2004, v.0.1Dallas2004, v.0.1