Fibonacci Pairing: Learning through CollaborationYilmaz Guleryuz
schedule 2 years agoSold Out!
According to many researches, we learn the best when we experience it personally, and we comprehend when we teach to someone else.
So if you want to achieve ample understanding of a topic, you’ll need to follow these basic steps:
"Listen -> Observe -> Do -> Share"
Pair-programming is a well-known practice, and it has been introduced by one of the thought leaders of Agile world, Kent Beck. I respect any technique that encourages collaboration and interaction among teams, and gets teams to communicate better.
However, if you want to establish understanding of mastery or a skill-set, and increase the shared knowledge across your team members, then you need to re-think & apply new techniques.
In this talk, I’ll share about What-Why-How of "Fibonacci Pairing" technique, which is yet another discovery from practice.
The main goal of that technique is to establish understanding and improve collaboration, without overcrowding by artificial ways like lecturing.
Fibonacci Pairing is simple yet very effective technique that can improve team work. This technique should be regarded as a complementary way to improve team culture effectively.
We will elaborate with practical examples, real life experiences, and applicable ways onto different contexts.
Ownership TransferVinod Sankaranarayanan
schedule 2 years agoSold Out!
Getting a different team to take over an application brings in challenges from multiple perspectives. There will be differences around processes, engineering as well as culture. Larger transfers would also involve changes to infrastructure. For long, the industry has done a disservice to this field by calling it Knowledge Transfer. Knowledge Transfer, is but a subset of the scope of activities involved in this exercise. We propose to rename this as Ownership Transfer.
In specific - we put this process into practice with one of our customers. After more than 5 years of supporting the platform, ThoughtWorks worked with The customer teams to transfer knowledge and context back to the customer. A few highlights on the application.
• More than 80% of all online ticket sales are done through this application
• More than 400,000 visits a day
• Close to 5 billion USD of ticket sales
• More than 70 VMs supporting the production application
• Upwards of 300 VMs supporting other development and testing environments
A few highlights on the program,
• More than 150 IT members involved in the program
• A ramp-down was part of the process to get the final numbers to about 60
• The transfer had to occur from Bangalore back to London
• Infrastructure had to re-optimised from Bangalore over to London
• Two organisations were involved viz. ThoughtWorks and the customer
Since both Bangalore and London were following agile practices, the teams decided to utilise core agile concepts to effect the transfer. This became all the more important as business required critical features to be delivered on a continuous basis.
Before we started off on this exercise, we created a methodology to effect the transfer. This methodology is fairly context agnostic and should support a healthy, sustainable and mature way to transfer ownership. The transition itself was about a year long and involved multiple aspects around agile such as remote pairing, program MVP and above all, continuous delivery and non-disruption to business through the process.
The session will introduce a framework that can be applied to most Ownership Transfer situations. In particular, this will be of interest to groups who are looking to transfer ownership from one team to another. These could be from a development team to a support team, or from one vendor to another as well. This will also provide insights on transferring ownership across distributed teams.