Hans Samios' Personal Lean-Agile Knowledge Base

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== What is the Elevator Pitch for Agile and Scrum? ======

Geoffrey Moore in [[https://www.amazon.com/s/ref=nb_sb_ss_c_0_13?url=search-alias%3Ddigital-text&field-keywords=crossing+the+chasm&sprefix=crossing+the+%2Caps%2C139|"Crossing the Chasm"]] talks about an "elevator pitch" for what you are selling. The idea is that you get in the elevator with the CEO of the company and you have the length of that trip in the elevator to explain to him / her what you are doing and why it is important. A classic elevator pitch has the following components:

  * Your target audience
  * The market alternative
  * The new category that your idea/product fills
  * What problem solving capability this new thing provides
  * An alternative that is in the target audiences mind, and
  * The key product features

I won't stick strictly to this format but I will try to capture most of these ideas. There are a number of these pitches out there. I think there are differences based on the kind of people you are working with so here is a version that reflects my contacts.

====== Elevator Pitch ======

The simplest version of "Why Agile" comes from [[http://jimhighsmith.com|Jim Highsmith]] who says “Scrum / Agile is a risk mitigation technique when our assumptions about predictability do not hold.” He further elaborates "Scrum / Agile are used to provide customers with what they need at the end of the project, not what they thought they wanted at the beginning of the project."

If you are more interested in Scrum then [[http://www.agileinfusion.com|Bob Schatz of Agile Infusion]] says that "Scrum is a pattern of practice that helps product developers break complex problems into smaller pieces and then work collaboratively with users to create better solutions."

The way I look at it "An agile approach to implementing software increases our effectiveness - our ability to deliver value, reduce risk, increase predictability and improve quality. The agile approach is a recognition that traditional software "upfront planning" approaches are not able to deal with the complex situation arising out of the need to evolve requirements, learn how to build the solution and cheaply address the changes that result from this situation."

And if your elevator ride goes up many floors or you have a slow elevator, you might want to consider a slightly longer explanation ...



{{page>why_should_we_consider_moving_to_agile&nodate&notags&nouser}}


{{page>what_types_of_benefits_do_people_see_when_they_go_agile&nodate&notags&nouser}}



{{page>what_types_of_problems_do_people_see_when_they_go_agile&nodate&notags&nouser}}


====== Thinking ======

Did a bit of research on this and here are some ideas that I came across that I liked:

[[https://www.scrum.org|Ken Schwaber, co-inventor of Scrum]]: "We'll help you fail in half the time!" (note: have to love this one, even if it is a little cryptic).

[[http://blog.berczuk.com/2009/06/pitching-agile-and-elevator-test.html|Steve Berczuk]]: "For organizations who are dissatisfied with the overhead and lack of flexibility of conventional software development methods, Agile Software Development is a software development process. Unlike traditional chaotic or document-heavy approaches, Agile Software Development is a lightweight, yet highly disciplined approach that delivers end to end value in frequent iterations, where the stakeholders can re-evaluate priorities based on the state of the application and current market needs at the end of an iteration."

[[https://www.quora.com/What-is-your-best-elevator-pitch-for-Scrum?share=1|Subashish Bose]]: "Scrum is a way to ship products frequently. The most valuable part goes first, so you get the best returns. Quality is never compromised, so you get the best stuff in best quality. That way you get rapid ROI, as well as you can even change your plans based on customer behavior. Change is very easy. It's based on empirical methods and uses feedback loops and continuous learning. So you get to know the most reliable forecasts. Team and people are the focus, so they end up being happy and proud. We moved from waterfall to Scrum for a telecom solutions company and started shipping every four months instead of previous 2 years. We prioritized and shipped the most valuable part first to get the best ROI. It's highly empirical with feedback and learning, so we were pretty sure of where we are going. Guys loved that."

[[http://bradapp.blogspot.com/2009/06/value-proposition-for-agility.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+bradapp+%28Brad+Appleton%27s+ACME+Blog%29|Brad Appleton]]: "Agility is all about harnessing the power of collaborative people and frequent delivery to:
learn & adapt to change, minimize risk & cycle-time, and maximize returns & customer-value in a volatile global marketplace."

{{tag>Consultant Tools CultureChange Organization ElevatorPitch FAQ PresentationIdea}}