Agile methodology adoption is galloping in adoption in the industry. It is almost a fad in many ways with most software practitioners wanting to have a personal certification. However, the question remains - Is agile methodology resulting in better agility? Yes? No? Is there an Achilles’ heel? We shall ponder in this talk. This is based on my observations with multiple of our customer where agile methodology has not brought in agility and how we are moving towards a transformational journey

If we look at industry at large, we will not be surprised to see that something that works well to one doesn’t work the same.   A careful analysis in most cases would show that there was something fundamental that was an essential ingredient is getting missed. Way back in early 1900s, Ford had a small lab where all new things were tried and brought into the shop floor. This lab was a place which very few had access to. However, this generated enough to drive their line manufacturing concept and new models. Henry Ford himself spent a significant time thinking how they can make a difference to customers. Few years from then, R&D team became a norm that every organization had and industry started measuring innovativeness of an organization based on R&D spend. However, many R&D functions became hub of inventions that would never be used and lost the sting that was before. Today traditional R&D functions are being shut in many places and R&D cost is being scrutinized heavily. Why? Many became too distant from their customers or they took the eyes of competition.

Can a similar Achilles heel exist for agile methodology? Sadly, the answer seems yes.

The talk will flow as below

  1. What is so unique in agile that waterfall or RUP did not have? Let us try and answer this? Did TDD originate with agile? Did user centric requirements originate with agile? Did acceptance criteria originate with agile? Answer is No for all of these. If so, what is the new thing in agile that makes the difference?   Talk with bring out the fundamental uniqueness of agile and why it is an imperative from business, developer
  2. Some samples of classic non-agile setup but still considered agile
    1. Reflection from an agile setup that has been in force for last 5+ years
    2. Reflection from an agile setup of a new transformational product is being developed
    3. Reflection from a production implementation setup that touted themselves of fast delivery to customers
  3. Where does agility start & how should we approach agility in the industry?
 
1 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. What is so unique in agile that waterfall or RUP did not have? Let us try and answer this? Did TDD originate with agile? Did user centric requirements originate with agile? Did acceptance criteria originate with agile? Answer is No for all of these. If so, what is the new thing in agile that makes the difference?   Talk with bring out the fundamental uniqueness of agile and why it is an imperative from business, developer
  2. Some samples of classic non-agile setup but still considered agile
    1. Reflection from an agile setup that has been in force for last 5+ years
    2. Reflection from an agile setup of a new transformational product is being developed
    3. Reflection from a production implementation setup that touted themselves of fast delivery to customers
  3. How should we approach agility in the industry?

Learning Outcome

Importance of the most fundamental element of agile - feedback from people who matter using a working product

Patterns of setups which miss the fundamental element of agile

A format to quickly assess agility and value delivery in any setup

Where to start the transformation journey

 

Target Audience

CIO, Delivery leadership, Agile coaches, scrum masters

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Evan Leybourn
    By Evan Leybourn  ~  1 year ago
    reply Reply

    Thanks for submitting the proposal. 

    Can you please update your proposal with the following...

    • Slides - Preferably an outline of this talk, but any similar presentation will do.
    • Videos Links - To some of your past presentations on this topic or any other. The video could be from other conferences, user group meetups or internal to your company. In case you don't have any; I suggest you shoot a short video presenting to the audience.
    • Blogs/Articles: Links to blogs or articles on this topic.

    The above will help you complete the proposals and also help the review panel. We can take it forward from there.

     

    Thanks, 
    Evan