The latest new, cool tool comes along. Will you be allowed to use it? Probably not! So how can you change that?

This presentation looks at the introduction of new technologies at three companies, The Forward Internet Group in London (a start­up originally, now grown to 400+); MailOnline, the online version of the Daily Mail newspaper from London (a very old organization with an existing IT shop); and Outpace, a Silicon Valley startup.

In both cases, Programmer Anarchy was introduced. This managerless process (not unlike GitHub in its value propositions) empowered the programmers to make technology choices and to freely experiment with new technology. In the case of Forward, massive growth and profits ensued. In the case of MailOnline, re­development of core systems into new technology has been launched, and expectations significantly exceeded.

This presentation will touch on the various aspects of implementing Programmer Anarchy at MailOnline:

  • Team building through programmer training

  • Pilot project without managers, BA’s or dedicated testers

  • Reinforce the model with new HR structure emphasizing skills over titles

  • Create self­organizing teams of 5­8 developers (multiple such teams)

  • Charter teams with a specific project, and let them deliver

  • Avoid artificial schedule pressure

The intent is to provide a possible roadmap to get your latest technical toys moved into production systems. 


Outline/Structure of the Keynote

Covered in the abstract above.

Learning Outcome

Broadly appealing presentation with something for a variety of audiences:

  • Developers: Describes an environment that facilitates introduction of emergent technologies

  • Project Managers: Describes an alternative to traditional empowerment and the power of blended roles to support experimentation.

  • Business Managers/Owners: Describes a system that keeps the start­up culture of rapid delivery and daily innovation. 

Target Audience

Developers, Project Managers, and Business Managers/Owners


schedule Submitted 6 years ago

Public Feedback

    • Patrick K Phillips

      Patrick K Phillips - Understanding Lean and How it Can Scale Agile

      60 Mins

      Is business process improvement part of Lean IT? What about best practices and benchmarking? Is agile software development a Lean IT practice? What about IT operational excellence and the ITIL service management framework? How about performance management dashboards and scorecards? Is applying Lean techniques to project management considered a Lean IT practice? And is cloud computing relevant in a Lean IT world? The answer to all these questions is yes. But Lean IT is much more than just a set of tools and practices; it is a deep behavioral and cultural transformation that encourages everyone in the organization to think differently about the role of quality information in the creation and delivery of value to the customer.

      Lean IT enables the IT organization to reach beyond alignment toward fundamental integration, cultivating an inseparable, collaborative partnership with the business. Whether you are new to Lean, or a seasoned veteran, in this book you will find new insights into the power of Lean and the critical impact of an integrated IT function. In this discussion Patrick Phillips will explore all aspects of Lean IT within two primary dimensions:

      Outward-facing Lean IT: Engaging information, information systems, and the IT organization in partnership with the business to continuously improve and innovate business processes and management systems

      Inward-facing Lean IT: Helping the IT organization achieve operational excellence, applying the principles and tools of continuous improvement to IT operations, services, software development, and projects These two dimensions are not separate but complementary.

      The adoption of the term Lean software development is more than a name change. While agile is a set of development and life cycle management tools and methods focused on the just-in-time development of quality software, Lean software development addresses a larger context: the environment within which the software operates, the value streams of the enterprise. For example, in a business application, properly functioning software is viewed as a supporting element of the business process. In an embedded software application (such as the operating system of a smartphone or the control systems of a jet aircraft), the software is part of the overall product design and value proposition to the customer. Lean emphasizes seeing the whole through the eyes of the customer, not its component parts through the eyes of the designer or developer. “Lean software development views all Agile methods as valid, proven applications of Lean thinking to software,” says Jeff Sutherland, a signer of the Agile Manifesto. “It goes beyond Agile, providing a broader perspective that enables Agile methods to thrive.”

      In the words of Mary and Tom Poppendieck, “A Lean organization optimizes the whole value stream, from the time it receives an order to address a customer need until software is deployed and the need is addressed. If an organization focuses on optimizing something less than the entire value stream, we can just about guarantee that the overall value stream will suffer.” We have witnessed many skilled agile practitioners fall into the common Lean trap: focusing on tools and techniques rather than solving problems and eliminating waste. Lean software development expands agile’s focus from optimizing the software development process toward improving entire value streams. Thus, Lean software development must integrate and synchronize with all business processes, management systems, and kaizen activity, supporting the Lean transformation of the overall enterprise.  This session will take you into a discussion with a practitioner who is one of the industry's leading figures in understanding and utilizing lean. 




    • Prasad

      Prasad / Alok Uniyal - Speed 2 Value.. helping large Enterprise IT to be in the game..

      20 Mins
      Experience Report

      Technology has blurred the lines between the digital and traditional methods of dealing with a consumer of any Global Enterprises. The Business Process and IT is no more separate, in most of the industry verticals the Business is driven by IT.   Constant Innovation around IT has become the new normal to the Enterprises to meet rapidly changing consumer expectations and behavior dynamics.

      More connected consumers, automated processes, and sophisticated analytics place unprecedented demands on IT functions. Many Enterprises are struggling to cope, and they seek to deliver on new demands by adding piecemeal elements to their existing operations. This is easier said than done. Reinventing the IT function at Global Enterprise requires far-reaching changes, from talent to infrastructure, tools, delivery models, partnership model.

      This experience report  brings strategy of 2 speed IT, through which Infosys helped its Global top 10 clients to 'renew' its IT related to Digital & Mobility space using Agile as a key lever.

      This session gives you experiences, practical on the ground challenges, stakeholder and vendor complexity and approach and journey towards Speed 2 value. Also I am pairing with Alok Uniyal who is senior leader at Infosys and a CIO coach who helped 50 plus clients to transform their IT organization in last 20 years.

    • Zaheerabbas Contractor

      Zaheerabbas Contractor / Rituparna Ghosh - Enterprise Agile Adoption: An Organizational Change Management Journey.

      45 Mins
      Experience Report

      We represent the Agile Center of Excellence at our Organization and are chartered to drive the change management initiative to imbibe Agile adoption across the enterprise.

      We plan to share our experience on the Organization Change Management initiative that we took up to drive Agility across the organization.  Our journey towards the derived vision and strategy to increase Agility in the system to thereby achieve:

      • Nimble simplified processes.
      • Ability to respond faster to change.
      • And most critical: delivering increased customer value.

      This is a continuous improvement journey and we initiated:

      • Structured multilevel communications of CHANGE to the teams.
      • Learning + Unlearning:  Structured Training and Development plans (Behavioral and Technical).
      • Bringing in Gamification as a tool to get millennial team members to learn quicker.
      • Approach to move from “Pyramid” to “Hour Glass” structure to align with the flat team structure.
      • Pilot: Career Development Framework Aligned to Agile structure and roles.
        • Bringing in change of G&O to align with Agile delivery
        • Enabling Talent Fulfilment to align to the Agile roles and structure
      • Pilot: Performance change management- Holistic approach to drive appropriate behavior
      • Brining in systemic changes to ease Agile adoption
    • Asheesh Mehdiratta

      Asheesh Mehdiratta / Debbie Wren - Tales of (not so) successful Dev-Ops

      20 Mins
      Experience Report

      Welcome to the crazy world of Dev-Ops, where the tales span the spectrum from gruesome, grizzly to the heavenly and flowery bliss!

      The silo’d structures, the agonizing buy v/s build debates, the departmental handoffs, tooling and of course the cultural barriers, which all add fuel to the story unfolding in our brave new dev-ops world. But sometimes there are silver linings and the heavens part way for the shining stars to reveal their true glory.

      Join our session to listen to the tales of our (not so) successful dev-ops, and learn the lessons from our experiences.

    • Vinod Kumaar Ramakrishnan

      Vinod Kumaar Ramakrishnan - Build it like sports teams

      20 Mins

      Is it easy to get a crash course in football by Pele or Maradona for a week and produce a world cup winning football team?

      Answer is NO. Then why do lots of people in the corporate world think of hiring scrum trainers & expert developers to train their team for a week and then expect their team to undergo a transformation at a magical scale?

      German football team made it a point to transform their team and it took them a lots of years before they were able to reach the pinnacle. A quick side by side comparison of what is causing agile transformation to fail.


      Football: Someone was there owning this entire transformation, the German football association spent a lot of time identifying talent in their teens and groomed them.

      Office: In the corporate world switching jobs every few years have become common, but there is no passing on of the context, resulting in the new person taking charge, starting from all over again, as well as frustrating existing good performers who have to rebuild the perception.


      Football: Players expecting state of the art training facilities, fitness programs and new shoes are not a luxury, it is a necessity.

      Office: Computers have become so cheap compared to the salaries, yet the policy of providing the best tools and good work environment are archaic.

      Coach vs Management

      Football: Coaches are given their due powers to help the team achieve the goal. It is very easy for anyone to comment on how professionals should play their game, there would be no use adhering to the metrics if the team cannot win. Winning is the only measure for management.

      Office: Often coaches are seen as part of the management or management tries to heavily influence coaching which results in a team which will work either for metrics or to please higher ups without the actual result that it had aimed for.


      Football: Just the ability to kick the ball does not make a footballer. Training will be introduced to increase physical strength & stamina, better mental wellness, injury prevention, tactics and strategy.  A heavy investment is made in the training facilities.

      Office: In the software industry a generation is about 2-3 years. Computer science degrees are nowhere near what is state of the art in the industry. At many places the on boarding process is either very shallow or not up to date with the recent developments, leaving people to learn most of the things hard way. Given too many things to learn and the information overload, this results in inefficient learning and application of knowledge on the job. We need to prepare people to find answers that are not available on Google.

      Team composition

      Football: Rookies don’t learn by watching greats from the bench, instead they play along with the veterans. Every sports team makes sure to have the right composition with a mix of rookies, emerging players and veterans. That is how they sustain a winning team.

      Office: Architects and Leads often do not code or are not part of the team every day, this means that most of the time the team just looks up to for advice or waits for reviews. There should be a good mix of people at all experience level so that there are enough people to try new things, enough people who have mastered few things and enough people who challenge change.

      Above all – Persistence

    • Fred George

      Fred George - MicroServices: Let's Build Some!

      Fred George
      Fred George
      Fred George Consulting
      schedule 6 years ago
      Sold Out!
      480 Mins

      It is one thing to talk about MicroServices. It is another altogether to have to build them.

      After a brief introduction of MicroService principles, we will watch an animation of a MicroService environment. We will start with a pre-built skeleton microservice environment (message bus plus a couple of RESTful services running against it). We will then design and implement additional services to broaden the overall functionality. These additional services can be written in any language that will run on the participants laptop. While pairing is strongly encouraged, it is not required.

      In the final stage, different pairs will implement different services, yet they will all run together implementing the animation.

      We wrap up with the participants making observations on what they learned (and how it may be different from MicroServices they are currently implementing, if any).

    • Asheesh Mehdiratta

      Asheesh Mehdiratta - Will the Real Slim Shady please stand up?

      20 Mins

      Guess there's a Slim Shady in all of us…but the real slim shady - Product Owner role - today is mostly ignored and misunderstood across most organizations. This talk highlights the confusion and the need for recognizing the product owner role as a ‘first-class’ citizen across the industry.

       The session will help you take a closer look at your current product owner team, and compare with an ideal product owner role, and in the end suggest possible ways to align your product organization better. If you are already a product owner or managing a team of product owners, you need to join this conversation and pick and/or suggest some of your own remedies.

    • Asheesh Mehdiratta

      Asheesh Mehdiratta - Self Organizing: How to Lean-in to difficult conversations?

      20 Mins

      Leaders today are looking at “self organizing” agile teams to WIN ALL the battles on Auto-Pilot. Nice try is all I can say !!

      ...though some teams surely do succeed (lucky guys?).  But most teams are not so lucky, and get constrained by the organizational systems, processes, boundaries, and need an outside-in perspective or a divine eye to kick start their next improvement journey. Sometimes a leader takes on this divine role to guide them on this journey.

      This talk aims to provide the leaders a toolbox for using Lean conversations, to spark their next team improvement journey, by designing improvement kata’s, while slowly inching the team forward towards nirvana !! Divine Bliss !! .... So if you are a leader looking at learning and implementing the simple techniques of guiding the team on a self improvement cycle, leading to true self organizing team, join us.

    • KK Sure

      KK Sure - Testing in Agile - Antipatterns and Remedies

      45 Mins
      When it comes to agile, we all know and practise standups, retrospectives, sprint plannings, showcases etc. Quite a few times, teams end up following these set of rituals and ceremonies without understanding the guiding principles of agile.
      In this talk I will present some testing practices that various agile teams employ. Some of these practices are anti-patterns and have the exact opposite effect of what is expected, while others become an anti-pattern sooner or later if not tweaked according to the changing situations.
      I will talk about the aspects like "Whose responsibility is Quality?", 'Measuring agile tester's success", "Balance between automation and exploratory testing". Along with each of the anti-pattern, I will present the remedies to fix these anti-patterns.
    • Sriram Rajagopalan

      Sriram Rajagopalan - TBD Approach to Agile Transformation

      45 Mins

      The principles of agile are so simple that its simplicity eludes many practitioners. Pulling in a white board with sticky notes, writing user stories instead of business requirements document, avoiding developing any document, and use of some agile popular tools does not mean that agile has been implemented. 

      In this presentation, I provide an approach to how agile transormation begins. Fundamental to agile is the self-organization and if one doesn't think (T) agile, become (B) agile by following the recommended steps, and develop (D) on practices to refine agile in the specific industry, agile will not solve the business challenges. The personality traits of those leaders that attempt to transform into agile will lead to incorrect implementation.  Often, in such cases if Agile fails, it is because we failed agile! 

      Breaking on the TBD approach, this presentation will explore additional topics that start with us, team, and the organization to truly transform into agile methodology.