filter_list help_outline
  • Liked Rashina Hoda
    keyboard_arrow_down

    Rashina Hoda - Becoming Agile vs Doing Agile (Research Keynote)

    45 Mins
    Keynote
    Beginner

    After 20 years since the manifesto, the latest state of agile reports more than 80% of organizations as "still maturing" in their agile practice. As agile methods expand beyond small teams and software itself, we are still struggling to answer these questions:

    • Why is it that some teams are more 'agile' than others even though they all claim to be practicing agile methods?
    • What all dimensions need to change as teams, managers, and entire organizations attempt to become agile?
    • How do these dimensions interact with each other?
    • Overall, what does it take to become agile and how does that differ from doing agile?

    This talk is based on my original theory of becoming agile developed from 10+ years of industrial research of agile practice in New Zealand and India, which received the distinguished paper award at the IEEE/ACM international conference on software engineering (ICSE), in 2017.

    In this session, I will explain the key dimensions that need to transition during agile transformations, using industrial examples, and highlight what you can do to progress beyond simply doing agile, to harness the most from your agile transformations.

    This keynote will add a unique research perspective to the conference program, sharing agile research in an industry-friendly format and delivery style.

  • Liked Arijit Sarbagna
    keyboard_arrow_down

    Arijit Sarbagna - Future of Agile: Digility 2020

    45 Mins
    Keynote
    Advanced

    Are you directly/indirectly involved with Agile software delivery? If yes, you may have already started questioning yourself “what next”? We have seen the evolution of Agile software delivery over years. Kent Beck took best practices to extreme levels way back in the nineties. We saw Agile Manifesto for Software Development coming out in 2001 and Scrum gaining popularity. And gradually organizations realizing that simple Scrum (or pure Scrum) may not work for large scale deliveries - leading to formation of multiple competing Agile Delivery Frameworks like SAFe (Scaled Agile Framework), Nexus, LeSS (Large Scale Scrum) and many others.

    But as we get uprooted by the wave of Digital Transformation - what is in store for us in the near future? Does Agile stand a chance to exist (or co-exist) as is? Or will it need to run through a sea change to survive?

    We explore the future of Agile (for software development) in this talk and see the possible change that we may expect to see in the next couple of years.

  • Liked Ramadevi Lakshmanan
    keyboard_arrow_down

    Ramadevi Lakshmanan - How to accelerate 'Mindset Shift' through 'Conscious Coaching' style?

    45 Mins
    Keynote
    Advanced

    The experiments with People and Projects so far clearly articulates that the Agile Maturity is not about the process or engineering practices but behaviours.

    Agile way of working can be made sustainable only by putting the values and principles into the regular practices.

    Hence there is a need for a structured model to cultivate the Agile Mindset across the Organisation through a slow, but steady pace on the right track.

    The Agile coaches to apply 'Conscious Coaching' style to empathise and empower the Teams by positioning 'Mindset' as the driving factor for Agility or Agile Maturity.

    'Agile Mindset Ladder' can be fully leveraged to accelerate the 'Agility'. https://www.slideshare.net/RamadeviLakshmanan/agile-mindset-ladder?qid=53957436-81a6-45bc-978c-e6a41f7db810&v=&b=&from_search=1

  • Liked Jen Krieger
    keyboard_arrow_down

    Jen Krieger - A Culture of Openness

    Jen Krieger
    Jen Krieger
    Chief Agile Architect
    Red Hat
    schedule 5 days ago
    Sold Out!
    45 Mins
    Keynote
    Beginner

    The “Agile mindset” was introduced to the software development community in 2001 in an attempt to foster freedom in the way that we work together. Its intent was to encourage organizational change that focused on people, collaboration and culture.

    But words on a screen don’t mean much in practice, especially if the people using them don’t - or won’t- understand their intent. How can individuals, teams and companies learn to correct these mistakes and break free from the challenges associated with change?

    Jen will share practical advice on effective Project Management, Agile Transformation, and getting things done– all told through the stories of her own journey towards something better at Red Hat.

  • Liked Alex Sloley
    keyboard_arrow_down

    Alex Sloley - The End is Nigh! Signs of Transformation Apocalypse

    45 Mins
    Talk
    Advanced

    How can an Agile Coach figure out when an Agile “Transformation” is going wrong? Are there signs that they might see, heed, and take action upon? Of course, there are!

    Hindsight is 20/20, but in the moment, these warning signs can be hard to see. Let’s explore some of the more common, and frightening, warning signs that your Agile “Transformation” might be exhibiting. We will discuss transformation provider types, frameworks, keywords, and other anti-patterns that might be signs that THE END IS NIGH.

    This session will review common themes and help familiarize you with the warning signs. Armed with this new knowledge, you will be able to plan as appropriate, to help navigate your organization through potential impending doom.

  • Liked Alex Sloley
    keyboard_arrow_down

    Alex Sloley - The Product Owner and Scrum Master Brain Transplant! Mwuhahahaha!!!

    45 Mins
    Talk
    Intermediate

    Imagine you are a Mad Agile Scientist and have a diabolical experiment to conduct - what would happen if you exchanged the brains of a Product Owner and Scrum Master? Mwuhahahaha!!! How would the body of a Product Owner with the brain of a Scrum Master act? And vice versa?

    Perhaps the Scrum Master would now treat the team like a backlog? This Scrum Master would be focused on value and maintaining a coaching backlog of team and person improvements. This Scrum Master is refining the team, crafting a group that delivers value.

    And perhaps the Product Owner might treat the backlog like a team? Rather than backlog refining, they coach the backlog. They would be focused on nurturing, protecting, and empowering the backlog. The backlog might transform from an irritation into a labor of love.

    Although this experiment sounds terrible, this change of perspective might be what you need to reanimate your dead team or backlog.

    Join the fun and come learn what horrifying results await!

  • Liked Alex Sloley
    keyboard_arrow_down

    Alex Sloley - Liberating Structures... 36 tried and true facilitation techniques to amp up your org's collaboration

    90 Mins
    Workshop
    Beginner

    The communication tools of Liberating Structures will teach you how to facilitate the discussions your org needs. I am going to demonstrate how to use these techniques in the workshop. And all the attendees are going to be fully immersed and ready to wield their new knowledge the very next day at work.

    Come learn how to help your team(s), org(s), and company(ies)!!!

    For more information, watch my video at http://youtu.be/UNOjqMUv8h0

    A version of this workshop that was presented at Agile Tour Sydney 2016 is at http://bit.ly/2f4Bie8

  • Liked Vivek Ganesan
    keyboard_arrow_down

    Vivek Ganesan / Rejikrishnan Rajan - Reinventing DevOps Practices for Blockchain Applications

    90 Mins
    Workshop
    Intermediate

    With the arrival of distributed applications that run on Blockchain, it is essential to rethink some of the basic aspects of DevOps. Few things that we take for granted in DevOps area are either irrelevant, impossible or too costly for blockchain applications. This session aims to explore the changes that the blockchain apps bring to the DevOps arena, using a hands-on demo of a sample blockchain app.

  • Liked Jutta Eckstein
    keyboard_arrow_down

    Jutta Eckstein - CD – Continuous Delivery and Cultural Difference

    20 Mins
    Talk
    Intermediate

    DevOps and continuous delivery is typically elaborated technically - what kind of tools, technologies, or skills are necessary for being able to deliver continuously. Often it is forgotten that continuous delivery requires also a culture change - in development, operations, marketing, sales, and not least for the customer.

    This can be recognized for example, that although it is technically possible for a team to deliver continuously, but it seems that this delivery isn't welcomed. This means the actual system will not be directly used.

    Therefore, in this session by taking into account the necessary cultural change, I want to answer the question how to implement continuous delivery successfully and what kind of pitfalls you need to be aware of when doing so.

  • Liked David Laribee
    keyboard_arrow_down

    David Laribee - An Evolutionary Approach to Managing Software Entropy

    David Laribee
    David Laribee
    CEO
    Nerd/Noir LLC
    schedule 4 days ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    As an industry, we’re not very good at managing tech debt. Yesterday's big balls of mud will likely to become tomorrow’s big buckets of glue. Wouldn’t it be great if we could:

    • Balance and evolve quality while delivering features?
    • Pinpoint hotspots in code? At multiple levels of detail?
    • Heighten situational awareness of system health and hygiene?
    • Conduct data-driven, constructive critiques within our team?
    • Automate (useful) measurement, putting quality gates in place to self-govern as a team?

    In this talk, I’ll share my lightweight approach and toolchain for realizing these aspirations. Expect lots of tips and tricks for combating entropy in long-lived, software-intensive products shared by teams and large organizations. Some of these tools can be a little daunting for beginners, so I’ll take a demo-driven approach sharing the cheat codes I use to get to value as quickly as possible.

    Ultimately, I'll show you how to start building a system for visualizing, prioritizing, and managing your software product's evolution and technical debt side by side with new feature development.

  • Liked Vishal Prasad
    keyboard_arrow_down

    Vishal Prasad - A "Quality" Debate - Rethinking the mindset for non-negotiable Quality in Software Products

    45 Mins
    Talk
    Intermediate

    One of the key reasons for embracing agility is faster feedback which helps improve the perceived quality of a software product. And every team is focused towards delivering quality, no one wakes up in the morning with an idea to introduce defects, we naturally ideate to solve problems. Unknowingly though, dysfunctions always creep in and identifying a dysfunction is extremely difficult especially when you are a part of the dysfunction.

    In this 45 min talk, I discuss about the importance of quality and how it's no longer negotiable even if Project Management principles tell us otherwise. I share stories from my past experience, and from organisations ranging from GM to Mumbai Dabbawalas that have embraced the "Quality is not Negotiable" principle and seen the difference.

    I present the context of defect severity and how these may create an illusion of quality; how accountability of a single person (e.g.: Product Owner) may result in a "Lack of Commitment" dysfunction; and how cost is not really proportional to quality especially when it comes to delivering virtual products and services related to it.

    I end the talk with practices that help build in quality and in the interest of an interactive session, many of these scenarios turn out to be debates since the context may differ; these debates are always good ways to solve problems (moving away from "Fear of Conflict").

    This talk is based on my article titled The Entropic Future of Software Quality

  • Liked Vishal Prasad
    keyboard_arrow_down

    Vishal Prasad - SLICE - The Experimentation Mindset

    20 Mins
    Talk
    Intermediate

    Agile Principle # 12 defines that at regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly. From Scrum to Kanban and other agile frameworks, this is accomplished through retrospectives and continuous improvement processes. The key to being a successful agile practitioner is to identify areas of improvement and then experiment ways of improving it. But it doesn't stop there; positive improvements ultimately become success stories for other teams and motivates them to experiment with newer ideas which eventually leads to innovation. A negative outcome isn't bad either since it adds to the experience of situations where ideas may not apply. Thus the key to this process lies in being a child, an explorer, and inculcate an experimentation mindset. The SLICE framework addresses this in the following way:

    • S hare: Share an area of improvement
    • L earn: Explore the area for ways of improvement
    • I mplement: Search & apply the learning to identify the success factors
    • C ollateral: Publish blogs, white papers, presentations, etc. as observations of the implementation
    • E xpansion: Grow, Seed, and Split in order to explore new venues for success

    In this talk, I create an environment that inculcates an experimentation mindset and utilise the SLICE framework to drive the exploration.

  • Liked Pradeep Chankarachan
    keyboard_arrow_down

    Pradeep Chankarachan - Agility in the Driver's Seat - Re-inventing the wheel of future

    45 Mins
    Case Study
    Intermediate

    Automotive industry is in the cusp of it's biggest transformation, Digital transformation in this industry is twice the speed of average adoption rates across technology areas. As the cars of future would be tagged as Autonomous, Connected, Shared and Electric, the change in parts of the car (BoMs), ecosystem(Charging , shared data, safety) software engineering platforms (Car Operating System), external connectivity(5G) and Sytem on Chip needs will bring the digital the key pillar . This would be the epitome of Agility at the center and will establish new standards for a personalized, digital driven connected world under a reliable and secure delivery platform for automotive. The outset of the session is sharing ways to bring the external disruptive collaboration perspective within the organization walls.This session is about sharing my experience of my journey of re-positioning IT for Digital and disruptive automotive industry, re-structuring the organization keeping agility in mind, successful implementation reference like cloud transformation for engineering, nurturing teams to embrace the change.

  • Liked Rucha Ramchandra Kapare
    keyboard_arrow_down

    Rucha Ramchandra Kapare - Embracing Performance Kaizen

    45 Mins
    Case Study
    Intermediate

    Every organisation hopes / expects / demands high performance from their employees and teams. It's not very long ago when most effective organisations in the world had a ritual called yearly goal - setting. Many organisations still continue with this where the HR cascades a set of goals set by the organisation's leaders for their employees. This is usually followed by a quarterly to yearly review cycle which with most organisations are linked with incentives. In general terms, there ain't any flaw with this system; goal setting is an efficient way to continuously improve oneself. However, the execution of this process may be flawed and may lead to unoptimized results.

    With the advent of business agility, this focus shifted towards continuously learning & improving organisations. This meant that faster feedback was highly recommended for performance improvement and the idea of year-long goal setting seemed a talk of the yesteryears. Many organisations embraced this change by completely abolishing the yearly goal setting practice and instead relying on mentor relationships for an individual's performance improvement. This did improve relationships at the same time hindered transparency since the organisation goals were no longer directly accessed by every employee.

    When seen from the perspective of game theory, it's evident that optimum results are obtained when employees achieve goals which are highly beneficial to them at the same time aligned with the organisation's goals. With the former approach explained above, it's pretty clear that the employees in the first case were aware of the organisation's goals, even if the goals were not aligned with their personal goals. Whereas in the latter case, the lack of transparency meant that the individual's goals were highly focused and may not be in-line with the organisation's objectives.

    This is where Performance Kaizen aligns these two systems with a flavour of Management 3.0 in order to create an optimum setup where high performing individuals, teams, and organisations can thrive. In this session, we present a case study of this implementation at Springer Nature along with our results and learnings; followed by a brief hands-on exercise for the attendees.

  • Liked Vivek Ganesan
    keyboard_arrow_down

    Vivek Ganesan - Happiness at Work - Does Business Agility Lead to Happy Workplaces?

    45 Mins
    Talk
    Beginner

    Have you ever wondered about the meaning of 'Happiness at Work'? Does everyone define them the same way? If not, how can an executive work towards improving the happiness of his employees? If you have these questions, this session is for you.

    With the increase in population that separates ‘work’ from ‘life’, as if work is the absence of life, it becomes increasingly important to study about what happiness means to people at work so that they can be made to feel alive in their offices too.

    This session is aimed at introducing two interesting research studies that aimed to do just that. Also, this session helps people understand if Business Agility keeps us happy in the true sense.

    The two studies that this session will discuss are as follows:

    1. Richard M. Ryan et al’s Self Determination Theory – led to a book Drive by Dan Pink
    2. Mihaly’s Measurement of Flow in Everyday’s life – led to book Flow by Mihaly himself

    This session does not just explain these two research works but also will find the commonalities between these and will engage the audience with discussions using scenario-based questions, thereby bringing out personal examples that they can relate to.

  • Liked Rakesh Kondreddy
    keyboard_arrow_down

    Rakesh Kondreddy - Inclusive Design - Manual & Automated Accessibility Testing Implementation

    45 Mins
    Demonstration
    Beginner

    When websites are designed, developed all users have equal access to information& functionality. QA& Dev needs to make sure web & mobile should be accessible to all users including differently abled or having special needs, abide by legislation (WCAG, section 508, ADA) and avoid lawsuits. QA needs to make the strategy using Manual review, Accessibility toolbars, Online evaluation tools, Assistive technology and Realistic end-user testing (visually challenged) and bring automation using Protractor, Selenium, HTML code sniffer/AXE to make developers and stakeholders aware on product accessibility compliance.

    I would like to mainly concentrate on 4 principles (POUR - perceivable, operable, understandable, Readable) and 12 guidelines of Text alternatives by providing alt attributes, Time based media by proving captions, Adaptable by all assistive technologies like screen readers/magnifiers, Distinguishable, Keyboard accessible, Enough Time for seeing especially for people having dyslexia, Navigate to all pages by providing appropriate headers sizes and accessible links, Readable by providing ARIA labels and roles, predictable and input assistance by providing error messages with efficient colour contrast, Compatible with all browser versions and make responsive web design suits tablets, mobile and Desktop

    QA should gain expertise by going through 30- day accessibility testing and adopt across the organization by having key stakeholders, checklist and benchmark levels of WCAG (A, AA, AAA). Establish UI standards, color contrast across teams. Inspire team by making accessibility is right to use

    This paper describes manual testing by reviewing HTML code and automated Accessibility techniques using evaluation tools like Voice over, AXE, HTML code sniffer, WAVE, A checker, W3c Mobile ok analyser, color contrast analyser useful for developers and QA within their automated scripts

    Demonstration of Manual and Automated Accessibility tools/libraries/ utility checks and reports generated with accessibility violations of all pages in a website

  • Liked Nitin Mittal
    keyboard_arrow_down

    Nitin Mittal - Bringing in Mindset and Cultural change – How to do it?

    45 Mins
    Talk
    Advanced

    Mindset and Culture change is at the core of agile and DevOps adoption. While we all know it’s importance, there is no single approach or process to make this change happen.

    In my session I will cover pragmatic approach of bringing in mindset and culture change. An approach which we are adopting in our workplace and seeing the change resulting in multi-fold benefits. You will leave the session with multiple ideas and an insights on how to make cultural and mindset shift in your organization

  • Liked Shane Hastie
    keyboard_arrow_down

    Shane Hastie - Being Agile in a Remote Team

    90 Mins
    Workshop
    Intermediate

    In this interactive session Shane discuss his experience working in a distributed, virtual organization which is founded on an Agile Mindset. The challenges of maintaining agility when remote, the ways the ICAgile team have consciously designed their team and organization culture and provide actionable advice based on real experience on how to maintain collaboration, teamwork and live the agile values in a remote only organization.

    ICAgile is a global, virtual organisation working with partners across over 100 countries spanning almost every timezone. There is no single corporate office and the ICAgile team is spread across seven locations in three countries. We have managed to build a strong collaborative culture and a truly safe working environment focused on outcomes rather than activities, holding each other to account and being really effective and productive while having a joyful workplace.

  • Liked Jutta Eckstein
    keyboard_arrow_down

    Jutta Eckstein / John Buck - Using Beyond Budgeting and Sociocracy for agile-friendly performance appraisals

    90 Mins
    Workshop
    Intermediate

    There are many suggestions dealing with Agile-friendly performance appraisals, which promise to rely on trust, honesty, respect, safety, and servant leadership. The Agile Manifesto does not address performance appraisal although it does generally mention regular and frequent feedback, which can also be applied to performance evaluation. Two related methods that share the same values as Agile, Beyond Budgeting, and Sociocracy, have worked out interesting approaches to agile performance review. In this session we want to present these two different performance appraisal approaches and want to invite the participants of this workshop to discuss the strengths and drawback of both and the possible synthesis of the two approaches.

    Similar to the Agile Manifesto, Beyond Budgeting is founded on values and principles. Two of its twelve general principles focus on the topic of performance appraisals. Where the first principle asks to “engage and inspire people around bold and noble causes; not around short-term financial targets,” the eleventh principle advocates: “Evaluate performance holistically and with peer feedback for learning and development; not based on measurement only and not for rewards only.” Thus, the main strategy of Beyond Budgeting is to separate (financial) bonuses from performance evaluation and to use relative and not fixed targets as a foundation for the evaluation.

    Sociocracy suggests holding 360 degree in-person meetings. The person being reviewed should request it when needed, not just on a rigid annual basis, and perhaps not just once in the year. In the 360 degree meeting, the organization itself can be critiqued in the review - “the way we are organize is causing performance problems.” Similar to Beyond Budgeting there is a focus on the vision and mission of the specific department as well as the overall company as a source of inspiration and motivation. The output of the performance review meeting should be a development plan that the immediate group of supervision, peers, and subordinates consent to.

    The type of measure is important - should we look at feedforward (leading indicators) as well as at feedback (lagging indicators). Financial bonuses can be set up - a lagging indicator. Sociocracy says consider the group performance when giving bonuses but you can also consider individual performance within that context.


    In this session we will summarize Beyond Budgeting and Sociocracy for the participants and then invite them to explore with us different strategies for synthesizing. Participants will take away insights that they can use in their organizations.

  • Liked Jutta Eckstein
    keyboard_arrow_down

    Jutta Eckstein / John Buck - Learning Fast & Small - Nourishing Company-wide Agility in a Skeptical Environment

    240 Mins
    Workshop
    Intermediate

    Agile beyond IT and beyond just doing it, but rather being it requires experimenting continuously in order to learn continuously. Thus more important than failing fast is learning fast.

    In this workshop we will learn what learning fast means for every individual and the organization as a whole and we will define experiments for you to use in your company for becoming agile truly. This will allow you to create an environment for continuous innovations.

    In this workshop we will also make use of examples that make:

    • the organizational structure (hierarchy?) more agile
    • the organizational processes faster so that they enable innovation
    • the organizational strategy better aligned with current needs so that your organization is able to drive the market instead of being driven by the market