Think Like an Agilist: Deliberate practice for Agile culture

If I say, culture is important to adopting Agile, most people will just agree without even thinking too much about it.  But what is meant by "culture"?  Why is it important?

Culture is not typical behaviour; it is not what we say we value (but don't actually do).  Culture is our basic assumptions of how things work.  Culture is the logic we use to think through and respond to any particular situation.

If you imagine a pyramid, Agile practice and any other visible behaviour is on the top, stated or written Agile values and principles are in the middle, fundamental assumptions (aka culture) is at the base.

My session is intended to expose people to the base of that pyramid.

If culture is assumptions, then to understand Agile culture, we need to understand the basic assumptions of Agile.  To do this, I have created an approach called "Think Like an Agilist" that both exposes how we think through an "Agile situation" and allows us to deliberately practice "Agile culture".

The general idea is that I won't just talk about Agile culture and values, what I'll call "culture theatre", but rather expose people, who nominally consider themselves part of the Agile culture, to their underlying thought processes and assumptions, given a relatively difficult scenario.  Those thought processes and assumptions are the essence of culture (reference Edgar H. Schein).  What is interesting is noting when the thought processes and assumptions are different which indicates that there is a different culture at play.  What I've noticed is that this difference is common between novice vs expert Agilists.

Note that it isn't even about analyzing vs doing it mechanically but more about exposing what assumptions are being used to respond.

NOTE: I will be updating the attached slides as when I created them, I was framing it more as "doctrine" rather than "culture", defined as fundamental assumptions"

 
 

Outline/structure of the Session

  1. Introductory presentation
  2. Think Like an Agilist scenario - small group practice session
  3. Debrief
  4. Repeat practice session / debrief
  5. Overall debrief

Learning Outcome

Clearer understanding of what is meant by "culture"

Clearer understanding of the basic assumptions underlying Agile

Awareness of an approach to expose and practice effective thought processes

Target Audience

Any

Requirements

Separate tables for up to 5 people.  Notepads and pens.

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Meghan Robinson
    By Meghan Robinson  ~  1 year ago
    reply Reply

    I’m intrigued by your articles regarding scrum and agile! I’m wondering if you would be willing to write a piece or give us permission to highlight an existing article on the new AgileCareers Blog. AgileCareers is powered by Scrum Alliance and is the only job board dedicated to connecting Scrum and Agile organizations with qualified, passionate Agile professionals.

     

    Click below to view the blog: http://membership.scrumalliance.org/blogpost/1322603/AgileCareers-News

     

    If you wish to discuss further, please email me at mrobinson@scrumalliance.org. I look forward to hearing from you!

     

    Thanks,

    Meghan

  • AgileSattva Consulting LLP
    By AgileSattva Consulting LLP  ~  1 year ago
    reply Reply

    Slide definitely made me thinking, I am coming to think if it would define "Culture" aspects. It feels to me more like "thinking at different situations" and the difference between analyzing the situation rather just do it mechanically.
    Could you help me understand the relation between the slides and the Agile culture ?

    • Jason Yip
      By Jason Yip  ~  3 years ago
      reply Reply

      Hello Deepak,

      I will be updating those slides as when I created them, I was framing it more as "doctrine" rather than "culture", defined as fundamental assumptions".  The general idea is that I won't just talk about Agile culture and values, what I'll call "culture theatre", but rather expose people, who nominally consider themselves part of the Agile culture, to their underlying thought processes and assumptions, given a relatively difficult scenario.  Those thought processes and assumptions are the essence of culture (reference Edgar H. Schein).  What is interesting is noting when the thought processes and assumptions are different which indicates that there is a different culture at play.  What I've noticed is that this difference is common between novice vs expert Agilists.

      Note that it isn't even about analyzing vs doing it mechanically but more about exposing what assumptions are being used to respond.

      • Doc Norton
        By Doc Norton  ~  3 years ago
        reply Reply

        Jason:

        Can you do me a favor and update your proposal details to incorporate some of the additional information you've provided in response to reviewer inquiries? While we can read through the thread of comments to gain the whole picture, the more we can garner from the write-up, the better.

        Thanks.

        - Doc
        (Agile Lifecycle Theme Chair)

  • Ellen Grove
    By Ellen Grove  ~  3 years ago
    reply Reply

    Hi Jason - I'm sorry I didn't have a chance to attend your workshop.  Thanks for making the slides available.  Good to meet you at Agile India!  

  • Joel Tosi
    By Joel Tosi  ~  3 years ago
    reply Reply

    Hi Jason,

       Would you be able to chat about this Monday or Wednesday this week?  Maybe skype or google hangout?  I have some questions I would like to go through with yout.

    Thanks.

    Joel

  • Joel Tosi
    By Joel Tosi  ~  3 years ago
    reply Reply

    Hi Jason,

      I am intrigued by your session but still struggling with the takeaways.  I want to make sure it isn't me / my beliefs.  I don't believe you create a culture, I believe a culture is a product of the system.  Does your session address culture as how to create an 'agile' culture, or is it about what an 'agile' culture is, etc.  Consider me simple ;)  Ground this very concrete for me.

    Best,

    Joel

  • Sachin goel
    By Sachin goel  ~  3 years ago
    reply Reply

    An interesting one, do you think this is more common than agile practices? Are there any co-relations of this with Agile pratices?

    • Jason Yip
      By Jason Yip  ~  3 years ago
      reply Reply

      Hello Sachin,

      Do you mean, will this approach work more generally than the Agile context?  If so, yes I believe it will, especially as it's derived from another context (i.e., Think Like a Commander).

      If you imagine a pyramid, Agile practice and any other visible behaviour is on the top, stated or written Agile values and principles are in the middle, fundamental assumptions (aka culture) is at the base.

      My session is intended to expose people to the base of that pyramid.


  • Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Advanced

    As the popularity of Agile methods have grown, so have the misconceptions or myths associated with Agile also grown. These myths get even more glorified when we talk about them in the offshore or distributed context. And to make matters worse, you can throw in a fixed-price contract spanner into the engine.

    Worry not! In this fun-filled activity, we'll collect facts from the participants that they believe are true and then we'll declare them as confirmed or busted after an interactive (heated) discussion.

  • Corey Haines
    Corey Haines
    schedule 3 years ago
    Sold Out!
    45 mins
    Tutorial
    Beginner

    Everyone has acronyms, mnemonics, and a list of rules to guide their everyday software design. In order to get the most out of these age-old gems, one needs to deliberately practices them. Rules are a good way to remind ourselves of these gems.

    Corey Haines emphasies his design guidelines in form of the "4 Rules of Simple Design." Attend this talk to understand the four rules and their importance in everyday programming.

  • Liked Corey Haines
    keyboard_arrow_down

    Stories from 10 Years of Extreme Programming

    Corey Haines
    Corey Haines
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    10 years ago I was introduced to Extreme Programming. Since then, I've been an avid practitioner, applying the techniques and values to my life as a software developer. Over that time, I've bounced between many extremes, learning and reflecting on the value that I get when building systems both for myself and for others.

    In this talk, I'll share some of those learnings and how my life as a software developer has changed with the times.

  • Dave Thomas
    Dave Thomas
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Advanced

    In 2002, Secretary of Defense Donald Rumsfeld introduced us to the concepts of known knowns, known unknowns, and unknown unknowns. But he left out Unknown Knowns, things that we know without knowing it. And it turns out that these Unknown Knowns are actually the biggest category of knowledge - tacit knowledge.


    As developers, we work with knowledge: knowledge of the problem domain, knowledge of our tools, knowledge of our techniques, and knowledge of each other. So getting good at accumulating tacit knowledge is important.

    This talk will look at how we are poorly served by most of the current ways we are taught to be better developers. Can we do better? Only if we stop talking and start showing. Let's see why.

  • Liked Ryan Martens
    keyboard_arrow_down

    Beyond Agile Execution: Agility for Business and Impact

    Ryan Martens
    Ryan Martens
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Beginner

    Agile is not just a process change, its a mindset change for most. With faster time to market, better feedback and highly functioning teams, the Agile mindset opens our eyes to a better way of working as humans on large complicated and complex problems. Combining it with the concepts of Lean Startup, delivers another leap in team capacity and capabilities. It also opens the possibilities of using agility for more than just software development.

    Do you wonder how can we drive innovation in a disciplined way to tame our world's toughest problems? Can we apply the lessons learned from Agile and Lean Startup? Over the past three years, we've been able to apply agility at a new level, beyond business impact. Through our corporate social responsibility effort, "Rally for Impact", we aim to apply the agile mindset to mobilize citizen engineers to serve our communities and protect the planet. I want you to consider this growth path for yourself and your agile teams.

    Let's open the worlds mindset to a better way to empathize, explore and execute in these complex times.

  • Martin Fowler
    Martin Fowler
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Intermediate

    In the last decade or so we've seen a number of new ideas added to the mix to help us effectively design our software. Patterns help us capture the solutions and rationale for using them. Refactoring allows us to alter the design of a system after the code is written. Agile methods, in particular Extreme Programming, give us a highly iterative and evolutionary approach which is particularly well suited to changing requirements and environments. Martin Fowler has been a leading voice in these techniques and will give a suite of short talks featuring various aspects about his recent thinking about how these and other developments affect our software development.

  • Liked Rae Abileah
    keyboard_arrow_down

    Engendering Justice: Women, War and Peace

    Rae Abileah
    Rae Abileah
    schedule 3 years ago
    Sold Out!
    45 mins
    Keynote
    Beginner

    One in three women will be raped or beaten in her lifetime. Half of the seven billion global population are women so that means one billion women alive now will, or have been, beaten or raped or beaten. Women and children are disproportionately affected by war and occupation as well. And yet numerous studies illustrate how uplifting women's work and leadership can strengthen the whole society and economy. Women are at the forefront of global campaigns challenging militarism and violence, and working to redirect resources into health care, education, green jobs and other life-affirming activities. What can we learn from these women and their successes thus far? How can the technology sector support this crucial work? How do these social movements stay agile to rapidly respond to breaking news while building a long-term progressive movements for deeper social, economic and environmental justice? As Arundhati Roy said, "Another world is not only possible, she is on her way. On a quiet day, I can hear her breathing." In this talk, Rae Abileah will share visionary examples of women-led work for peace and justice and explore the paradigm shift needed for equality, human rights, and justice for all.

  • Todd Little
    Todd Little
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Intermediate

    A major challenge in agile development is the ability of test teams to keep pace with ongoing development while simultaneously ensuring that new development has not created regression failures. This case study from Halliburton shows how together with two globally distributed outsourcing partners they developed a comprehensive test automation strategy for their agile teams that effectively leveraged both in house and outsourced activities. This approach resulted in a significant quality improvement from prior releases.

  • Ash Maurya
    Ash Maurya
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Intermediate

    Most products fail. Not because we fail to build what we set out to build, but because we waste time, money, and effort building the wrong product.

    In this talk, I'll share our lean product development process that utilizes continuous customer feedback loops to ensure you don't go astray and instead build products people (will) want.

    What you'll learn:

    - How to track your your feature lifecycle on a validated learning kanban board
    - How to use qualitative testing techniques for early validation during the design and test phases
    - And then follow up with cohort based quantitative metrics to verify you have built something people wanted.

  • Liked Tarang Baxi
    keyboard_arrow_down

    A Practical Guide to Setting up Distributed Agile Projects

    Tarang Baxi
    Tarang Baxi
    Chirag Doshi
    Chirag Doshi
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    A practical guide to setting up a new agile project team. Based on years of agile delivery and coaching experience for projects in a number of distributed and offshore models, for teams sized from 10 to 200 people, and spread across 4 continents, and 8+ locations. Some areas that will be touched on:

    • People - how to organize distributed teams, cultural factors to consider, ways to build trust, and how to avoid timezone burnout.
    • Process - how to communicate effectively, plan collaboratively, setup distributed practices (standups, retros, pairing, etc), effectively divide work on a common codebase, maintain visibility, and track progress.
    • Tools - (tips provided as a handout) which hardware and software tools should you absolutely invest in to help overcome communication,  visibility and collaboration challenges
  • Ravi Krishnan
    Ravi Krishnan
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Advanced

    Organizations which have diverse functional units and technology portfolios (BI, Mobile, Web Application development, Web Design etc) following different methods cannot make an overnight or a sudden transformation to following a mature model of Agile method.

    These teams need to come up with a structured approach towards Agile adoption and transformation enabling the different teams to make a gradual progression towards the adoption of Agile in their projects and teams.

    We at Aditi Technologies realized this and came up with a Aditi Agile Transformation Maturity Model which provides guidance to the different project teams and functional groups on the transformation journey within their engagement. The salient points of the Maturity model include:

    * Agile Project Planning and Management Maturity Model - Traditional teams are used to tradition planning methods plan around the typical 3 constraints of Scope, Cost and Time. A transformation to a model where emphasis is on delivering the highest priority items is arguably one of the more difficult lifecycle areas of the transformation. The Agile Project Planning and Management maturity model provides guidance to such teams on moving from a managed team services model to a self directed and self managing teams services model.

    * Collaboration Maturity Model - Moving from a SLA driven environment to a collaborative environment is again a massive cultural mindset change for the different teams. The collaboration maturity model at Aditi for Agile engagements provides a framework for teams to start collaborating better in a gradual manner. Starting with a well defined collaboration model within the Agile sprints between the QA and Development teams leading to an end to end collaborative lifecycle involving the different stakeholders is the overall approach we have adopted at Aditi to improve the Collaboration within the lifecycle in a phase wise manner.

    * Agile Requirements Engineering Maturity Model - The Aditi AREMM provides the business and product ownership teams with a gradual migration approach from the traditional Business Requirements Document based Requirements Management approach to an Agile approach towards the same incorporating basic principles like story card based requirements engineering to a more collaborative and leaner approach incorporating starting principles such as Product Backlog and Story Cards and moving to more advanced models such as executable specification models prescribed by BDD.

    * Engineering Maturity Model - While there are well prescribed best practices and models within the Engineering phase for Agile teams, adopting an all at once approach can be fraught with danger for the teams especially given the constraints of a global delivery model such as staffing pyramid (practitioners at different levels of capability including graduate hire resources), the Engineering maturity model provides teams with a prescriptive model around adoption starting with relatively basic principles like refactoring to adoption of more advanced practices like TDD, BDD etc.  

    * Metrics - Based on the level of the maturity of the Agile adoption, Aditi has come up with prescription around metrics the teams could adopt. These are classified into different buckets using the MoSCoW prioritization principles.

    * Tooling - Aditi has come up with a well prescribed guideline for Agile teams in the adoption of tools across the lifecycle (Ex: for Collaborative lifecycle management, Continuous Integration, Build management, Code quality management etc) and has come up with bootstrap assets which teams can leverage to run with when they start the transformation.

    * Organization readiness - For an organization to embrace Agile, many of the current internal practices (Recruitment, Sales etc) and current infrastructure (Ex: Collaboration platforms, infrastructure) needs to scale up as well. A well defined maturity model towards transformation allows organizations to adopt a more phase wise approach towards these areas of transformation and helps the different business units to also scale up at a sustainable pace.

  • Liked Mukesh Bhangria
    keyboard_arrow_down

    Continuous Refactoring at Amazon: A Case Study

    Mukesh Bhangria
    Mukesh Bhangria
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Between the project deadlines, we always feel there is code which needs to be improved

    Usually Developers have the following 3 options:

    - Bite the bullet and do the refactoring as they go along.
    - Park the issue and address it later.
    - Allocate special time when the project gets out-of-control.

    As customer facing stories take higher priority, usually Developers are forced to choose the last option.

    However a team at Amazon took a different approach. Attend this session to listen to their first-hand story of how they changed this typical behavior to achieve Continuous Deployment on a critical service.

  • Ram Srinivasan
    Ram Srinivasan
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    It is not a question of if a team is going to have a conflict; it is a question of when. Equipping them to deal with conflict is more than creating agreements or having a good facilitator. We look at a conflict model that focuses on dynamics of conflict by understanding- 1. Cognitive skills:self-awareness about triggers, hot spots, emotions,behaviors. 2. Emotional skills:reading emotions, body language, balancing emotions, using curiosity 3. Behavioral skills:understanding others’ perspectives and needs, avoiding 8 destructive behaviors, embracing 8 constructive behavior. In an organizational setting, it is important to understand the source (culture, interdependence, incompatibility, personality, power, etc.) and types of conflict (cognitive vs. affective). Creating awareness about conflict processes, retaliatory cycles and building a conflict profile can empower teams engage in constructive disagreements. 

  • Liked Joseph V
    keyboard_arrow_down

    Tale of an Off-shore Agile Scrum Implementation

    Joseph V
    Joseph V
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    Couple of years ago our business unit engaged a vendor in India  to do some software development for us.  Since we are agile scrum based organization, we are seeking a vendor who has exposure to agile. We identified and signed up with a vendor to start the process. It was a ride filled lot of excitement and challenges. Finally we are able to land safely.

  • Liked Pavel Dabrytski
    keyboard_arrow_down

    Agile Anti-Patterns in Distributed Teams

    Pavel Dabrytski
    Pavel Dabrytski
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Implementing Agile is hard. You know what is even harder? Implementing Agile across distributed offshore teams.
    Due to constrains we face in our daily communication and collaboration, it is always difficult to get rid of old waterfall thinking. Sometime waterfall way even feels easier. This is where we find most of Distributed Agile Anti-Patterns.
    Agile Anti-Pattern often looks like Agile, it follows the right mechanics, but it is missing essential Agile values and principles.
    Join me for an interactive session where you will learn about 10 Agile Anti-Patterns specific to outsource and offshore development, and the ways to address them.

    Some of my favourite Anti-Patterns are:
    * Retrospective via emails
    * Scrum Master across the sea
    * Stabilisation sprint (sprint for bug fixing)

  • Liked Victoria Schiffer
    keyboard_arrow_down

    Agile Coaching? Sure thing! What about Life Coaching in Agile Thinking?

    Victoria Schiffer
    Victoria Schiffer
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    I love being around awesome people, who build great products customers desire. 
    I love learning from and together with these amazing minds. 
    I love creating the right environment for teams to flourish. 
    I love change, and learning from new experiences. 
    I love working in Agile environments.

    How about you? 
    I bet there are some elements of this list why you're in Agile, too. And you can probably add even more elements to it.

    The Agile Manifesto states amongst others individuals and interactions, customer collaboration and responding to change.

    In our everyday life doing Agile we already respect these aspects in many ways. 
    But do we practice what we preach as best we can?

    I'd like to challenge your current way of thinking about people and processes. 
    I'd like to challenge you to focus on you, before you focus on others. 
    I'd like to challenge your current way of reflecting. 
    I'd like to inspire you to go different ways. 
    I'd like to inspire you to inspire others.

    In Agile we're already good in improving our processes and creating well performing teams and hence building the right things in the right way. And in the Agile Manifesto's communication and collaboration piece we can even get better.
    "You have not yet reached the limit of what you're capable of!" means we can always further improve. And we do follow this idea in our Agile processes, too, through continuous feedback (Retrospectives) and improvement.

    And why not take it even further? Why not go "Beyond Agile"?!

    Here's where aspects of Life Coaching come in handy: through also understanding and improving ourselves (how do we interact with people due to how we perceive our environment) we will even further improve communication and collaboration.

    Life Coaches believe our clients know the answer. And even if Agile Coaching is slightly different than Life Coaching, I see it as very relevant in Agile Coaching, too. If we apply this in Agile, instead of giving our clients (team, colleagues) the answers, asking them powerful questions to help them be more aware of what's happening at the moment, they will find their answer for it and will have a much better commitment to making the change for themselves, their teams and the company. It's not for us to TELL them what to do, but to ASK them what's going on for themselves. Here's where I see a huge chance for improvement.

    In my session I give lots of examples on how to link Life Coaching ideas to our Agile work environments. I've given the session at LAST Conference Melbourne and at the Agile Coaching Circles Meetup Melbourne. The audience was engaged and the attendees were very happy about having some new ideas on how to improve their daily work life.

    Come along to be inspired by Life Coaching and thus to benefit our Agile Thinking!

  • Liked Nagendra Kumar Elluru
    keyboard_arrow_down

    A Drive through SAFe Boulevard

    Nagendra Kumar Elluru
    Nagendra Kumar Elluru
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    An introductory session on SAFe's way of building agility at an enterprise scale. It is very hard to find an organization with teams who aren't practicing agile, but knitting them together into a program with appropriate cohesion, visibility and governance continued to be traumatic. Join me in understanding how SAFe can help us come out of this trauma.

     

  • Liked Roy Nuriel
    keyboard_arrow_down

    The Quality Assurance Journey - From Waterfall to Continuous Delivery

    Roy Nuriel
    Roy Nuriel
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    In the past several years we have seen more and more organization taking the decision and moving their development divisions to adopt Agile methodology. In most cases the change starts with a POC of a new and – in most cases – small project that validates the ability of the organization to make the shift to Agile. In many cases the development team takes the lead: changing the process, moving to unified teams, selecting which Agile practice to adopt, etc.

    In this session I will share how we made the shift, while focusing on the change in our quality process.

    As an R&D group that develops an Agile solution (HP Agile Manager), we wanted to get it right. We changed the way in which we develop software from waterfall to Agile, and built a process to support the teams in a complex and large enterprise. While previously we were accustomed to delivering releases in 1-2 year cycles, we now operate within a SaaS model where we update our production environment on a weekly basis. 

    We have experimented with the same process that our customers are going through and, as a result, we adapted the way our QA engineers work. In accordance with their new role, we gave them a new title – Dev Testers.

    Here are some of the dilemmas we faced:

    -          What are the differences between "Dev Tester" and "QA Engineer"?

    -          How can we measure quality in 2-week sprints?

    -          What needs to change when testing a SaaS solution that is delivered on a weekly basis?

    -          When and how should load testing be performed?

    -          Automated v. manual testing

    -          What testing should be part of the CI process?

    -          How do offshore Dev Testers take part in our Agile practices (e.g. daily meetings)?

    We dealt with all of these questions, and I would like to share the lessons we learned, our conclusions, and some of the challenges that we still face.

  • Liked Gopinath R
    keyboard_arrow_down

    3Cs for Agile Project Success - Critical Success Factors & Proven Practices

    Gopinath R
    Gopinath R
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Agile methodologies are gaining wider acceptance in Software Development and Testing due to its inherent values like Accelerate Time to Market, Eliminate Waste and flexible to adapt changes quickly. Agile practices emphasis on effective communication, collaboration and customer involvement for addressing the challenges in developing the product in dynamic business environment due to fast changing requirements. The co-location of project teams and high customer interaction throughout the project helps in achieving effective communication, team and customer collaboration.

     In an outsourced or offshore Software development, teams are geographically distributed to develop products in a collaborative and cost-effective manner by better utilization of global talents. Adopting agile methodologies helps in better ROI by developing quality products as per changing market needs in short span. Adopting Agile in global software development shall pose few challenges due to wider geographical distance, time zone differences, and cultural aspects and so on.

     

    This paper presents 3Cs – Communication, Collaboration and Customer Involvement as Critical Success Factors that need to be considered while implementing Agile for Global Software Development. It also details proven practices to address the challenges due to distributed agile software development. This paper is based on Author’s experience in executing Outsourced Product Development engagements using Distributed Agile Methodologies for co-creating Telecom products

  • Phil Abernathy
    Phil Abernathy
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Over the last 2 years, in small pockets all over the world, people have been experimenting with the use of Agile and Lean in formulating and executing corporate strategy.

    The finding will astound you and lay the foundations for what may become the next wave of ‘Agilean’ transformations, thus paving the way for vertically transformed ‘Agilean’ organisations that deliver outstanding profitability.

    The ‘Lean Startup’ mentality or ‘Management 3.0’ are tips of the iceberg in recent strategic thinking.

    This talk draws on experience and real life examples to outline how Agile and Lean, and not just Porter’s 5 forces, can be used effectively to not only formulate and execute corporate strategy but also to enable transformation throughout the organisation.