The case for agile development
This presentation is the property of its rightful owner.
Sponsored Links
1 / 24

The Case for Agile Development PowerPoint PPT Presentation


  • 55 Views
  • Uploaded on
  • Presentation posted in: General

The Case for Agile Development. Creative Disruption: A Core Systems Strategy Workshop November 3, 2011. Project Results. Source: Standish Group Chaos Manifesto. Risk Potential. Average Project Cost Overrun 27% But one in six exceeded 200%. “ The number one reason projects fail

Download Presentation

The Case for Agile Development

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


The case for agile development

The Case for Agile Development

Creative Disruption:

A Core Systems Strategy Workshop

November 3, 2011


Project results

Project Results

Source: Standish Group Chaos Manifesto


Risk potential

Risk Potential

Average Project Cost Overrun

27%

But one in six exceeded

200%


The case for agile development 1369618

“The number one reason projects fail

is due to absent or inadequate

executive sponsorship.”


Factors of success

Factors of Success

  • User Involvement

  • Executive Support

  • Clear Business Objectives

  • Emotional Maturity

  • Optimizing Scope

  • Agile Process

  • Project Management Expertise

  • Skilled Resources

  • Execution

  • Tools and Infrastructure

Source: Standish Group Chaos Manifesto


Agile process

Agile Process

Game-changing Benefits

Nerve-wracking Risks

CHANGE


Key principles

Key Principles

  • Collaboration

  • Embracing Change

  • High Performance Teams

  • Working Software Often


Key principles1

Key Principles

  • Set of Tools

  • Dodging Documentation

  • Design Methodology


Scrum an agile approach

Scrum - An Agile Approach


Scaling scrum

Scaling Scrum

  • Feature Teams

  • Continuous Integration

  • User Centered Design

  • Scrum of Scrums

  • Program Backlog

  • And More


Pitfalls

Pitfalls

  • Not Empowering the Team

  • Different World View of Cross-Functional Teams

  • Discomfort with Identifying Impediments

  • Limited Business Involvement

  • Defining Done

  • “Agilefall”


Case study

Case Study

Generally successful but still not a silver bullet.


Inception sprint zero

Inception – Sprint Zero

  • Define the program backlog

  • Organize by major features

  • Prioritize features

  • Plan work by team

  • Plan cross-team interactions

  • Visual layout of the program

  • Define a conceptual vision to start

  • Evolve and change as conditions dictate


The case for agile development 1369618

Sprint Plan Overview


The case for agile development 1369618

Features by Team


The case for agile development 1369618

Testing Phase

Multiple test sprints

End to end testing

Regression Testing

User Acceptance Testing


The case for agile development 1369618

Supporting Factors

  • Business Case Objectives

  • Governance Model

  • Dedicated Team

  • Collocated Team

  • handful of parameters guiding independent decision making

  • rules of the road defining decision making expectations

  • develop confidence in teammates and expectations to deliver

  • timely responsive


The case for agile development 1369618

Business case became a tool throughout the program.


The case for agile development 1369618

The right people and the right partners given the commitment they needed to succeed!

  • Internal participants 100% committed for the duration of the program

  • Team collocated at off-site office space

  • Multi-disciplined teams consisting of internal business SMEs, internal IT analysts, vendor experts and system integrator analysts


The case for agile development 1369618

Lessons Learned

  • Educate

    • Product owner

    • ScrumMaster

    • Team members

    • Others interacting with the agile team

  • Communicate, communicate, communicate

    • Delivery

    • Daily scrums

    • Sprint reviews

  • Incrementally improve

    • Sprint, assess, sprint again

    • Improve the process as well as delivery

  • Empower the team


The case for agile development 1369618

Lasting Effects

  • Scrum is now the default for all strategic projects

  • Application maintenance releases follow an agile approach

  • Adopted for numerous non-project efforts – scrum meeting format, etc.

  • IT planning follows a conceptual plan with quarterly reviews for the maintenance of projects in the “product backlog”

More dynamic, more transparent, shorter timeframes and focused on functional deliverables.


The case for agile development 1369618

Final Note:

Invest in lots of

colored Post-It Notes


The case for agile development 1369618

Questions?


The case for agile development 1369618

  • Michael Foerst

    • VP of IS / CIO - Missouri Employers Mutual

    • Contact Information

      • E-Mail:[email protected]

      • LinkedIn:www.linkedin.com/in/michaelfoerst

      • Twitter:twitter.com/michaelfoerst


  • Login