We are delighted to confirm our Software Delivery line up which will run on the both days at Agile on the Beach
The Software Delivery track will be headlined by a keynote from Rebecca Parsons CTO at Thoughtworks
- Build In Quality – Jo Cranford
- The design and implementation of cyber-dojo – Jon Jagger
- How we implemented TDD in Embedded C/C++ – Byran Wills-Heath
- 10% time the pros and cons?
- Testing in a Continuous Delivery World
– Wouter Lagerweij
- Continuously delivering software to big brands – Paul Boocock
- Smoothing the continuous delivery path – a tale of two architectures – Lyndsay Prewer
- Penetration Testing in the Release Pipeline – David Brownhill & Craig Scott-Angell
- Finding the merkle tree in the block chain forest – Jim Barritt
- Moving on Up – Sarah Glanville & Paul Lemon – Sky
- Being Agile: business survival essentials – Marc Heasman, Kainos
Jo Cranford Build In Quality
Short synopsis: After months of hacking things together, small changes often break a dozen other features. Even with every refactoring technique in the book, it’s going to be incredibly hard to improve unless you can make increasing quality part of your team’s development process. This talk discusses what constitutes “good code”, with practical to bring code quality and craftsmanship into your development lifecycle.
Bio: Jo is a lead developer at Culture Amp, the world’s leading culture analytics platform. Before her current role, Jo worked at the likes of Lonely Planet, Atlasssian, ThoughtWorks and Expedia, in roles such as Product Planner, Senior Business Analyst, Development Manager and Chief Technical Officer. She was also a CTO of an Australian startup accepted into Telstra’s Muru-D program. Jo is an experienced Ruby developer, a strong advocate of clean code and good tests, and has been working in agile teams for over ten years. She is passionate about increased diversity in the tech industry. When she’s not at her computer she can be found running around the Tan, or biking along the beach.
Long synopsis: With the exception of students, I have never met a developer who hasn’t had to work on a codebase that has areas of poorly written, untested code, at least once in their life. Making changes becomes incredibly painful and error prone, when changing code in one place has effects in seemingly unrelated areas. There are a lot of amazing resources on refactoring techniques, but without the support of a team who makes quality a priority, any improvement in quality is soon overtaken by careless hacks. With a development process that supports ongoing management and tracking of quality, refactoring can be spread out over time, the team can be confident that their efforts are being spent in the right places, and they waste less time justifying ‘refactoring’ cards or stories that don’t appear to have business value. Not only is work far more enjoyable and rewarding when we write “good” code, but over time, making changes becomes faster and easier. This talk discusses what constitutes “good code”, with practical to bring code quality and craftsmanship into your development lifecycle.
Jon Jagger The design and implementation of cyber-dojo
Short synopsis: http://cyber-dojo.org is an open-source browser-based environment where teams can practise programming. Under the hood it uses docker â€“ but in an unusual way.
Bio: I’m a self employed software consultant specialising in practice, process, TDD, and complex-adaptive systems-thinking. I’ve worked with Accenture, Aviva, Cisco, Ericsson, Friends Provident, HP, Microsoft, Operator, Ordnance Survey, RBS, Reuters, Renault F1, Schlumberger, Tandberg and many many more. I’m 31 years old (hex) and I’ve loved software since I was 10 (decimal). I live in Somerset in England. I’m married to the beautiful Natalie and dad to Ellie, Penny and Patrick. I love coarse fishing and salmon fishing. I’m the ex ACCU conference chairman. I’ve had some C# books published. I’m the co-author with Olve Maudal of the Deep C/C++ slide deck (over 600,000 views). On twitter I’m @JonJagger. I built cyber-dojo.org to promote deliberate practice for software developers.
Long synopsis: http://cyber-dojo.org is an open-source browser-based environment where teams can practise programming. The server is hosted inside a docker container, and it also uses docker (for isolation) but in an unusual way. In this presentation I’ll recount the story of cyber-dojo, starting from its origin, in the Scotsman pub in Oslo in 2009! I’ll do a brief demo, and show several key aspects of its design, its testing, its deployment, and the core principles on which it is based. I’ll discuss how it has evolved, who has helped, some of the difficulties it’s faced, and where it might be heading.
Byran Wills-Heath How we implemented TDD in Embedded C/C++
Short synopsis: We’ve been developing embedded software using TDD since 2009. This talk presents some of the patterns and practices that help us deal with the extra complications incurred when practising TDD in an embedded environment.
Bio: Byran began developing software at school as a teenager on BBC Micros; 22 years later he’s still passionate about software development. He’s worked in the embedded software industry for the past 16 years, working in a range of industries using technologies from 8051s to ARM microcontrollers. He currently lives in Cornwall, England working at Bluefruit Software. His recent focus has been on software testing of bare metal systems.
Long synopsis: With the ever increasing complexity of software the need to use development practices like Test Driven Development (TDD) is becoming more and more important. Embedded software development presents an extra set of challenges when practising TDD. Hardware is often still in development, expensive or has limited availability. Deploying to the target device takes a long time. The target device has limited program space and RAM. For these reasons testing of embedded software is often performed manually (if at all). We’ve been developing embedded software using TDD (and a variety of other Agile techniques) since 2009. This talk presents some of the patterns and practices that help us deal with the extra complications incurred when practising TDD in an embedded environment. It covers how we keep the feedback from our tests fast while still running tests on the target hardware. How we replace dependencies and discusses the advantages and disadvantages to the techniques shown.
Elizabeth Pope 10% time the pros and cons?
Short synopsis: I’m lucky enough to work for a company who offer 10% time, and believe it’s had many benefits for our team including engagement and performance improvements and as a tool for both retainment and attraction. However sometimes it can be hard to keep the business bought in to the idea of a very expensive team doing ‘nothing’ one day a fortnight. I’ll also share tips and tricks to get your team to make the most of their Learning and Development time without telling them what to do!
Bio: Liz started out as a QA Engineer at Holiday Extras in 2010. She’s come a long way since then, after revamping their testing team she had a spell as a Scrum Master before finding herself managing a team of developers. Liz has 3+ years experience in Management, focusing mostly on developing high performance and supporting the changing needs of a growing team. She currently Leads a Web team of 70+ people, and is passionate about having a motivated and empowered team.
Long synopsis: I’ll be talking about how Holiday Extras came to implement our version of 10% time, and why it has been successful (and when it hasn’t!). I will first focus on the positives I have seen as a result of 10% time. I’ll give examples of feedback the team have given on what they’ve personally got out of the time and how I’ve seen this have a knock on effect on our employee engagement. I’ll also give examples of where individual performance has improved thanks to the dedicated learning time, and examples of systems and functionality that were built because someone had an idea and began to implement it during this time and how this has contributed to our business. I’ll also speak honestly about the challenges 10% time can present for a business and what happens if someone is asked to skip it to deliver a project. I’ll give examples of when I believe this to be ok (business critical situations), and when a Product Owner is simply trying their luck! Finally I’ll give tips and ideas on how to coach a team to get them to make the most of the Learning and Development time. For example – guide someone to make better choices about what they are working on – encourage someone to spend their time working more collaboratively help come up with ideas – help someone who tries to do to much to focus on one thing at a time – encouraging someone who doesn’t want to take part to see how they can benefit
Wouter Lagerweij Testing in a Continuous Delivery World
Short synopsis: Hey, do you remember when everyone was asking what the role of the tester would be in an agile team? It’s happening again! A team that releases every commit needs to take testing seriously. That changes the role of the tester once again. And of developers, too. It puts the customer center stage again.
Bio: Wouter Lagerweij is an independent Agile Coach operating out of The Netherlands. He loves spending time with teams and organisations to figure out how to improve the way they make software, and make it more fun. To make that happen Wouter uses the knowledge and skills gathered in over eighteen years of experience applying Agile processes and practices from XP, Scrum, Kanban, Lean and Systems Thinking. To turn those improvements into real business opportunities, Wouter has added Lean Startup/Lean Enterprise approaches. He’s even known to, occasionally, use common sense.
Long synopsis: Hey, do you remember when everyone was asking what the role of the tester would be in an agile team? It’s happening again! And things are changing again. A team that takes on the challenge to release their every commit certainly will take testing seriously. It will need to evolve new ways of testing. It will have new dynamics of testers working with developers. It will find new ways of of interacting with customers, stakeholders and product owners. In this talk we’ll look at how continuous deployment changes the dynamics of an agile team. How quality moves even more to the center of the stage. How that changes the role of the tester once again. How it changes the role of developers, too. How this practice allows you to put the customer center stage again. And how that, too, has testing competencies at its core. And we’ll not forget DevOps, and how monitoring can be a continuous testing strategy.
Paul Boocock Continuously delivering software to big brands
Short synopsis: The ability to react and deliver working software quickly is a vital component to the way we work. Our clients run some of the biggest brands in the world, so how do we continuously deliver software whilst ensuring we keep our clients happy and our quality high?
Bio: Paul Boocock is the Academy Leader at Codeweavers, a leading finance technology specialist in the automotive industry. Paul focuses on staff development and learning across the entire business but with a particular focus on the development. Prior to Codeweavers Paul was a University Lecturer at Staffordshire University teach Software Engineer and Computer Games Programming. He has always been a developer at heart and relishes the opportunity to teach others as well as still getting his hands dirty.
Long synopsis: This talk will take you on a journey from a developers mind to our customer’s hands from writing the first test to deploying your changes to a live environment using a variety of techniques and tools. We will investigate our various processes and how they have adapted as our needs change as well as looking at the off the shelf and custom tooling we use. It’s not all about the process though, empowering our teams to continuously deliver is vital to everything working smoothly.
Lyndsay Prewer Smoothing the continuous delivery path – a tale of two architectures
Short synopsis: What makes Continuous Delivery easy and what makes it hard? Should it be all Scala, Docker and microservices, or is .Net, Windows and monoliths a safer bet? This session shares best practices and anti-patterns encountered by two teams, with very different architectures, both on their journey to successful continuous delivery.
Bio: Lyndsay is an Agile Delivery Consultant. He’s spent the last twenty years helping developers, teams and organisations improve their software delivery. He’s currently consulting for Equal Experts, at HMRC, on the delivery of HMRC’s new Gov.UK digital tax services. He speaks regularly at European conferences (Agile Cambridge, Agile Testing Days, Agile Lean Europe) and London Meetups. For more information, check out lyndsayp.com.
Long synopsis: Continuous Delivery is gaining recognition as a best practice. It’s in use by many leading organisations, including NetFlix, Amazon and Etsy. It’s a proven way of reducing risk, reducing time to market and increasing a team’s agility. Despite these benefits, adopting and improving it is challenging. This is the story of how two very different teams successfully practice and improve Continuous Delivery. Both teams were sizeable (more than five features teams) and mature in their use of agile and lean practices. One team chose Scala, mongodb, Docker and microservices, on a greenfield project. The other faced the constraints of legacy code, .Net, MySQL, Windows, and a monolithic architecture. This session shares the best practices and anti-patterns encountered by the two teams, looking at those common to both, and those that were specific to each team’s own context.
Short synopsis: Agile development teams that have security verification requirements for their user story acceptance criteria will have these defined using a BDD-style scenario. The talk will explain how the security tests can be defined and implemented using a framework combining tools from the popular KALI Linux tool-set.
Long synopsis: Teams should take security seriously with today’s online threats and follow secure coding practices. They should utilise web and native application scanning tools both statically and dynamically where-ever possible and required. These tools can be time consuming in a release pipeline which is where you want to target your testing to real security requirements for fast feedback. Utilising a framework like BDD-Security you can utilise a collection of provided scenarios or write your own specific security tests. Potential vulnerabilities within a build candidate may be functional and driven using Selenium WebDriver in the form of a traditional penetration test or API based. SSL vulnerabilities can be checked and verified using SSLyze and scans utilising the OWASP Zed Attack Proxy can be run. Example scenarios will be presented along with an example implementation of a release pipeline running against AWS, built from Team City using Ansible and executing vulnerability tests against both pre-production and production environments.
David is a Non Functional Test Consultant currently working with implementing non-functional requirements as part of a continuously deploying pipeline. In addition to security this includes performance and operational acceptance scenarios.
Graduating from Stirling University David started his career as a developer at British Telecom in Martlesham Heath progressing via performance testing to a more all encompassing role including a full range of non-functional responsibilities.
Craig is a Software Test Engineer with extensive experience in quality assurance through a career in defence, Finance and internet economy businesses.
Originally graduating as an Electro-Mechanical Engineer Craig started his career as a System engineer in defence at General Dynamics before moving to a career as a software Test Engineer for Ingenico UK and Skyscanner. Craig now works as a Senior Automation Engineer.
Working closely with Agile teams, Craig believes that Security testing should be a key component of the software development lifecycle to ensure secure, quality software in a continuous integration environment.
Craig is passionate about building quality from the start and thrives on the challenge of cultivating a security conscious culture to ensure continued success in the current climate of online threats.
Jim Barritt Finding the merkle tree in the block chain forest
Short synopsis: You may have heard that “block chain” technology is going to change the world (http://www.weforum.org/agenda/2015/12/how-blockchain-technology-could-change-the-world) . This talk will take you behind the scenes to explore what exactly is block chain anyway, from a technical perspective.
Bio: Jim Barritt has been writing code for many years. He is currently a Principal Consultant for ThoughtWorks. His passion is the code and systems architectures, helping teams deliver reliably and rapidly. https://about.me/jimbarritt
Long synopsis: Bitcoin has created a federated, digital currency in which there is no single authority to guarantee transactions – there is no bank. Instead a distributed collection of nodes process transactions and come to a consensus about the truth. The underlying algorithms and patterns that enable bitcoin to be successful have potentially widespread application in the areas of distributed contracts, verification of integrity of data and distributed financial transactions amongst others. This “block chain” technology is fast becoming the latest buzzword in the IT industry, even receiving attention from the the UK governments chief scientific officer on Radio 4 Today Programme (http://www.bbc.co.uk/programmes/p03fyd3z). The BBC have also published a series focusing on the social and economic impacts of this technology (http://www.bbc.co.uk/programmes/b066wfp4). But what is “block chain”, technically? What does it mean to a developer or a person building software? And what are these “Merkle Trees” that seem to play a big part in the story. In this talk, Jim will give an overview of blockchain from a technical perspective, starting with the original paper that was the foundation for bitcoin and discussing some of the component elements, such as Merkle Trees and how they might be applied in different scenarios. Along the way we will also visit related initiatives like google certificate transparency (https://www.certificate-transparency.org/)
Lunchtime Sponsored Speakers
Agile at Sky : As Gold sponsors we look forward to welcoming the Sky team to Agile on the Beach including a lunchtime session on Agile at Sky with Head of Technology Paul Lemon and Scrum Master, Sarah Glanville.
Moving on Up
Building a brand new agile team of over 100 people in 4 months is an exciting, challenging and rewarding task and Sarah and Paul will talk through the highs and lows and share their learnings from doing this. Sky are creating a brand new digital centre in Leeds, the heart of the Northern Powerhouse and this talk will share the experience of the first team to land in Leeds. How do you seed the culture, recruit the right people, set up the correct working practises and continue to deliver a committed roadmap?
Sarah Glanville – Sky – Scrum Master
Sarah Glanville is an enthusiastic and motivating speaker who has held several positions in Agile organisations and is passionate about inspiring women into a role in STEM careers. She has worked in many male dominated environments and is a strong believer in diversity being the key to a successful team. Sarah is currently a Scrum Master at Sky, where she ensures the wellbeing of her team and empowers them to continuously improve their practices whilst still meeting the high expectations of their customers. @girlstest2
Paul Lemon – Sky – Head of Technology
Paul Lemon is a technical leader with over 16 years industry experience. He has a passion for the creation and development of digital products and content. He is an expert at agile technical delivery both leading and/or collaborating with stakeholders, project management and creative experts.
He is the Head of Technology for Sky’s 70+ online service team, heading up the team of Scrum Masters, Business Analysts, Engineers and Testers which he helped to build in Sky’s new tech hub in Leeds @anthonylime
Being Agile: business survival essentials – Marc Heasman, Kainos
The world of business is changing faster than ever. Digital start-ups are re-shaping long established industries with innovative business models and services that better meet customers’ needs. Companies that fail to respond to the challenge are falling by the wayside, with many high street names amongst the list of casualties.
This talk will discuss the drivers for digital transformation, including the use Agile to achieve the business flexibility required in the digital age. Highlighting the increasing use of mobile, it will outline the changing expectations of customers in how services are delivered and illustrate the impact on those businesses that have failed to respond. Identifying some of the dramatic shifts in market competition seen across many industries, we will discuss the imperative for digital transformation. Then, drawing from the practices of some of the world’s most successful digital businesses, we will describe the key features now increasingly essential to business survival, covering:
– Customer focus
– Service agility
– Data exploitation
– Technology maximization
– Systematic innovation
– Digital skills
– Experimental culture
At the end of the session, participants will have the opportunity to reflect on their own businesses and how they are using Agile to achieve broader digital transformation.
Digital technologies are not only radically changing how services are delivered, but they are fueling changes to customer demands and opening markets to new competition. Adopting an Agile approach to software development is one way in which organizations can increase their flexibility and respond to these changes, but on its own this isn’t enough. This talk will explore the drivers and features of digital transformation needed to survive in today’s ever-changing business landscape.
Marc is a leader in digital transformation and has a strong background in public service strategy and delivery. Having led Agile development on one of the Government’s 25 exemplar digital programmes, he combines practical experience with academic study from the Academy of Digital Business Leaders. He joined Kainos in September 2015 and is currently supporting DVSA’s digital transformation of its MOT Testing Service.
Kainos is a high growth, UK-based provider of IT services, consulting and software solutions. The Group specialises in the development of digital technology solutions; software design and agile software development; automated testing services; technology support services; and related ancillary services such as project management, all provided across multiple sectors.
View more sessions