BOOK A CALL

September 23, 2014

Agile Estimation Cards and the Art of Kitchen Renovation

By Russ Lewis. Published online September 23, 2014

Builder working inside a roof

Construction runs to a well-established plan

Simon is a project manager who is having some building work done at home - an extension with a new kitchen. We were discussing Agile project management and specifically Estimation Cards. He pointed-out that his "development team" consisted of builders, electricians, plumbers and kitchen fitters, who all worked to a well-known requirement and a well-established plan.

Builders are specialists who are estimating and planning all the time - without using agile estimation cards!

Running a building project is all about responding to threats to the "big, up-front" plan. Each trades-person knows how much time it will take to do the work once the materials have arrived on site. What matters is the order of the work and these dependencies are well-known. Each morning they plan the next day's work, call the builder's yard and order the materials needed. This isn't Agile, it's plan-driven and relies heavily on an external supplier. Estimation cards aren't needed because there's no team activity.

Coordinating the plan

The plumber and electrician do a "first fit" to lay the pipes and cables, followed by a "second fit" when they attach the basins, taps, sockets and switches. The kitchen fitter though does everything in one go, so all the plastering and floors have to be in place beforehand. The variations, and "unknowns" from one job to the next are learning how to use new fittings and fixtures, working with trades-people of varying levels of quality, and of course, the impact the customer makes. Some customers keep changing their minds during the job - apparently!

Building works like these are plan-driven projects. They are deeply affected by last-minute customer changes. Simon, an enlightened client who would never make last-minute changes, says that a big impact on the plan comes from external factors like the power company, availability of raw materials and lead time for sub-assemblies like stairs, windows and doors. Of course, as a first-class project manager, he had prepared a risk log, with back-up options and plans already in place.

Use Agile to develop the plan

For software projects, the risks are inherent in the technique itself which is where Agile management is needed (useful article on Agile Project Management here). You are creating something for the very first time, for a customer who needs something that performs better than what they have now. Not just bigger and with the latest fittings, as is the case of a new kitchen, but something that will support an improving process, scale when needed, be easier to maintain and help the business create an advantage in its market.

Categories: ,
Tags:
Newsletter signup

    Recent Posts

    How to restore Teams Wiki data after Jan 2024

    Microsoft killed Wiki on Teams - who knew they would delete our data too - here's how to restore it

    Read More
    Transformation research update

    'Managing Tensions not People' as transformation method research update at the end of 2023 This time last year I was searching through the ambidexterity literature for tensions other than the usual explore-exploit. I built a website to publish my progress online, which I think was a diversion! Literature research update I found more than 70 […]

    Read More
    The HOW of Transformation

    The HOW of Transformation recorded at the Global Digital Transformation Summit in Berlin 2023 Summary Managers who manage tensions enjoy greater performance, especially in complex and dynamic environments. In this 36-minute talk: I tell the story of Transport for London's transformation from a one-sided fares Operator to an integrated Developer-Operator. And show how technologists using […]

    Read More
    In praise of rights licensing bots

    I was at the digital transformation summit in Berlin last week when I got a scary "unlicensed use" email from a rights licensing lawyer. The rights licensing bot service sent me a screenshot of the page and the cartoon I was alleged to have used. I say alleged because I didn't recognise the cartoon or […]

    Read More
    Ways of Working: 5 improvements for leaders

    Most ways of working still rely on functional hierarchy, where managers make decisions and workers do the work. Managers know they can't change this work structure, but they can transform its effectiveness without asking for permission and without needing a budget. Before exploring the changes that transform the way people work, we need to recognise […]

    Read More
    Manage tensions if you want an agile transformation

    Today’s challenge is that traditional management approaches, where managers tell people what to do and how to do it, are not as effective as they once were. Agile transformation takes years, but changing management’s focus from people to tensions could be a better solution. It is simpler, faster, and considerably more cost-effective. Management is the […]

    Read More
    July 3, 2020
    New Normal: FGS Panel Discussion

    I joined FGS CEO, Peter Stroud and his guests discussing “the new normal”; James Hall, Global Storage Chief Technologist at HPE Frank Purcell, Operational Services Manager at Islington Council What you cant see is the wine-tasting that followed. Pete sent each of us a case of half-bottles of wine from Berry Bros. It was great.

    Read More
    June 18, 2014
    Developing Skills the Agile Way

    Development Occurs over Time, not on a Training Course During our many combined years as trainers with Learning Tree International, the average instructor grade exceeded 3.8 of a possible 4.0. Attendees loved the training, and provided fantastic testimonials. But that doesn't mean they used what we taught them, or that they improved because of the […]

    Read More
    June 22, 2016
    Writing an Agile Article for a Proper Journal

    The work of the agile business analyst is never done is one of the conclusions reached in my first agile article for online journal InfoQ User Stories Are Placeholders for Requirements. At 3500 words plus five key take-away points, and with editorial and peer-review by the wonderful agile writer and educator Ben Linders, this was […]

    Read More
    1 2 3 13
    linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram