Thursday promised to be as intense and event saturated as yesterday, so, having had our nutritious breakfasts, we rushed to the keynote session at 9.30 am, presented by Michael Brunton-Spall. He addressed an acute topic of maintaining security measures while working in Agile. Indeed, we’ve noticed such a tendency in a number of businesses after Agile transformation and had quite a hard time in each case, establishing the right balance between agility and security. This session gave us a foothold, proved how right we were in our methods and gave us a couple ideas on what can we do to improve our ways.
Next session – and again a conundrum. We had such heated discussions on what session to attend that almost reserved to pulling straws. All in all, we decided on “Crafting a robust deployment pipeline for the financial sector” by Boyan Mihaylov. From our experience of dealing with financial institutions we already know how rigid they are and how do they cling to that waterfall project management, so we were intrigued and later impressed by Mr. Mihaylov’s experience with pension fund. We especially loved the way he organized testing and CD/CI, configuring the processes so that they would perfectly fit organization’s specifics.
After the lunch we decided to allocate this energy we got on more practical matters, therefore opting for “The Agile Security Game” workshop from Charles Weir, lead author of Secure Development. Yes, we take security very seriously here, so we wanted to learn as much as possible on it while we’re here. At this session we were introduced to the ingenious game, developed by Security Lancaster with the aim to educate programmers, testers, project managers and stakeholders about all sorts of security threats they may face and how to face them. All materials on it are available here: http://bit.ly/_SecurityGame , which is a wonderful news for those who couldn’t attend. Believe me, this game is worth your time.
As for the session “The 5 pillars of collaborative product ownership” by John Le Drew, we were mostly attracted by the audacious description – but we never regretted that we came. This session showed us the product owner role in a completely different light – from the very definition to qualities, role culture and decision making. We’re quite anxious to apply our knowledge on practice as we get home.
This is when our educational part of Agile Cambridge Day Two ended and the entertainment part began – but this is not as interesting) Stay tuned for the Day Three report!