Agile RFC Pilot Newsletter 1 LET'S GET STARTED!


Welcome to our first newsletter regarding the Agile RFC Pilot. Throughout the pilot, we will send you monthly newsletters to update you on the progress and to share the learnings with each other. Please enjoy reading it. Let’s get started!

Embedding the Agile way of working


In line with one of the strategic pillars of GIS, AMS also continues to develop it’s Agile capability. Earlier this year AMS has successfully explored the Agile way of working for the delivery of change requests which demonstrated benefits such as: adaptive to change, shorter Time To Market and increased collaboration. As AMS we would now like to expand this to more Operating Companies and more common solutions. By means of a Design Thinking workshop this was kicked off mid-September. Leveraging the collaboration between OpCo’s, IBM and AMS, this workshop resulted in a complete new process design. Read this newsletter to learn about the workshop, it’s outcomes, the reactions of 8 participants and the next steps.

The story so far...

Agile Workshop September 14/15

On September 14th and 15th IBM facilitated a HEINEKEN Design Thinking Workshop. The aim for this workshop was to create a new process that everyone agrees upon and that adds value to all the stakeholders involved. We decided to focus on 4 personas: Developer, On-Site Coordinator/Scrum Master, BAS Specialist/GIS Product Owner and OpCo User/OpCo Product Owner. The participants were split into 4 multi-disciplinary groups. Each group approached the RFC process from the perspective of a different user. They created their own persona, which they focused on for the rest of the workshop. Part 1 of the workshop was about Understanding the User’s Experience (Empathy map, As-Is Scenario), part 2 about Envisioning the Future (To-Be Scenario, Prototyping, Storyboard, Action Planning).

Highlights of the workshop

1. Designed End-to-end Agile delivery process for RFC delivery

2. Agreed to form Product Owner Committee that includes BAS specialists and OpCo business & IT

3. IBM on-site coordinator to act as Scrum Master in the pilot

4. Defined Agile RFC selection criteria

5. Guaranteed story points (Capacity) in every sprint per OpCo

6. Commitment from every stakeholder: OpCo, IBM & AMS team

7. Automation of testing is key to reduce Time to Market

What did 8 participants think about the workshop?

Are they enthusiastic about the new way of working? Or do they have doubts? Read their reactions below:

“The advantages of this new way of working is that we will be more flexible and more adaptable. Through flexibility and prioritizing we will be able to decrease the lead time to deliver parts of the product from 2 months to 3 weeks. A better collaboration will also manage expectations and put an end to silo thinking and acting.”
“We need to increase customer satisfaction. If not, we will lose their involvement. This Agile way of working could be a road to that. I am enthusiastic but I am also critical because I wonder how we are going to manage it within the OpCo. Time will tell.”
“This Agile workshop is all about collaboration and the trust that we need to build. It’s not just ‘we deliver when the business asks us’ anymore. I am sure there will be hurdles on the way. It will not be a 100% perfect at first, we need to accept that. But once we go through it, it will be a success for sure.”
“Normally everybody works in silence, in all areas. We will really have to practice working in a team. I am sure it will empower me to make better decisions based on the value that we can provide to our business, because I will be closer to the OpCo and I will be able to understand our user better. It will also help me to connect with the customer more often.”
“The pain point on the OpCo side is that they quite often have to wait too long for a solution. I really hope the process will be shorter with this way of working. We will need help and sponsorship from Global and local management to get this in place because, unlike IT people, the business is a bit hesitant in accepting and embracing a new way of working.”
“Agile will help us at the beginning of the process to structure the back log and to be open minded. When you get a RFC, a lot of work will already have been done. It puts the priority where it needs to be but it also means that we, as BAS specialists, need to describe clearly what the product looks like and do it First Time Right.”
“I see a lot of advantages. Developers will be smiling more because they have a start and a finish! They have to deliver what has value and it is clear what the timing is and what needs to be done. No blaming, it’s a shared responsibility. We make the business part of the solution.”
“I am very, very excited about this. Everybody will own the deliverables and have a voice now. The very mindset has to change. I need to empower my people and tell them: be open, don’t keep questions to yourself, talk to people, talk to me, talk to the product owner, understand each other, let’s make it together!”

Next Steps

• Detail the new procedure | The workshop output is a start of the new process, but needs to be detailed out further (for example with timelines).

Define Follow-up on ideas | Define the budget, external considerations, and cost-benefit of the proposed ideas.

Roadmap | Develop a roadmap to bring this process into place.

Do you wish to know more about this initiative? Please send an e-mail to ajinkya.apte@heineken.com

Created By
GPB Media B.V. Hall


Content: Limona Communicatie

Report Abuse

If you feel that this video content violates the Adobe Terms of Use, you may report this content by filling out this quick form.

To report a Copyright Violation, please follow Section 17 in the Terms of Use.