Skip to main content

Lessons in Lean (1)

When I wrote the Fingerspeller Flashcards, I thought I should pre-load the graphics (and the dictionaries) so that when a character is displayed, it is available instantly.

This had a small problem with it: Each alphabet, say ASL, has 26 to 30 images (actually more, since each letter needs at least 2 images) and each image is 30KB. So I had 1 MB of images plus the program (another 200KB), so all in all some 1.2 MB of data had to be downloaded before the program was ready to go.

This has a major disadvange: With a 128Mbit/s ISDN internet connection (very fast dialup, equal to 16 KByte/s), it took at least 75 seconds to get the application ready to go. Even my 3.5 Mbit/s Cable connection needed almost 4 seconds (although 4 seconds is fast enough that I didn't think about it much). But the long delays made the program unusable for most of my users.

The program only displays one letter at time. But it was downloading all the images in advance, just in case one was needed, and this meant none were available for a minute and half (and even a basic DSL line needed 40 seconds), longer than most users are willing to wait. If it would load just what it needed, it could be ready much sooner.

This is like writing detailed specifications before you start implementing. You have so much specification, just figuring out where to start take a significant amount of time. You can't see the forest for the trees. And because everything is "Must have", the whole project must be finished any value can be obtained from the project.

This is the biggest drawback of the procurement process as practiced by the Swiss government and other big institutions. Massive, very detailed specifications produce huge projects which must be implemented in their entirety before they can be used at all. A product that can't be used has no return on investment.

Time to ROI is probably the most under-appreciated cost factor in software projects.

How did I solve my problem? Easy: load the images on demand. There is a delay of 1.5 seconds between the point when I know I need the image and when I actually have to display it, which at 128Kbit is enough to download 24KBytes. This is "Just in Time" Delivery.

So I changed to code load images only on demand, and did some other compression on the HTML and javascript. In the second iteration, I reduced the image size from 30K to 15K. Result: The start page now needs about 2.7 seconds to load on a 128K line.

I need to find a way to get the images down to 8K (suggestions on how to do so would be most welcome!) to make the process really robust, but the improvement was immediately visible in my Google Analytics stats.

This is Lean Thinking. Eliminate waste, focus on delivering value, and improve continuously. This is also Scrum, with its plan - do - evaluate - improve loop, which focuses on implementing the most important functionality this month, getting it done, and then repeating process next month.


Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …