schedule Feb 28th 03:30 PM - Jan 1st 12:00 AM place Sigma

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.
 
7 favorite thumb_down thumb_up 16 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. Intro: "What is extreme programming" (ping pong programming and the 3, 4 or 5 steps of TDD)
  2. Demo (10 minutes): Johannes demonstrates a simple problem with a volunteer from the audience
  3. Warm-up exercise (15 minutes): Working in pairs
  4. Exercise (45 minutes): Working in pairs
  5. Retrospective

(NB: The session is even better if extended to 2 or 2,5 hours)

Learning Outcome

How to become a better programmer

  • Breaking down programming problems
  • Using your IDE better
  • Working effectively with tests
  • Working effectively in pairs
  • Refactoring

Target Audience

Developers

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Deepak Dhananjaya
    By Deepak Dhananjaya  ~  1 year ago
    reply Reply

    Hi Johannes, 

     Very inviting proposal! Would like to know what could be the good size of the audience for this dojo? i also read that you would do Projector style, in which case, how many could participate in this dojo? Would you do timer based rotation? Would invite you to think on the ways to keep the audience engaging as its hands on, and if its projector style!

    Deepak

    • Johannes Brodwall
      By Johannes Brodwall  ~  4 years ago
      reply Reply

      I've done dojos with 6 to 35 participants and all have been great. I could probably go beyond. When I pass 20-25 I like to have an assistant.

      For the projector style the number of people per projector limits how often each person gets to be at the keyboard. This effect starts to show at 6 and at 9 or beyond, someone will inevitably be less engaged. I can bring 2-3 coaches with computers (these will in effect be co-presenters), so we can handle 3-4 groups. In this case around 25-30 is the limit.

      When I do pairing style, I and my assistant walk around and basically stop people who're running in the wrong direction, point them in the right direction and let them continue. When I do a projector-style, I or my asistant will ask the group provokative questions or help them refocus on making progress.

       

  • Joel Tosi
    By Joel Tosi  ~  4 years ago
    reply Reply

    Hi Johannes,

       Congrats on having your submission accepted. Is there anything I can work with you on for your session?  Any material you would like a second set of eyes on any examples, etc?  Let me know how I can best assist.

     

    Best,

    Joel

    • Johannes Brodwall
      By Johannes Brodwall  ~  4 years ago
      reply Reply

      Thanks, Joel.

      Is your request that you would like to assist during the workshop? I'm planning on using a standard kata, probably roman numbers or prime factors. If there's many people who sign up, I could use a teaching assistant who has practiced the problem in advance. Interested?

      (The rest of the materials will be the same as multiple dojos that I've run. You can see the slideshare link for the slides)

      • Joel Tosi
        By Joel Tosi  ~  4 years ago
        reply Reply

        I doubt I will be at the conference sadly.  I like both of those katas.  Should we plan on getting you an assistant to be safe?

        • Johannes Brodwall
          By Johannes Brodwall  ~  4 years ago
          reply Reply

          I expect one of my colleagues who will be present can assist. Do you guys know how many people to expect? I usually like one assistant when I pass 25 people at the workshop and another when I get to 35-40.

  • Johannes Brodwall
    By Johannes Brodwall  ~  4 years ago
    reply Reply

    (Guys: If you've asked me a question and were happy with my answer, please vote for my talk :) )

  • Ram Srinivasan
    By Ram Srinivasan  ~  4 years ago
    reply Reply

    Hi Johannes,

    What language/IDE do you plan on using?

    Thanks,
    Ram

    • Johannes Brodwall
      By Johannes Brodwall  ~  4 years ago
      reply Reply

      Hi Ram

      We will either do a pairing style or a projector-style dojo. In the pairing style, people are free to pair with someone who also want to program in their favorite language. For the projector-style, we will take a quick poll and choose the language that most participants know among Java, C#, JavaScript, Ruby or Python.

  • Naresh Jain
    By Naresh Jain  ~  4 years ago
    reply Reply

    Hi Johannes,

    This is a great proposal and love the idea of running a Dojo at the conference.

    However I would like to set some expecations:

    * Last couple of years, in spite of us making it clear that its a hands-on programming session, 90% of the participants showed up without a laptop. Speakers had to immediately switch the format to something, which would work without a computer. For ex: last year in my TDD workshop, I asked participants to write down their first test on a paper and then we went around and discuss it. For my BDD workshop, I ended up doing a live demo. 

    * In case of the Dojo, may be you can have your computer connected to the project and invite participants to come up and pair on your machine, while others can watch or if they have laptops, they can program.

    * Also giving more than 90 mins would not be possible. Would suggest you reduce the number of examples to fit inside 90 mins slot.

    • Johannes Brodwall
      By Johannes Brodwall  ~  4 years ago
      reply Reply

      Hi Naresh

      I've got good experience with running both a pairing style and a randori-style (projector-based). I think the learning benefit is greatest from the pairing-style dojo, but either way is fine.

      For a ninety minute dojo, we could do Leap Years as a warm-up and Prime Factors as a main exercise. The fastest programmers would probably be able to complete both, but it's not necessary to complete the exercise to get a huge learning benefit.

  • Tathagat Varma
    By Tathagat Varma  ~  4 years ago
    reply Reply

    Hi Johannes - I believe the core agile engineering practices like pair programming, test driven development and continuous refactoring are more mainstream part and parcel of agile development practices. To that end, do you want to consider looking at tracks such as agile lifecycle in case there is a better fit with the overall track theme?

    -TV

    • Johannes Brodwall
      By Johannes Brodwall  ~  4 years ago
      reply Reply

      Thanks for the comment, Tathagat. I'm not sure if I understand you correctly, but I updated the workshop to be in the Agile lifecycle track instead. I agree it's a better fit.

  • gnuyoga
    By gnuyoga  ~  4 years ago
    reply Reply

    @johannes

    Very interesting topic i should say. 

    Are you gonna cover CI/CD aspects as part of Continous refactoring. I feel that if we dont have the vision of pushing code live ( Release early and Release often ) doing continous refactoring is of limited use. 

    Curious to know about "IDE tricks". Will the tricks be applicable to tools like {emacs, vi} ? or certain types of IDE ( Eclipse sorts ? ) 

     

     

    • Johannes Brodwall
      By Johannes Brodwall  ~  4 years ago
      reply Reply

      I agree that continuous integration is a cornerstone to software craftsmanship practices. However, in this workshop, there will not be time to implement this. I focus instead of giving people a hands-on experience with TDD, refactoring and pair programming.

      The IDE tricks come mostly from pair programming. In all the dojos I've conducted people come out learning a lot from their pair programming partner. This means that if you pair with another e.g. Vi user, you will learn Vi tricks. ;-)

      Regarding refactoring: I think you should come to my workshop, I think it would expand your view on what refactoring can be. :-)


  • Liked Pramod Sadalage
    keyboard_arrow_down

    Pramod Sadalage - Ten Patterns of Database Refactoring

    Pramod Sadalage
    Pramod Sadalage
    Software Developer
    ThoughtWorks
    schedule 4 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

    Johannes Brodwall / Niruka Ruhunage - Remote Pair Programming

    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 Evan Leybourn
    keyboard_arrow_down

    Evan Leybourn - From Lean Startup to Agile Enterprise (beyond IT)

    45 Mins
    Talk
    Beginner

    Traditional models of management and corporate governance are failing to keep up with the needs of the modern economy. Change, both technological and cultural, is occurring at faster rates than ever before. In this climate, modern enterprises will live or die on their ability to adapt. This is where Agile, and Agile Business Management, come in. Agile is change; changing how you think, changing how you work and changing the way you interact. This is important whether you are a software developer or a CEO.

    In this presentation, Evan will provide engaging and enlightening case studies of Agile beyond IT; from lean startups to large enterprises. These will be reinforced with practical approaches for the leadership of teams, divisions and businesses. 

    Taking the successful concepts and methods from the Agile movement and Evan's new book, Agile Business Management is a framework for the day-to-day management of organisations regardless of industry, size or location. We will discuss processes, techniques, and case studies for the 4 key domains from Agile Business Management;

    1. You, the Agile Manager - What makes a good manager and how do their responsibilities change?
    2. Integrated Customer Engagement - Collaboration and communication techniques to build trust and deliver Customer needs efficiently, with minimal waste, and to everyone's satisfaction.
    3. The Structure of an Agile Organisation - Efficient, transparent and collaborative techniques to manage empowered staff.
    4. Work, the Agile Way - Managing all types of business functions, from software, HR, finance to legal, by using Just-In-Time planning and Incremental or Continuous Delivery processes.

    Ultimately, the goal of this presentation is to make you think about your role as a leader. 

  • Aman King
    Aman King
    Agile Technologist
    ThoughtWorks
    schedule 4 years ago
    Sold Out!
    20 Mins
    Experience Report
    Beginner

    Are you an Agile Practitioner? Or are you responsible for Agile transformation?

    Organizations that have begun their Agile journey welcome the guidance of an experienced Agile Coach. But external guidance cannot continue indefinitely as the only way to scale Agile.

    If you are in an Agile team, are you prepared to take on the coaching role for other teams once your Agile Coach moves on?

    If you are a manager, are you looking at grooming in-house coaches to scale and self-sustain transformation?

    The transitioning of practitioners into coaches can be key to your Agile journey. Individuals get to build on their potential, while the organization becomes more self-reliant.

    This session explores my personal journey from practitioner to coach. It should help you too in taking that first jump into the role of a coach. I will share real-world examples of dealing with on-the-fly situations, and of preparing upfront where possible. I will recommend resources, and mention handy techniques that should be in a coach's toolkit. The session essentially provides a kick-start for first-time coaches.

  • Liked Vinodhini
    keyboard_arrow_down

    Vinodhini / Thushara Wijewardena - Robotic Warehouses, Alien Domain, Offshore developers, Visionary customer : Saved by agile

    20 Mins
    Experience Report
    Intermediate

    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

  • Liked Prasanna Vaste
    keyboard_arrow_down

    Prasanna Vaste - Should we stop using Story Points and Velocity?

    Prasanna Vaste
    Prasanna Vaste
    Business Analyst
    Thoughtworks
    schedule 4 years ago
    Sold Out!
    20 Mins
    Experience Report
    Beginner

    On Agile projects we estimate user stories in order to allow team to

    1. 1. Track velocity
    2. 2. Decide scope for the Iteration
    3. 3. Help Prioritize stories
    4. 4. Help Release planning

    But most of the time we faced issues with estimation. It takes lot of time in estimating user stories, managers tend to relate estimate to number of days it will take to complete the story, in some teams estimate is equal to deadline. Most of the teams which use story points to estimate the work face these issues. This results in lack of confidence on development team when stories are taking more time to complete.

    Here I am going to talk about better alternative for both the suppliers of software products (financially and ethically) and their customers (internal and external). This alternative is being used in real companies delivering to real customers with great effect where team uses count of stories completed in an Iteration as measure of progress. Will talk about how this alternative can be used to track velocity, prioritize stories, planning Iteration and for release planning.

    I will share some exmples from my past projects where team did not use story points/velocty but used count of stories completed in Iteration to measure progress and also as best indicator of future performance.

  • Liked Tathagat Varma
    keyboard_arrow_down

    Tathagat Varma - Agility @ The Scale of Busine$$

    Tathagat Varma
    Tathagat Varma
    Founder
    Thought Leadership
    schedule 4 years ago
    Sold Out!
    45 Mins
    Case Study
    Advanced

    [24]7 Customer, Inc started out in customer service space from Bangalore in 2000. Today, it is a sucessful mid-size company in voice-based customer support that also creates IP and products in big data and predictive analytics for some of the biggest names in business, and is a a high-growth company headquartered out of US. The growth in product R&D happened both organically as well as from acquisitions across multiple geos. While the initial / startup stage processes had been extremely successful in building the company's strong foundation, it was felt that the next stage of growth might not be a linear extrapolation of the past successes. Recognizing this futuristic need, it initially embraced agile software development methods in Q1 of 2013 to improve responsiveness, predictability and time to market in the product development organization. In Q2 of 2013, it embarked upon an ambitious company-wide program. The charter was to establish an end-to-end execution framework to make the entire operations efficient and effective - right from marketing and pre-sales to delivery, deployment, operations and ongoing optimization. 

    In this session,

    • We will analyze challanges involved in scaling-up agile adoption outside the software team across the entire organization.
    • Specifically, we will also discuss how we addressed some of those unique challanges that are associated with growth and scale, and
    • What does it take to achieve true end-to-end agility. 
  • Liked Naresh Jain
    keyboard_arrow_down

    Naresh Jain - SAMPLE PROPOSAL - Product Discovery Workshop

    Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 4 years ago
    Sold Out!
    90 Mins
    Tutorial
    Beginner

    Many product companies struggle with a big challenge: how to identify a Minimal Viable Product that will let them quickly validate their product hypothesis?

    Teams that share the product vision and agree on priorities for features are able to move faster and more effectively.

    During this workshop, we’ll take a hypothetical product and coach you on how to effectively come up with an evolutionary roadmap for your product.

    This 90 mins workshop teaches you how to collaborate on the vision of the product and create a Product Backlog, a User Story map and a pragmatic Release Plan.

    This is a sample proposal to demonstrate how your proposal can look on this submission system.

  • Liked Johannes Brodwall
    keyboard_arrow_down

    Johannes Brodwall - Bare-Knuckle Web Development

    Johannes Brodwall
    Johannes Brodwall
    Chief Scientist
    Exilesoft
    schedule 4 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.

  • Liked Aruni Siriwardene
    keyboard_arrow_down

    Aruni Siriwardene - The Waterfall enthusiast and The Agile Contract

    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!

  • Liked Anuradha Gajanayaka
    keyboard_arrow_down

    Anuradha Gajanayaka - Convincing Agile Estimation to a non-Agile Project board

    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

    Pradeepa Narayanaswamy - WORKSHOP- Defining Behaviors as a team

    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

    Anuradha Gajanayaka - Some say they do Scrum to be agile ...

    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

    Tarang Baxi - The Agile ContraDictionary

    Tarang Baxi
    Tarang Baxi
    Principal Consultant
    ThoughtWorks
    schedule 4 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!

  • Liked Aruna Rajapaksha
    keyboard_arrow_down

    Aruna Rajapaksha - Remote Pair Testing

    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 Johannes Brodwall
    keyboard_arrow_down

    Johannes Brodwall - Kicking off agile remote teams

    Johannes Brodwall
    Johannes Brodwall
    Chief Scientist
    Exilesoft
    schedule 4 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 Shamira Dias
    keyboard_arrow_down

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

    Shamira Dias
    Shamira Dias
    Delivery Manager
    Exilesoft Pvt Ltd
    schedule 4 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.