Many companies in today's VUCA world are planning to bring enterprise agility. While many frameworks are available in market, what is missing is the mindset, culture and organizational design that is needed to bring enterprise agility. It also demands coordination across entire value chain and various business process that are part of, or impact the software development life cycle. This session will focus on larger context of enterprise agility and what is needed to bring life to agile enterprises.

 
 

Outline/Structure of the Talk

This will be interactive presentation of 45 mins focused on :

  • What is enterprise agility, business context
  • understanding how value flow in the organization and which part of the organization is not agile. Theory of constraints.
  • importance of making business processes agile - e.g. sales, procurement, HR, finance, IT support etc.
  • organization designs and structures needed to support enterprise agility
  • importance of lean and agile mindset at enterprise level.
  • Roadmap to enterprise/business agility

Learning Outcome

Key takeaways for participants would be:

  • getting larger picture of what is enterprise agility
  • using value streams and lean thinking to understand how value flows
  • how to bring agility into business processes
  • rethinking organizational design and structure to support enterprise agility

Target Audience

Managers, enterprise agile coaches, change agents, senior and middle management, anyone who is interested in enterprise agility.

Prerequisites for Attendees

Basic knowledge or experience about agile is desirable.

schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker
  • Shane Hastie
    By Shane Hastie  ~  11 months ago
    reply Reply

    This looks like an interesting talk, I am concerned that there is too much content for a 45 minute session.  How can you trim it down and ensure the most important aspects are covered with enough depth?

    • Nilesh Kulkarni
      By Nilesh Kulkarni  ~  11 months ago
      reply Reply

      Hi Shane,

      Thank you for your time in reviewing the proposal. I did a dry run of this session couple of times and from content perspective, I was able to fit it in 45 mins. However, I am still planning to make it more lightweight, reduce slides and trim down the content on slides.  


  • Liked Rashina Hoda
    keyboard_arrow_down

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

    45 Mins
    Talk
    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 Vishal Prasad
    keyboard_arrow_down

    Vishal Prasad - SLICE - The Experimentation Mindset

    Vishal Prasad
    Vishal Prasad
    Lead Consultant
    Thoughtworks
    schedule 1 year ago
    Sold Out!
    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.

  • Naresh Jain
    Naresh Jain
    Founder
    XNSIO
    schedule 11 months ago
    Sold Out!
    45 Mins
    Case Study
    Intermediate

    Looking to move to Continuous Delivery? Worried about the quality of your the code? Helping your developers understand clean-code practices and getting the right testing strategy in place can take a while. What should you do to control the quality of the incoming code till then? This talk shares our experience of using PRRiskAdvisor to gradually educate and influence developers to write better code and also help the code reviewer to be more effective at their reviews.

    Every time a developer raises a pull-request, PRRiskAdvisor analyzes the files that were changed and publishes a report on the pull request itself with the overall risk associated with this pull request and also risk associated with each file. It also runs static code analysis using SonarQube and publishes the configured violations as comments on the pull request. This way the reviewer just has to look at the pull request to get a decent idea of what it means to review this pull request. If there are too many violations, then PRRiskAdvisor can also automatically reject the pull request.

    By doing this, we saw our developers starting paying more attention to clean code practices and hence the overall quality of the incoming code improved, while we worked on putting the right engineering practices and testing strategy in place.

  • Liked Shane Hastie
    keyboard_arrow_down

    Shane Hastie - Deliberately Designing Culture for Collaboration

    90 Mins
    Workshop
    Advanced

    Collaborative organisational culture doesn't just happen, it needs conscious and deliberate design and careful nurturing. In this workshop participants will explore what a collaborative organisation culture is, why it matters and how to deliberately design culture.

    Culture is "the way we do things here" rather than anything written or prescribed, so understanding how leadership attitudes and behaviors influence and create organisation culture is vitally important to successfully establishing an environment where people are able to bring their whole selves to work, are engaged and positively contribute to the organisation's success.

    This session is presented as series of facilitated conversations drawing out the key aspects of organisation culture and showing how it is influenced by a wide variety of factors including structure, geography, promotion policies and practices, the conversations leaders have, what gets rewarded, ignored or punished, relationships and friendships and a wide variety of other factors.

  • Liked Vered Netzer
    keyboard_arrow_down

    Vered Netzer - agile Leadership - why the army is the most agile organisation I've ever been in

    Vered Netzer
    Vered Netzer
    Transformation Leader
    Thoughtworks
    schedule 11 months ago
    Sold Out!
    20 Mins
    Talk
    Executive

    It is time to talk about ‘agile Leadership’.

    Reflecting on 7 years of experience in the Israeli army I’ll be sharing stories and insights about how the army REALLY operates.

    The army is not as ‘Command & Control’ as people commonly expects – it is much more empowering and agile than you’d think.

    At the army, I’ve learnt the true meaning of cross functional teams, the importance of reflection, feedback, creative problem solving, trust, teamwork, conflict resolution, resilience & responding to change.

    This talk will be intertwined with army (and civilian) war stories & tips for leaders in an agile world. This talk aims to inspire a new wave of Agile Leaders, through sharing examples of effective leadership, it draws on real, lived experiences and concepts (directly from the ‘horse mouth’) as well as useful takeaways that attendees can take back and apply to their work.

  • Liked Prasad
    keyboard_arrow_down

    Prasad - Remaining innovative - struggle story of a growing start-up

    Prasad
    Prasad
    Prasad
    HolleyHolland
    schedule 11 months ago
    Sold Out!
    45 Mins
    Case Study
    Beginner

    Being a start-up we are discovering new business models and experimenting new client behaviour. Our platform is a B2B insurance digital platform which redefines customer experiences of an Insurance retailer / broker. Having 7 paying customers, now all of us are spending time with client on boarding and removing blockers related to legal, contracts and procurements process. We thought we are smart in having a separate team to focus on new discovery / new ideas so that our creative juices keep flowing in the midst of all the chaos of client on- boarding etc.. but this turned us into dysfunctional discovery - delivery teams, we started becoming silo organisations one focusing on discovery and other focusing on delivery.

    This case study is about how we experimented a dual track model to regain our agility in experimentation and discovery.

  • 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 Vishal Prasad
    keyboard_arrow_down

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

    Vishal Prasad
    Vishal Prasad
    Lead Consultant
    Thoughtworks
    schedule 1 year ago
    Sold Out!
    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 Ravishankar
    keyboard_arrow_down

    Ravishankar - The 'Cannot' Syndrome and the Art of the Possible

    45 Mins
    Talk
    Intermediate

    ******** I submitted this proposal under the Agile Mindset track and after review Tathagat opined that this could be more relevant under the DevOps track advised me to submit this under DevOps track *******

    Enterprise Agility is about collaboration and willingness to embrace risk, learn, improve and move forward. Transformation to Agility requires multi-dimensional changes and these changes are driven by people with the right mind set across the organization.

    Typically in the early stages of a transformation people tend to be skeptical and demonstrate the 'cannot' syndrome - this cannot happen, we cannot do this and this is not the right way and so on. However leaders with positive approach and the right balance of aggression and patience can take along the onlookers and the skeptics and successfully transform towards enterprise wide Agile practices - not only in IT but also in the Business and Support functions.

    My presentation identifies the 'Cannot' syndrome towards Agile and DevOps related transformation at the hierarchical layers of an organization and explores the 'Art of the Possible' to transition people to a 'We can and will do it' journey.

  • Liked Zaheerabbas Contractor
    keyboard_arrow_down

    Zaheerabbas Contractor / Pradeep Kellangere - Transformation Hiccups - Emphasis on Technology or Alignment to Business Objective or Vice-Versa?

    45 Mins
    Case Study
    Intermediate

    Today Industry across various organizations is on a journey towards multiple transformation initiatives with the core aspect of bringing Business Agility to their existing construct. As they embark on the journey of transformation initiatives unfortunately each initiative operates in siloes due to reasons across limited Perspective, Partial Collaboration and Inefficient Execution approach.

    The Organization Culture and hence the Mindset restricts their thoughts towards being able to transform across areas of Overall Strategy, Customer Experience, Products (& Services), People, Organization and Technology. What is the intrinsic motivation behind driving towards this huge initiative and the desire to adopting to change.

    Through this session we intend to share the characteristics of a business transformation and the mindset change required to work towards the various transformation initiatives which potentially cuts across;

    1. Agile Transformation :

    • Ingrain the concept of “think small” – thinking away from monolithic and breaking smaller towards microservices adoption

    2. Business Process Re-engineering

    • Incubate “Build and own concept” with federated business objectives focused towards business process improvement and outcome based approach

    3. Engineering Transformation

    • Achieve Predictability ingrained while building system – Anticipate the system of failure
    • Reliability Incubate – Resilient and Fault tolerant system
    • Quality – Defect reduction across life cycle using Automation

    4. Workforce Transformation

    • Cadre building focused towards Engineering skills
    • Utilizing the concept of “Core” and “innersourced” team to leverage Critical skills across the board.

    5. Technology transformation - Open Source and Cloud Adoption etc

    • Time to market by creating pipeline in matter of minutes
    • Pattern Implementation (Immutable Infrastructure, Blue-green deployment, Canary release)
    • Executable across multiple platforms and Teams. Infrastructure(Cloud) Agnostic

    6. Improving Operational Efficiency.

    • Cost Effective - Effective utilization of development and operational teams
    • Being able to groom stories into buckets allowing to distribute across "Core" and "Innersourced" teams hence allowing flexibility of operating model,
    • Speed – Improving processes and playbook adoption
  • Liked Fennande van der Meulen
    keyboard_arrow_down

    Fennande van der Meulen / Maartje Wolff - Making performance reviews most effective: play the card game for the best conversation

    90 Mins
    Workshop
    Beginner

    Being effective, efficient and happy is a challenge. We all want to bring our best to work, but how do we thrive at work? Science shows that the way teams work together and management have a huge influence on our performance. Talking about happiness at work is for some people a difficult task. It might be awkward, too personal, or just odd. But knowing what makes you happy at work is extremely important if we want to work in flow and get the best out of our team. The card game Talking about Happiness at work, give you just the right tool to do this. This game can help you to enhance happiness levels within your team, skip the usual boring performance reviews and helps to thrive at work.

  • Liked George Ukkuru
    keyboard_arrow_down

    George Ukkuru - Continuous Quality Monitoring

    George Ukkuru
    George Ukkuru
    Head of Testing
    UST Global
    schedule 1 year ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Continuously monitoring of application quality in production with a purpose of continuous improvement and reduce production support cost. The approach is to collect the data from sources such as social media, app store, and production ticketing solutions. The objective is to analyze the data to provide insights into key quality parameters such as functional performance, security, and usability. The approach helps to holistic view of the application and helps in providing alerts to the development and test teams proactively.