Technology, in the business landscape is ever-evolving as business challenges have become increasingly complex. To keep up, organisations must build and deploy innovative, timely solutions.
The focus of the conference is on finding methods and tools for business value through the adoption of Agile, DevOps and Testing and well-built software. This transformation depends on significant changes in culture, roles & responsibilities, team structure, and tools & processes.
This event is mainly focused on participants from South East Asia; hence the start and end times have been chosen for the convenience of participants from these Time Zones
UNICOM’s Code of Conduct & Views on Diversity
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.
We are inviting speakers – thought leaders, subject experts and start-up entrepreneurs – to share their knowledge and enthusiasm about their work and vision in these three fields. Please let us know too if you would like to participate in the panel sessions only.
We are also planning short “how to do” sessions or full-day workshops to run as pre or post conference events. Let us know if you have a related topic that you want to run as a workshop or an extended briefing.
Please complete the speaker’s response form submit a proposal to present at this event.
Vasantha Priya, Product Owner, Digitate
Due to the pandemic, the adoption of digital technologies has been phenomenal across the verticals and horizontals. There has been a behavioral shift in day-to-day life that includes working from home, door-step service delivery, digital payments etc. Every business understands that the increase in digitization has led to an exponential rise in customer expectations. Hence, there is a rapid demand from for organizations to deliver applications in the shortest time possible without compromising on the quality.
Software testing is no more a manual, siloed process. It has been evolving over decades with several test automation tools being introduced into the market. However, traditional test automation will not be sufficient to handle the rising agile and DevOps practices for software development, and hence comes the need for a futuristic approach- Autonomous testing.
This session talks about how autonomous testing that leverages AI/ML techniques, can be used to deliver better quality applications and take it to the market faster ultimately making your , test designing autonomous and achieve rapid application development.
The Journey of achieving No-Ops (No-Operations) always begins with 2 key objectives • Extreme automation • No “dedicated” infrastructure teams, ever!
In this era of tech-evolution, even though we are already in the middle of Industry 4.0 revolution, there is no unified / singular framework to adopt No-Ops. Everyone has a different take of what No-Ops to them means. While for some the idea of evolving their systems to minimal operations is exciting, for a few – its more of a way to refine management of teams & channelize their efforts into something towards development. Whatever it may be, loosing operations specialists is still a long distant dream. Maybe we are so dependent on Managed-Ops, that plugging it off “majorly” is a nightmare to even think of.
The continuous growth of the CD tooling with a plethora of extensions made available to the DevOps ecosystem, even though we have significantly achieved & reaped quantifiable benefits from this implementation – scaling this across the organizational divisions is becoming a visible challenge.
Introducing more evolutionary controls such as templating provisioning & orchestration, immunizing integrations & connectors, adding extended & deep monitoring systems etc., Uncertainty & Unreliability still is a common problem across transformation scoring charts.
Revolutionary processes like Chaos Engineering, Auto-Enabled SRE, AIOps are creating aspirational backlogs for BU’s who are still struggling to manage their existing implementation Operations (Ops) amalgamated with development transformational ways of using microservices, containerization etc. applications are becoming indeed complex to manage as well.
Current Ops management is already beyond the scope of manual management & it will eventually become worse in the years to come because of the growing complexity of applications.
It’s time to introduce a friend, DevOps & CD automation needed since a good long time. Welcome No-Ops!
Current process of test automation is a multi stage process involving -1) creation of manual test cases 2) creation of feature files and 3) creation of automation script.This process is time consuming and needs people with specific skills around programming/ scripting or automation tools and involves significant maintenance overhead.
It is anticipated that there will be increased usage of test automation at all levels, so speed and ability to quickly reskill people will be an important differentiators going forward.
Low code automation platforms address these challenges by providing visual approach to test automation and enabling colleagues with little to no knowledge in programming to create automations
During the session we will discuss how do we transform the current approach of using traditional programming based automation to visual models of automation.
Faster time to market is extremely important for businesses now. However, it’s not just the to market or the quality of the product that is in question.
The points to ponder include:
5. Disaster recovery and Emergency Response
6. Change Management
7. Capacity planning
While all of these are key elements of engineering tied to development and operations, close observation tells you that there is a lot of testing involved in all of this. What makes it even more interesting is with more and more businesses moving away from monolithic architecture to a more microservices architecture model site reliability is transforming to service relieability which means that testing has a much bigger role to play.
The key takeaways of this talk look at the aspects of testing relevant to SRE.
Elliot Pittam, Field CTO – APAC, Everbridge
Organizations are becoming mired in DevOps transformations that are stuck in a middle ground according to the latest Puppet State of DevOps Report (2021). Value Stream Management aims to kick these organizations on by applying the necessary cultural and lean changes required, and by applying the principles directly to ITSM, we can add new efficiencies to team workflows and incident resolution. This session will demonstrate why applying Value Stream Management to Incident Management is as important as its application to Software Delivery and how that can be achieved through a Digital Operations Platform.
In the past year we switched from Selenium to Playwright (for web UI automated testing) and from Jmeter to K6 Load (for Load/Stress testing).
The switch was necessitated by the fact that both tools are more DevOps friendly.
In this presentation I’d like to address some of the challenges we faced on our way.
Victoria Alexiou, Product Manager, Peoplecert, Intl.
More and more organizations are adopting DevOps, where 76% of them are either already working on their transformation initiative or are in the planning stage. However, not all organizations manage to realize the same benefits as Amazon and Spotify do.
To successfully implement DevOps, one needs to take care of the entire DevOps Full Stack, i.e., Culture, Practices and Automation. Our experience shows, that in regions and industries where the notion of DevOps has not matured enough, organizations tend to overfocus their efforts towards tooling and neglect the components of Culture and Practices, thus they are not getting the results they aim for.
During our session we will discuss what DevOps Culture is, its importance and urgency, which tools exist and their uses, the common mistakes and pitfalls organizations tend to fall in and how we can convert this modern fairytale into a “and they lived happily ever after” story.
From its beginning, Agilists advocated for self-organizing teams. But more recent thinking is focused on leadership. Which is it? Are these approaches complementary or mutually exclusive? A matter of degree? Or is it complicated? We will connect the dots!
Alex Pestchanker, Innovation and Digital Products Lead, Tesacom
Businesses are being disrupted by the Exponential Transformation the advancement of technology is generating. This situation generates lots of stress for design and building teams. Just adopting scrum or safe is not enough, a combination DevOps, Organizational Agilism and Lean thinking is needed to be able to create Exponential Products.
Vivek Pandey, Senior Vice President – DevOps, Citibank
First DevOps and now recently DevSecops have revolutionized the development organizations, but while teams are still trying to get better at adoption of it, big dilemma is What steps must really be part of CICD pipeline , which steps among static code analysis, unit testing, security testing, performance testing etc…must be part of pipeline for development environment vs certification environment vs delivering a hotfix.
* “My product has a 80% code coverage but there are many defects that escape to production”
* “Our developers do not push code without writing tests but still our quality is bad.”
* “How can we be sure that we are writing good tests?”
If you see yourself in the above scenarios and are looking for a way to improve your product’s quality, this session is for you.
In this session, we will share how we stumbled upon mutation testing as a way to check the quality of our test cases. This quick report will start with the problem statement, i.e., how to test our tests. Then, we will explain our experience with implementing mutation testing and the results it gave us.
Erfana Sikder, Engineering Manager, Rokt
With bigger organizations and complex products, if you want your QA team to scale up, you will hit a bottleneck very fast. Rather I believe having the right people doing the right job is the key to success. The people who feel passionate about testing and quality could help build the perfect network of tests in the big organizations by paving the best path possible for the development team and can make the dream of perfect CI/CD a reality.
Site Reliability Engineering (SRE) is often talked about as the next logical step for a performance tester/engineer, but is that really the case? In this session I will share my journey from PE to SRE including how the two roles differ, and what you need to prepare.
There are tools, processes and people to make true agile transformation. But the real challenge is to place these aspects appropriately. In this talk, We will go through some practical examples of how we can customize and optimize these components effectively.