As the adage goes, "many a true word is spoken in jest". In this session we will take a humourous look at common distortions and misunderstandings of Agile principles, processes, behaviours and roles. You will learn precise, clear (re)definitions for Exactimation, ScrumLord, Rundown chart, Fauxgile Methods and many more! Using levity as the entry point, for each definition we will examine how the original idea or concept is commonly misunderstood or misapplied and discuss corrective measures.


Outline/Structure of the Talk

Related blogpost which has a number of 'definitions':

Will introduce around 10-12 term definitions. For each term:

  1. Introduce definition (e.g. Exactimation)
  2. Wait for laugher to die down (fine, wait momentarily for polite chuckling to subside)
  3. Talk about a few common examples (e.g. how estimates forced by management can appear to be misleadingly precise, but have little to no accuracy leading to poor planning decisions)
  4. Briefly discuss how this can be done better (e.g. for initial estimation for a project, instead of breaking down the scope into epics and doing ground-up estimation, use t-shirt sizes using a relative sizing board, with t-shirt sizes converted to time & cost based on historical data ranges, making the low-fidelity nature of the estimate evident).

Learning Outcome

  • Expand your vocubulary of classic misinterpreted and misapplied concepts that many of us encounter on our agile journeys
  • Learn how to spot such instances
  • Get introduced to some ideas for better ways to think about and apply these concepts

Target Audience

Agile newbies and experienced agile practitioners may both be able to appreciate this lexicon

schedule Submitted 6 years ago

  • 45 Mins

    Good engineering practices and fail-fast, iterative, low-ceremony processes help achieve team level agility. They are necessary but not sufficient to scale agility across the IT organization. In this talk, I'll address what else is needed and why. In particular, I'll address:

    1. Why plan-driven IT projects are a bad idea why we need value-driven projects instead
    2. Why a matrix org is a bad idea for IT and why we need cross-functional teams instead
    3. Why IT budgeting needs to change from being project-based to being team-capacity based
  • Naresh Jain
    Naresh Jain
    schedule 6 years ago
    Sold Out!
    90 Mins

    In order to achieve my goals, as a buyer of your product, I want awesome feature.

    AT: make sure your users stories don't get in the way.

    Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories that adhere to the INVEST principle. We'll learn various techniques to slice your stories using the vertical-slicing approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.

  • Chirag Doshi

    Chirag Doshi - 1000 Words - Illustrating Project Challenges with Visuals

    Chirag Doshi
    Chirag Doshi
    General Manager
    schedule 6 years ago
    Sold Out!
    80 Mins

    A project can face varied challenges through its life, foreseen and otherwise - runaway scope, high defect volumes, depressed velocity, and many more. Addressing many of these first requires recognition of the problem and then action from one or more sets of project stakeholders. Telling the story with simple visuals can be a very powerful way to articulate a challenge (the what), the potential root causes (the why) and the options available to fix it (the now-what). Teams typically already track a lot of data related to throughput, quality, scope and cost. Creative use of this data combined with simple, hand-crafted visuals can be much more effective than hundreds of bullet points. In this hands-on workshop, you get to exercise your visual thinking and visual communication skills. We introduce some simple visual thinking techniques like Look-See-Imagine-Show, and then let you apply them in a project simulation, so that you can practice hand-rolling simple visuals that speak volumes (no fancy tools needed!).