Agile, Testing and DevOps: Are they a Separate conversation or a progression of capability?
DevOps, Testing and Agile have shared environments that facilitate working together. Spurred by greater demand for excellence, these three methods are more than simply adopting new tools and processes. The synergy involves building an evolving and a stable Continuous Integration (CI) Infrastructure, as well as an automated pipeline that moves deliverables from development to production to meet users’ expectations. They can work together, and the entire build process should be transparent, and it should enable and support development and operations. This transformation depends on: significant changes in culture; roles and responsibilities; team structure; tools and processes.
The Round Table session is for 45 minutes. The speaker at each table will have a set theme and delegates join any table that they are interested in. They are given all the topics with their joining instructions and again at the time of registration and so make their choice on the topics that they want to attend. This is a discussion group and so no presentation slides are necessary, but please submit a topic if you would like to chair a discussion on a topic related to Testing, Agile and DevOps.
Among the topic addressed are
We are inviting speakers – thought leaders, subject experts and start up entrepreneurs – to share their knowledge and enthusiasm about their work and their vision in the field of Agile, Testing and DevOps.
We understand that successful projects are written up as “White Papers”. Please share these with us. But projects that did not achieve their targets – “Black Papers” – are of interest to us too. They can be a very important topics of discussion / panels that you can present. Talk to us about both, we welcome your input.
Please complete the speaker’s response form and submit a proposal to present at this event.
UNICOM’s Code of Conduct & Views on Diversity
We at UNICOM strive to be a leading provider of knowledge to the business community and to engage the global business community as a specialised provider of knowledge. We strive to do this maintaining a culture of co-operation, commitment and trust. We want every UNICOM conference and training day to be a safe and productive environment for everyone – a place to share research and innovation and to build professional networks. To that end, we will enforce a code of conduct throughout all our events. We expect cooperation from all participants to help ensure a safe environment for everybody.
Our approach is that our events are dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity or religion. We do not tolerate intimidation, stalking, harassing photography or recording, sustained disruption of sessions or events, and unwelcome physical contact or sexual attention. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, Twitter and other online media. Event participants violating these rules may be sanctioned or expelled from the event without a refund at the discretion of the conference organisers. Please bring your concerns to the immediate attention of the event staff.
Diversity: In our endeavour to be the provider of knowledge to the business community, we understand that this depends on hearing from and listening to a variety of perspectives that come from people of all races, ethnicities, genders, ages, abilities, religions, sexual orientation, and military service. We welcome diverse speakers for all our events, we do not always fully achieve this goal, but it is an ongoing process.
An introduction and scene setting for the day
Aldo Rall, Agile Coach, Ministry of Social Development (MSD)
You have heard have about the successes from other teams, and are motivated to start your Agile journey, but not sure where to start. There are so many different messages and noise about Agile.
Or you have been on your journey for a while, but you have become disillusioned and are struggling; You are at a loss as to what do or try next. Perhaps you have run into unintended consequences by being stuck with a practice or method that simply is not working for you.
Or, you are about to give up on your Agile journey, feeling disillusioned and filled with despair. Then this talk is for you: There is hope.
We will explore a few basic ideas to get you on your way, and then look at how to use the Disciplined Agile toolkit to make informed choices. This talk will cover the following:
Steve Peacocke, Chief Executive Officer, DragonsArm
Sometimes, teams are so focused on the customer that they are unable to perform. In this talk, I will discuss a real-life example of a problem encountered with a few teams who had just this issue.
In our eagerness to satisfy the Agile mindset of Customer collaboration and satisfying the customer, we can often fall into a trap that none of us expects. In this case, it led to the worst possible outcome – an inability to deliver.
How can this happen? Surely being closer to the customer is the best possible position? As it turns out, it can cripple our productivity and set the team into a spiral that is difficult to come out of. Nothing was getting done and the team carried all the blame when in fact, the blame lay equally between the team and the customer.
It took someone from outside of the loop to see the problem and act.
As the Principal Consultant for Agile for a government department, I found exactly this situation. I was at a loss as to how to resolve this situation. I tried a number of tactics to try to resolve the situation and both sides were willing to do whatever it took.
Dragging the teams away from the customer sounds very un-agile, but in this case, it was the only option. I’ll show you what we did and how we did it.
The worst of those teams are now considered one of the most customer-centric teams in the organisation, getting praise from some unexpected areas.
David Fuller, Board Member/Treasurer, ANZTB
There are so many opportunities for us to develop ourselves, improve the way we ensure Quality and how we deliver (earlier) value to our Customers.
In this talk I will look at what these opportunities are and how we can achieve higher quality, deliver quicker and improve our skillsets.
But it’s not just about ourselves, we can also influence change within our organisations and improve the relationships we have with our Clients and Suppliers.
We will discuss the challenges and successes you have observed, leveraging Agile & DevOps practices, so we can improve our effectiveness.
Helen Snitkovsky, Associate – Head of Business Agility, The Migration Company
DevOps can be a backbone of your company’s success when it’s done properly. What does it take to be successful with DevOps?
How can you make most your investment?
According to AWS, DevOps is the combination of cultural philosophies, practices, and tools that increase an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes.
I will be sharing the secret sauce of DevOps transformation, and how to combine both culture, processes and tools for a win-win outcome.
Grant Simonds, Agile Ways of Working Coach, Telstra
Presentation on the micro service design, challenges and architecture used to power the Telstra TV3 and it’s voice control. Overview of the design and architecture, development strategy and DevOps strategy that the team used to design, develop and deploy the backend systems used to support Telstra TV. Show how Docker, Kubernetes and Amazon AWS can be used to quickly deploy new services. Present the need for DevOps processes when a micro service architecture is used. Present a working architecture that the team used to enable voice control on Telstra TV3.
Abhijit Khan, Practice Leader, Performance Testing & Engineering (PACE), Cognizant Technology Solutions
The Software development process has undergone a paradigm shift in the last few years mostly owing to a number of technology innovations, rising user expectations and delivery efficiency that was unprecedented in the last decade. In a fast paced world, where the feedback loop is very short and quick , there is no option other than transforming the entire delivery mechanism. Incremental change has become the de-facto standard instead of a big bang transformation. And the way you can embrace that change and deliver efficiently – is by establishing a mechanism that fosters seamless flow of ‘quality’ events.
This has been made possible by the ‘Continuous Delivery’. The principle behind continuous delivery remains as the chain of events managed through an uninterrupted and automated process. A true ‘Continuous Delivery’ is enabled by ‘Continuous Integration’, ‘Continuous Testing’ and ‘Continuous Deployment’ – all in an automated and meaningful way. This talk aims to address the ‘continuous Testing out of these triangle. It expands on the ingredients and the success criteria for achieving true Continuous Testing, ably supported by automation.
In a rush to deliver, teams often rely on a narrow definition of ‘testing’ , represented by a high-maintenance automated suite followed by significant manual acceptance testing. Even if there is an attempt to include a set of regression set as part of the build process, it is often limited to functional acceptance tests, ignoring the many other forms of testing that should be part of your continuous testing spectrum. The definition and the scope for continuous testing is much broader than these popular assumptions. A true continuous testing starts with ‘quality’ at the center and expands the different aspects of testing that helps to bring the best in the product. As we start to embrace more of continuous delivery, continuous testing will be even more critical in that journey as it will ensure – ‘quality’ will not be a discrete set of events, rather a continuous process. ‘Quality’ cannot be built into the product, it will have to be flowed in, right from the start.
Marat Basyrov, CEO, ADEVI
There are 2 main problems with the current development lifecycle. Fragmentation of the software development processes and tools, and the second problem relates to user experience. Attempting to automate frontend development would allow to software developers to focus on most complex engineering issues rather than rudimental areas.
Collaboration between designers and developers is quite problematic, in my view too. Breaking the tasks on the smaller pieces and allowing agility would be the ideal environment. The Inspect feature by Invision is great but looking at the whole development process is not ideal (this is my view).
Communication is another huge issue and building a rapport over many years of working together, of course, allows making it fluent. Reality is that a lot of companies have turnover, and sometimes teams are put together on a project basis. At the same time, there are also other project stakeholders that collaborate on a project.
Melbourne Convention and Exhibition Centre (MCEC)
1 Convention Centre Pl
South Wharf VIC 3006