Agıle falls, so how to fıx ıt?

19 Eki 2017
14:00 - 14:40
Hall 2

Agıle falls, so how to fıx ıt?

Agile become one of the most popular buzzwords. It’s magical, imaginary because it satisfies all expectations and resolves any problem in your company. However Agile says ‘it’s not a silver bullet’ and it emphasizes delivering value to customers via focusing quality. Then, organisations will be a leader in their domain and/or hold their leadership.
The number of people who worked in agile, implemented agile techniques, delivered agile projects, has been increasing, and also exponentially increased recently because management asks teams to be agile. Not just saying, management supports teams to be agile. Nonetheless they do not think that the way of management should be adaptive too. Agile requires the engagement of every department in the organisation, not just information technologies. Agile requires practices, real-cases to implement, actual lessons to learn. If foundations are not in place, the gap between the actuals and expectations gets bigger and the biggest fans of Agile start to say ‘it’s not working!’, ‘Am I Agile now?’, ‘I invested pots of money, I should be agile, did not I?’ Unfortunately, the number of failure cases is too many, hard to ignore. ..

Thoughworks have been engaged several customers who had fed up, still trying or new starters, and the perception of Agile’s success is questionable because of wrong expectations on day one. Agile is not a way of implementation by the book, it reaches the best form within the organisation, culture, people, process, business, technology and willingness to change. We do try to find the best fit while working with clients in their office, in their development teams to optimise value stream, use technology and techniques according to their uniqueness.

This talk includes actual case studies from ThoughtWorks clients. There will be failures, lessons learnt, challenges we took, pain points in the journey, actual figures that define success and a checklist for foundations of agile software development. The talk will include engineering practices used, technologies chosen, roadmap for lean transformation from different projects/programs all over the world. And finally, guidelines to understand the current state of being agile (via Agile Fluency Model), the way of kick-start change, pinpoints to attack if you have similar issues in your organisation and a future backwards for an Agile transformation journey.

Agenda:

  1. What is not Agile?
  2. Why is Agile important? Tell me the best of doing this?
  3. When and Why Agile falls apart?
  4. How to fix if things go wrong?
  5. Conclusion – Be Agile, Do not Pretend!