Vyom BharadwajSenior Manager| Vodafone GroupPune, Maharashtra, India
1-Have you ever failed while doing or being agile? 2-What are/were your experiences/lessons learned/change in perceptions etc.? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
There is a similar discussion. Here what I commented:
No, thanks God or any other force you believe governs the Universe, because I always worked on initiatives to implement Agile as the leader or head of the initiative. Do not fail is simple, here the steps: 1-understand what Agile really is: You can apply Agile with any type of life cycle, for any type of product, at enterprise wide first which is the place from where Agile was born. 2-explain to the people that are hiring you to implement Agile that Agile is nothing they beleive it is. Is not low cost, is not deliver faster, is not no documentation, is not makeing changes when they want, etc. This is the first thing I did from 1995 up to date. If after the presentation they decide not work with me no problem. If I do not do that then I am "dead on arrive (DOA)". 3-understand that everything you introduce into an organization will impact the organization as a whole because it is impossible to be successful without using systemic thinking. Mainly if you are trying to use Agile. Then, you must make an impact analysis which is an activity that belongs to business analysis (just to add information) and it is named "needs assessment" (PMI) or "strategy analysis" (IIBA). Saving Changes...
RAJESH K LProject Manager, PMP| Bharat Electronics, Bengaluru, IndiaBengaluru, Karnataka, India
Agree with Sergio Saving Changes...
Farouq ZaababResearcher, Coach, Trainer, Consultant| FreelancerSohar, Oman
Can you clarify what you mean by failed? If you mean that an adaptive lifecycle was not appropriate for the project then "no" but if you mean either a team that was doing agile vs. Being agile and/or a lack of organizational support for agile, then frequently!
Agile is not a silver (or bronze or wooden) bullet and fundamental delivery dysfunctions and blockers won't get magically cured when you wave the agile wand.
Kiron Saving Changes...
Justus NScrum Master| BCBSTXArlington, Tx, United States
The only time we have failed at an agile project is when we weren't doing agile. Most organizations do their own version of "agile"
Doing wagile (waterfall and agile) doing scrum-but (doing scrum but not really following best practices as prescribed in Scrum) and the list goes on...... Saving Changes...
Joseph Prem AnandProgram Manager| Deutsche Bank AGCary, Nc, United States
Not failure but sustaining agile 'best' practices has been a challenge. Saving Changes...
I have observed Agile failing in at least three situations:
- Healthcare.gov by CGI, see https://www.washingtonpost.com/news/wonk/w...m=.b821cc9b7984 - Keeping mission critical systems running: in order to keep IE-checks arriving on time in the mailbox of unemployed people, an organization like ESDC (Employment Social Development Canada) cannot afford itself to plan their software enhancement projects only for the next 30-days out. They need to plan the entire enhancement out very carefully. Agile does not fit situations like that.
- Financial services firm: the migration Business Analysts wanted to do their work in an Agile fashion and had established an Agile that they limited to 8 people that were used to work together and liked to work together. Their project was massive and the migration was so much work that their initial draft schedule was 2 years long and appeared as the longest path in the program schedule. Similar migrations had previously been done in 8 months and it was clear that senior management would never allow this cozy agile team to drive the program duration out by more than a year. Saving Changes...
