Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

When size doesn't matter: A case study on adopting agile in large enterprises by Damir Bajrektarovic and Haris Krkalić

22 views

Published on

Although agile can yield significant advantages, the journey is not always easy. Agile methods have become an appealing alternative for companies striving to improve their performance, but the methods were originally designed for small and individual teams. This creates unique challenges when introducing agile at scale, when development teams must synchronize their activities and there might be a need to interface with other organizational units. Agile principles indeed can be applied to large, even very large, groups of people, allowing them to be more connected to their work and its impact, despite being part of a huge system. As Agile scales up, it also scales 'out' across an organization's value chain -- to departments outside of product development -- to deliver a valuable product or service to the market. This is the story of how we managed to challenge teams to synchronize their activities, to improve performance. The story of non-agile becoming agile. Story of how we leveraged our customers' loyalty, and how we tailored agile strategies to our organisation's needs.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

When size doesn't matter: A case study on adopting agile in large enterprises by Damir Bajrektarovic and Haris Krkalić

  1. 1. When size doesn't matter A case study on adopting agile in large enterprises HOTEL EUROPE, October 21st
  2. 2. ZIRA Leading vendor of innovative BSS solutions for customer, revenue and risk management • 50+ telecommunication operators • 22 countries • 150.000 up to 80 million subscribers • Over 2.5 billion transactions per day 100+ employees and Award-winning solutions Distinctive leadership within the entire Business Support System framework
  3. 3. Why Change? Why go Agile? Predictable Costs and Schedule While reviewing the Sprints the cost is predictable and limited to the amount of work that can be performed by the team. It improves decision making and the priority of features that is need for additional iterations. Transparency and Predictable Delivery Agile provides a unique opportunity for clients to be involved during the project review sessions for new feature which is attractive. Better Flexibility Quickly adapt to customer‘s changing needs. Clients being able to change the scope of the project, giving you the competitive edge in the evergrowing industry. The product is continuously morphing to meet the changing needs of users. Faster Deployment Faster delivery to end-users, as continuous improvements go on simultaneously.
  4. 4. Does Size Really Matter? • Team size DOES affect performance of Agile Teams • Scaling Agile in larger companies is exponentially more difficult • >9 and any group splits into teams • Trouble of teams being geographically distributed, not having face to face interaction • The more overlap you have with different teams the harder it gets to follow a strict AGILE approach.
  5. 5. Creativity Companies from industrial revolution Less creative freedom
  6. 6. The Old Fashioned Way „I think we should actually consider....” „Stop playing, let me tell you how it was in my day...”
  7. 7. Tools & Testing Testing is just an afterthought that happens after the coding is done Outdated tools and technologies
  8. 8. Difficulties with Agile Lack of Communication Lack of Trust Lack of Planning
  9. 9. Waterfall vs Agile Large, lumbering companies that are traditionally more conservative mindset than start-ups and have a lot more money on the line cannot possibly afford to mess up their transition to agile.
  10. 10. Customer problems „...why cannot I get the feature now??” Ignoring the customer
  11. 11. Usual Agile Training
  12. 12. How did we manage? Damir Bajrektarovic HOTEL EUROPE, October 21st
  13. 13. Thinking of Agile as a TOOL • Install it everywhere and it will solve everything. • If the ecosystem is unhealthy, it will continue to be unhealthy at any scale.
  14. 14. Our Personal Experience Take a product-oriented, not project-oriented, approach to building ADT Teams Start with „Light” Designs
  15. 15. Our Personal Experience Improve interactions between Business and IT
  16. 16. Our Personal Experience Redefine managerial roles and responsibilities Key Points: 1. Comunicate 2. Comunicate 3. Comunicate!!!
  17. 17. Our Personal Experience All in one place is a must
  18. 18. Scale by People not Project Team Size Does Matter Two Pizza Team Military Approach
  19. 19. Scale by People not Project Team Size Does Matter
  20. 20. How to Manage Testing iteratively over not fully completed features Adequate training for QA personnel Self Organising Team
  21. 21. State Of Mind Dont measure new menthodologies by old standards "We know that agile is first about ‘how you think’ and then about 'what you do,'" Agile Alliance
  22. 22. Agile in Other Placese
  23. 23. Room For Growth Agile Still Has Room For Growth
  24. 24. Room For Growth Enterprise Agility Is Increasing Organizations Can Achieve More
  25. 25. THANK YOU!

×