Robotic Warehouses, Alien Domain, Offshore developers, Visionary customer : Saved by agile

Here is a case study of how agile outsourcing can be practically applied even when the business domain is very complex and alien to offshore teams.
The example is a project in which Exilesoft provided for a leading Norwegian producer of Robotic warehousing solutions. The project involved transforming their legacy application, produced using multiple suppliers and methods, into a newly cast application solution. This project also had its own share of typical challenges.

• Lacked definitive and reliable documentation,
• Domain knowledge was limited to a few very busy individuals,
• Development and redeployment could not interrupt attention to current customers,
• Complexity was high and design was fragmented, and
• Focus heavily invested on current product and customer support

These limitations along with the lack of understanding of agile methods strongly suggested the use of a method adaptive in nature, and not heavily vested in large inflexible legacy elements.
We commenced the engagement with two pivotal elements; client awareness (agile orientation) and a roadmap of committed involvement. To lay credibility this had to be backed up with proven result delivery in the very early stages. It allowed for flexible adaption, and the creation of an atmosphere that fostered client interest.

During this session, we will take the audience through a small video clipping of such a warehouse. We will elaborate how the customer and offshore developers worked together using agile in a highly integrated team collaboration model to achieve success within a very short time frame.

The session will cover the following key areas:

How such projects can be initiated

- What type of team model and contract type we used

- How we did the agile transformation with the customer

- How the roles were assigned between offshore and onshore team members

- To improve remote collaboration the tools and techniques we used

- Techniues learned to get teams up to speed with the new domain

- As we go along, the process changes we identified and implemented to make things work better.

- Agile engineering practices and team dynamics that helps in such situations

 
 

Outline/structure of the Session

- Introduction to the business case.
The video will be played here to explain the
complication we need to tackel in such warehouse applciation : 4 Mins ( Video is for around 40 Secs)

- Walkthrough the challenges : 5 Mins
- Unknown domain with a legacy system which should run parallely
- No documentation
- Limited noof people from customer who has good understanding on the domain
- No access to product owner during planning meetings
- Releases planned for multiple existing customers at the same time, Time to market fctor
- Customer has no agile experience

- Solutions we came up with will be discussed : 10 mins

- Wrap up the session : 1 mins

Learning Outcome

- A practical approach to apply agile principles in complex buisness scenarios

- Apply agile in offshore project context

- How to model offshore - onshore team collaboration

Target Audience

Agile coach, Project managers, Developers, Product owner, Business users

Requirements

Seating arrangement - Theater style or discussion 

 

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Pramod Sadalage
    By Pramod Sadalage  ~  3 years ago
    reply Reply

    Vinodhini,

    I would encourage you to distill your learnings and focus on key outcomes so that you can present a case study in 20 min.

     

    Thanks

    • Prashant Sagar
      By Prashant Sagar  ~  3 years ago
      reply Reply

      Hey Vinodhini,

       I find your presentation/talk very similar to http://confengine.com/proposal/173/the-different-engagement-models-processes-challenges-and-solutions-for-a-distributed-scrum-team-in-an-outsourced-product-development-opd ?

      Can you please differentiate how is your presentation different/better value proposition than above?

      • Vinodhini
        By Vinodhini  ~  3 years ago
        reply Reply

        Hi Prashant,

         

        I read the proposal which you have pointed here. What I read is same as what you read so I don’t have extra information to compare that proposal with mine. Further its not fair for me to do that without knowing more insights about her talk, I searched that in youtube to see whether there are any recorded presentations of her talk, but I couldn’t find anything related to it.

         

        All what I can do is to explain bit more about why I selected this case study to present at AgileIndia.

        The main reason for me to propose this case study was that, this is a very complex domain to understand by a team in a remote location, who are very new to such robotic warehouses. So how we made such project successful using agile and how we got the teams up to speed with such complex domain and started to deliver software within its very first sprint itself. Further, as offshore developers we do not always get a chance to work with such systems outside usual transaction based applications. So I think this is a very interesting case to share.

         

         

    • Pavel Dabrytski
      By Pavel Dabrytski  ~  3 years ago
      reply Reply

      Hi Vinodhini,

      In order for us to understand your session better and see if it feets our program, we would like you to add some more details into 'Process' section. Also move some of process specific information into from Description into Process (i.e. watching video wording fits more into process).

      We would like to know things like:

      1. duration of each segment of your talk, duration of the video

      2. You mention 'walkthrouh challenges and solutions'. Could you please ellaborate more on which challenges you faced and what solutions you came up with? Are those the same as key areas described in description? Will you cover all of these key areas? How much time do you plan to spend on each of the areas?

      3. What type of discussion would you have with the audience. Will it be Q & A. How much time do you plan for this section? Otherwise what topics/ideas will you discuss with the audience?

      4. Do you plan to have any interactions with the audience? if yes, can you describe these interactions?

      5. Your requirements section doesn't mention anything regarding watching videos. I would assume you need equipment for it. Also, do you need flipcharts for discussions, etc.

       

      Biggest concern for me that watching video doesn't take up most of the time of the session.

      tip: it is better to edit the proposal itself instead of putting info into comment replies. This way we can save reviwers time.

       

      Thank you very much for submitting you proposal to Agile India!

      • Sudipta Lahiri
        By Sudipta Lahiri  ~  3 years ago
        reply Reply

        Hi Vinodhini,

         

        Can you pls give some high level information on what are the suggestions/recommendation that you will be detailing during the talk? For example, would you be focussing people to people interactions OR some process level tips/what worked and what didn't OR some cultural aspects that were addressed?

         

        Without that, it is hard for us to comment on your submission.

         

        Regards

        Sudipta.

        • Vinodhini
          By Vinodhini  ~  3 years ago
          reply Reply

          We will mainly address how Agile methods and models can be used in order to get an offshore team up to speed within a very short time to deliver software in a totally new business context.  

          - How such projects can be initiated

          - What type of team model and contract type we used

          - How the roles were assigned between offshore and onshore team members

          - To improve remote collaboration the tools and techniques we used

          - Techniues learned to get teams up to speed with the new domain

          - As we go along, the process changes we identified and implemented to make things work better.

          - Agile engineering practices which helped in such situations

          - Ofcourse we will touch in to team dynamics as well.

          My co-presenter will cover the customer engagement and agile tranformation part as she was involved in that area while I cover the rest of the presentation. We both will be avialable for Questions and Answers.

          Greatly appreciate your help!

          As time permits, I will keep on improving the proposal


      • Liked Sreerupa Sen
        keyboard_arrow_down

        Changing our Rhythm: Our Ongoing Journey towards Continuous Delivery

        Sreerupa Sen
        Sreerupa Sen
        schedule 3 years ago
        Sold Out!
        20 mins
        Experience Report
        Beginner

        Annual software release cycles cramping the agility of the team? Too many hot fixes reducing the efficiency of your organization? Customers waiting impatientlyfor  the next cool features hot off the press? These are some of the painful and common problems faced by development teams worldwide. In today's world, most things get outdated or out-of-fashion very fast - and software is no different. Users cannot afford to wait for the next cool set of features for a year. They want a steady stream of cool new features that they can adopt and use immediately.

        My team follows a development model that we like to call Open Commercial Development - where we're always connected to our stakeholders, our plans are out in the open, and we're always gathering feedback and reprioritizing. We used to have yearly releases of our product - a sort of big bang release with a host of new featres. Based on our stakeholder interactions, however, we figured that our software delivery wasn't agile enough for our customers. Users wanted new features incrementally throughout the year. They especially didn't want to wait a year for a feature that they'd requested that was critical for their business.

        So began our journey to Continuous Delivery - an interesting one for sure. It's not easy to deliver new features, manage technical debt, collaborate with users and incorporate their feedback into the new features - once every quarter. To do it consistently, with quality and on time, you need to have a framework in place - a combination of planning, process, automation and team organization - that lets teams focus on the right things to get to DONE DONE for their new features, and at the same time manage their quality and tecnical debt. Over the past year, we like to think that we've put that framework in place, and that is what I'd like to talk about in this session.

      • Liked Giovanni Asproni
        keyboard_arrow_down

        Methodology Patterns: a Different Approach to Create a Methodology for Your Project

        Giovanni Asproni
        Giovanni Asproni
        schedule 3 years ago
        Sold Out!
        90 mins
        Tutorial
        Advanced

        In the software world we have been looking for “The Methodology” to solve our software development sorrows for quite a while. We started with Waterfall, then Spiral, Evo, RUP and, more recently with XP, Scrum, Kanban, DAD, SAFe (there are many others, but, their impact, so far, has been limited).

        In this tutorial, I'll show why this search for the holy grail is bound to fail--each methodology has strenghts and weaknesses that make it suitable only in some contexts--and I'll describe a different approach based on patterns and pattern languages, that teams can use to create their own methodologies to suit their specific needs, which, in my experience, has a higher chance of success. 

        The approach is based on the observation that all the practices used in all modern methodologies--e.g., user stories, use cases, team self organization, TDD, unit testing, acceptance testing, continuous integration, iterative and incremental development, etc.--come from the same set. Different methodologies just mix and match them differently. All those practices can (and many have already been) described as patterns whose relationships with each other form a set of pattern languages.

      • Liked Vinay Krishna
        keyboard_arrow_down

        Effective 9 Practices to minimize technical debt

        Vinay Krishna
        Vinay Krishna
        schedule 3 years ago
        Sold Out!
        45 mins
        Talk
        Beginner

        Often we find it difficult to incorporate any changes in a software project during later phases of its development, or during post-delivery maintenance. Primary reason for this is inflexibility in design and code which makes it difficult for changes to be incorporated. This inflexibility substantially increases the cost of making changes and this metaphor has been termed as Technical Debt.
        While Technical Debt cannot be eliminated completely, its burden needs to be reduced. Many agile practitioners have suggested some practices to avoid or eliminate Technical Debt.
        In this session I shall discuss about a method to get relief from Technical Debt and talks about nine proven practices that a developer can follow to minimize Technical Debt. These practices help to:

        • Change the coder's mindset so that they should use technical practices i.e. various refactoring techniques to reduce technical debt in code and design
        • Developers to plan and manage the time to pay down the debt i.e. determine your living budget
        • Take minimal technical credit in design and code

        These practices have been used and found to be effective when implemented in projects which will be used as a case study.

      • Liked Naresh Jain
        keyboard_arrow_down

        Scaling XP Practices inside your organization using Train-the-Trainer Model

        Naresh Jain
        Naresh Jain
        schedule 3 years ago
        Sold Out!
        90 mins
        Workshop
        Advanced

        How do you effectively scale skill-based, quality training across your organization?

        Over the years, I've experimented with different ideas/models to scaling skill-based training across an organization. In the last 4 years, I've pretty much settled down on the following model. Its very useful when mentoring teams on skills like Test-Drive-Development (TDD), Behavior-Driven Development (BDD), Product Discovery, Writing User Stories, Evolutionary Design, Design Patterns, Problem Solving, etc. I've successfully implemented this model at some very prominent fortune 500 enterprises.

        The goal of this workshop is to explore what other successful models organized have used to scale skill-based training in their organization.

      • Liked Shashank Teotia
        keyboard_arrow_down

        TDD and CI - closing the agile loop over system programming using Go (golang)

        Shashank Teotia
        Shashank Teotia
        schedule 3 years ago
        Sold Out!
        90 mins
        Demonstration
        Advanced

        With Google Go becoming more popular and accepted, it becomes important for us to know the right framework to apply for adopting a TDD and CI approach to writing application written in Go. Especially, when we are talking in the context of writing software which interfaces with system drivers and services.


        We will also look at how we can create a build pipeline to run automated tests and continuously integrate into a packaged software.


        Other programming environments, have achieved a good level of maturity with tools for writing tests. I will present how we adapted our learnings in such environments into development in golang.

      • Liked Karthik Vijayakumar
        keyboard_arrow_down

        Agile Retrospectives based on Continuous Process Improvement

        Karthik Vijayakumar
        Karthik Vijayakumar
        schedule 3 years ago
        Sold Out!
        45 mins
        Talk
        Beginner

        Agile Retrospectives are talked about and practiced my many teams, at varying levels across the globe. But more often than not, while these retrospectives are carried out with great fervor, teams often struggle on following up. This struggle is greater when teams begin to follow Agile.

        Effective Retrospectives create learning teams and helps aid continuous process improvement.

        In this talk, we'll walk you though a technique that applies continuous process improvement practices to help you many your retrospectives effective, easy to follow-up and measure your progress over the course of time.

        In the 45 minutes of this interactive Talk, you will learn a very useful technique to interacting with teams and effectively communicating with "management" and other key internal stakeholders on the roadmap to continuous improvement.

      • Aruni Siriwardene
        Aruni Siriwardene
        schedule 3 years ago
        Sold Out!
        45 mins
        Talk
        Intermediate

        A traditional software development project entails specifics around elements in or out of scope, tied up to deliverables, all ensconced within specified estimates and timelines, subjected to legal clauses for everything from acceptance to indemnities. For Agile contracts, the boundaries of legal intervention must stand; merely due to the marriage of parties when a project is executed; the definitions of boundaries must be established be it scope, budget or timeline and all standard deliverables from a traditional project stands; yet, the execution is as diverse as chalk and cheese.

        What are the key criteria to be aware of when we define Agile contracts; as in typical agile projects, should the client be involved in mutually drafting the contract? How much legal intervention can we allow? What happens to deliverables and expenses when delays occur and scope boundaries are reduced? Can blame be apportioned to an extent that each party will have to indemnify themselves?

        An Agile contract needs to reflect the nature of the engagement; no template contract with standard clauses can be coaxed upon a true agile project. In line with the Agile principles and values and targeted to the agile manifesto; Agile contracts should be just that – Agile!

      • Naresh Jain
        Naresh Jain
        schedule 3 years ago
        Sold Out!
        45 mins
        Demonstration
        Intermediate

        "Release Early, Release Often" is a proven mantra and many companies have taken this one step further by releasing products to real users with every commit a.k.a Continuous Deployment (CD).

        Over the years, I've built many web/infrastructure products, where we've effectively practiced CD. However at Edventure Labs, when we started building iPad games, we realized there was no easy was to practice CD, esp. given the fact that Apple review takes a few days.

        Our main question was: As mobile app developers, how should we architect/design our apps for CD?

        We were a young startup, learning new behavior about our users (kids aged 5-8) everyday. We could not afford any delay in releasing latest, greatest features to our users. To solve this problem, I believe we've built an innovative solution to enable any mobile app developer to achieve CD.

        If you are building real products, which have platform/3rd-party dependencies and you want to practice CD, this session is for you.

      • Aruna Rajapaksha
        Aruna Rajapaksha
        schedule 3 years ago
        Sold Out!
        20 mins
        Experience Report
        Intermediate

        Pair testing with onshore team members enrich the quality outcome and naturally transfer the domain knowledge to offshore teams effortlessly. This practice helps to sustain clients by providing superior quality outcome for their investments.

        Best practices of distributed testing, modern tools and technologies for communication, mitigating cultural gaps, language barriers and time zone differences are subjects itself to discuss in detail.

      • Liked Pramod Sadalage
        keyboard_arrow_down

        Ten Patterns of Database Refactoring

        Pramod Sadalage
        Pramod Sadalage
        schedule 3 years ago
        Sold Out!
        45 mins
        Talk
        Beginner

        Over the life of an application as requirements change, application usage patterns alter, load and performance changes the need to change database and database architecture is inevitable. There are patterns of these changes such as

        1. 1. Encapsulate Table with View
        2. 2. Migrate method from database
        3. 3. Replace method with views
        4. 4. Introduce Read only table
        5. 5. Split table
        6. 6. Make column non-nullable
        7. 7. Drop column
        8. 8. Add foreign key constaint
        9. 9. Merge columns
        10. 10. Replace columns

        In this talk we will discuss the above database refactoring patterns and different implementation techniques to enable blue, green deployments, allow for legacy applications to work with fast changing database and enable the teams to effectively refactor the database to fulfill the changing needs of the organization.

      • Liked Johannes Brodwall
        keyboard_arrow_down

        Kicking off agile remote teams

        Johannes Brodwall
        Johannes Brodwall
        schedule 3 years ago
        Sold Out!
        90 mins
        Workshop
        Beginner

        So your project is just getting started. Or maybe you're just about to embark on a new release. Or new members just joined the team. What now?

        In either situation, your project will have a lot of energy and attention right now. But at the same time, there's probably a lot of uncertainty about what to do first. Many projects waste this valuable time without a clear plan or purpose. In Exilesoft, we have refined activities to deal with these problems, even with the additional constraint that the team may be distributed geographically.

        In this workshop, we share a typical plan of what activities to do every day in the first weeks together with a set of activities which yeld tangible results in terms of team building, vision, architecture and a coherent working system in a minimum of time. Participants will get a chance to practice the skills as well with several interactive exercises.

      • Liked Johannes Brodwall
        keyboard_arrow_down

        Practice agile programming with coding dojo

        Johannes Brodwall
        Johannes Brodwall
        Buddhima w.wickramasinghe.
        Buddhima w.wickramasinghe.
        schedule 3 years ago
        Sold Out!
        90 mins
        Workshop
        Beginner

        A Coding Dojo is a fun and social way to become a better programmer. Johannes is an experienced coding coach who will guide you through a few hours of programming that will transform your understand your craft and yourself as a programmer. In the workshop you get to try out pair programming, test-driven development and continuous refactoring for yourself and you get lots of recommendations on how to improve your coding and testing. You will need to bring your own computer with a development environment of your choice. Recommended for Java, Ruby, JavaScript and C# developers.

        This is what previous participants say about the workshop:

        • What did you learn? New tools, pair programming and fun exercises; Ide tricks, programming language basics, testing tools, using tests as a reasoning tool; you can comfortably pair with strangers.
        • What surprised you? Small steps work better than planning; It's easy to get started when you pair program; Pair programming is nice
        • What do you plan to do next? Using TDD every day; Listen to partner more carefully - he may already have solved the problem.
      • Liked Johannes Brodwall
        keyboard_arrow_down

        Bare-Knuckle Web Development

        Johannes Brodwall
        Johannes Brodwall
        schedule 3 years ago
        Sold Out!
        45 mins
        Talk
        Intermediate

        Can you go faster with less weight?

        We have all learned the benefit of reusing application servers like JBoss, ORMs like NHibernate or dependency injection frameworks like Spring that "solve all the plumbing code for you", but how real are these benefits really? Most developers struggle using techniques like test-driven development and refactoring effectively in their day to day project. Many developers spend a majority of their day finding out which magic incantations will make your framework solve your requirement.

        Yes, frameworks probably will reduce the size of your code base. But will their reduce the time it takes to develop that code base? And perhaps even more pressingly: How certain are your estimates when you know that a the majority of your work is to find out exactly which few lines of code you need to change by debugging, reading documentation and searching for answers on stack overflow?

        When I was first learning math, my dad told me that I didn't to use a calculator before I could do the math without it. In the same tradition, this talk builds on the premise that you shouldn't use a framework that you can't do without: I will create, live, a realistic web application without generators, without frameworks and without bullshit. Instead, I will use test-driven development to ensure steady progress to a solution with no magic.

      • Johannes Brodwall
        Johannes Brodwall
        Niruka Ruhunage
        Niruka Ruhunage
        schedule 3 years ago
        Sold Out!
        45 mins
        Demonstration
        Beginner

        Can you maintain agile engineering practices with a distributed team?

        Johannes is the Oslo based Chief Scientist for the Sri Lanka based company Exilesoft. In order to promote agile engineering practices, he uses remote pair programming to connect with teams halfway across the world.

        In this talk, we will go through a practical approach for remote pair programming adopted for high-latency situations. We will demonstrate remote pair programming with a live example and we will discuss the advantages and usages of the approach. We will also cover the practical parts of remote pair programming, such as tools and setup.

        After seeing this talk, the audience should be able to remotely pair with members of their distributed team. They will also get a lot of tips on how to use pair programming effectively in both local and remote settings.

      • Liked Anuradha Gajanayaka
        keyboard_arrow_down

        Convincing Agile Estimation to a non-Agile Project board

        Anuradha Gajanayaka
        Anuradha Gajanayaka
        schedule 3 years ago
        Sold Out!
        20 mins
        Case Study
        Intermediate

        Software development estimates are considered to be evil. If you have attended Agile India 2013 you know what I’m talking about! Both we use user stories and points or Gantt chat and hours, we have never discovered that magical formula for the right estimation.

        But is it something you dare to tell your project board?

        The bad news is that the software industry may not be able to forgone Estimate for a foreseeable future. The good news is that agile estimation techniques provides some kind of balance between need for estimates and inability to predict future.

        Still, our Agile Estimates can be really challenging when the receiving partly has no clue about Agile Software Development, specially the customers, members of project control boards and senior management.

        In this case study, I would like to draw the experience on how we used certain techniques and invented some tools to convince a non-Agile, traditional project board to use Agile Estimates.

      • Liked Pradeepa Narayanaswamy
        keyboard_arrow_down

        WORKSHOP- Defining Behaviors as a team

        Pradeepa Narayanaswamy
        Pradeepa Narayanaswamy
        schedule 3 years ago
        Sold Out!
        45 mins
        Workshop
        Intermediate

        In lot of agile teams, often times, all the team members will be doing the grooming and planning exercise as a team. Often times, defining the behaviors is either ignored, overlooked, skimped or done by individuals on their own without a common understanding as a team.

        To solve this problem, I have used this hands-on time-boxed activity for all of my teams to define behaviors as they move along in the sprint. This will help all the team members to have a shared understanding on their users and their behaviors as it relates to their user story. This is an activity that any agile team member can take and implement the next day at work.

         

         

      • Liked Anuradha Gajanayaka
        keyboard_arrow_down

        Some say they do Scrum to be agile ...

        Anuradha Gajanayaka
        Anuradha Gajanayaka
        schedule 3 years ago
        Sold Out!
        45 mins
        Experience Report
        Intermediate

        In the challenging context of offshore Agile Software Development, not everything in the book would work. In this experience report, I would like to discuss how the teams can tailor the current so called standard Agile methodologies/practices (within the guidelines of the Agile Manifesto), yet become successful in deliveries.

        In the session, I would like to discuss some of the agile practices the audience is using and then discuss the challenges they face when it comes to Agile Offshore Development. Then I would like to draw my experience on offshore software development projects where we successfully used Agile concepts and demonstrate how to customize those standard methodologies/practices within the Agile Manifesto Framework.

      • Liked Tarang Baxi
        keyboard_arrow_down

        The Agile ContraDictionary

        Tarang Baxi
        Tarang Baxi
        schedule 3 years ago
        Sold Out!
        20 mins
        Talk
        Beginner

        Inspired by 'The Devil's Dictionary' by Ambrose Bierce, this is a satirical look at common misinterpretations and misunderstandings of Agile principles, processes, behaviours and roles. Precise, clear (re)definitions for Exactimation, Scrumudgeon, Abuser stories, Kanband-aid, Fragile methods, ScrumLord, Rundown chart, and many more!

      • Sudipta Lahiri
        Sudipta Lahiri
        schedule 3 years ago
        Sold Out!
        20 mins
        Experience Report
        Intermediate

        Fixed price (and fixed scope) projects dominate the offshore industry. These projects have offshore/onsite teams. They often have large team size (over 100s of people in one team).

        Agile thinking uses team velocity/ throughput and uses that to project an end date (Kanban system) or how much scope can be accomplished in a given time duration (number of sprints in SCRUM). They assume a stable team. However, this is not applicable for projects. They experience resource and productivity ramp-up issues. Often, resources keep changing as new projects come in. Projects do not have past velocity or throughput data. Extrapolating historical data from other similar projects, though possible, is inaccurate for multiple reasons.

        This talk is based on our experience of working with such project teams. They want to adopt agile methods. We show how they can adopt the Kanban Method and yet do: A) Initial Capacity Planning B) Assess the impact of scope creep to the project end date.

        The session assumes a basic understanding of the Kanban method.

      • Liked Shamira Dias
        keyboard_arrow_down

        GUIDING YOUR OFFSHORE CLIENT FROM WATERFALL TO AGILE: what works and how

        Shamira Dias
        Shamira Dias
        schedule 3 years ago
        Sold Out!
        45 mins
        Case Study
        Advanced

        A Scandinavian client who had bad experience with offshoring came to our doorstep. He was somewhat skeptical about offshoring but was willing to take a second chance. We had to be vigilant right from the start, it was a learning experience, a new project a suspicious customer and a watchful management… how did we handle the situation? The obstacles experienced by the team are universal. They are applicable to any team attempting to convert a client from waterfall to Agile.

         ss

         

         

        How did we initiate the project - what was the way forward?

        Were we cautions or did we plunge right in?

        Did we play by the rules or did we make our own?

         The learning experience of this talk is a step by step directive of how the above challenge was undertaken. The audience will be introduced to four attributes identified by the team as the four pillars of offshore agile rollout, namely being resilient, being innovative, being pro-active and being cooperative. By the end of the session the audience will understand

        (i)                 how to be resilient with the product owner, what are the essential practices

        (ii)               the habit of being innovative, what needs to be incorporated

        (iii)             the secret of pro-activeness, and taking control

        (iv)             the importance of being cooperative, how to instigate productive discussions

        Following this case study the audience will be able to apply the four pillars of offshore agile rollout to challenges faced with their own clientele.