They’ve done it again. Gojko Adzic, David Evans and, in this book, Tom Roden has written another 50 quick ideas book. And this one is equally good as the previous book on user stories. If not even better.

From the looks of it there’s a whole concept around these quick ideas and, fingers crossed, we can expect much more goodness like this.

This is my review after reading the book in the worst possible manner. I’ll tell you why. But even doing so I got so much out of this book and my tool belt expanded significantly.

I’m at the airport waiting to go back to Indonesia after great Yow West 2015 conference. As always the mind is filled with impressions and memories. And as always when you think back is mostly the great people you met that sticks in your head.

I just realize that there’s like an “agile culture” that I’ve now seen all over the world. I met a lot of people that I’ve never seen or interacted with but still, since we have read, thought about and worked around the same things the connection was immediate and I felt right at home directly.

The agile community in Australia is really vibrant and filled with awesome people championing conferences like YOW and Agile Australia. Standing a big risk of forgetting someone I had such a great time meeting Dave Thomas, Craig Smith and Nigel Dalton that was running...

Twitter is a wonderful forum and I owe much of my knowledge and progress from sparks found in tweets and from following interesting people and threads. But according Spiderman wisdom it, like all thing powerful;

yada yada yada ... great responsibility

I have seen many of my good friends being bashed, or they themselves lashing out towards people on Twitter. A couple of times I have been hit by just a small portion of that and it hurts. I’ve considered quitting it altogether a couple time. As many of my colleagues has done.

In this post I wanted to examine a Twitter phenomena and see what I can learn about how I communicate. Please join me.

I had a couple of great conversations yesterday that gave me a small epiphany. Here’s the small thing that I came up with:

Meta is not the most important thing. By definition.

Well… it’s not much now that I see it. But maybe you’ll care to join in my reasoning. Anyway that what’s the rest of the post is about.

The other day I commented on a tweet from Paul Klipp. A man I highly respect around all things Lean and Agile. Here’s the tweet and my response:

@duarte_vasco @paulklipp true, but only chasing waste is too simple :) "Value trumps flow, flow trumps waste reduction" @DReinertsen

— Marcus Hammarberg (@marcusoftnet) May 9, 2015

All the elements to have an argument are in there: the word “waste” is used (see below) the tag #NoEstimates is mention (which in itself has caused a lot of anger) and finally the tweet is a bit provocative.

However, since I know that “waste” is a concept that many people have many different ideas about (I promise I will explain) I wrote the comment above.

After that I found myself in a discussion on twitter made up of some the names that I...

One of the things that becomes increasingly fascinating as I get older is the new knowledge acquired while “doing things for real”. Currently, we have been building a site for my current organization.

We built a little CMS to drive content, and the whole page is a Single Page Application (SPA). As we approached completion, we naturally wanted to add Google Analytics to the site. Sounds simple enough.

Or maybe not… in this post, I’ll describe how we got it to work for our Single Page Application. Google Analytics default setup is not built for that. And many descriptions you find out there are written with a client-side framework in mind, like Backbone.js.

What I write about below only requires jQuery, and that’s mostly for convenience.

As with most things I learn, it’s based on others’ knowledge that I tweak. In this case, I found a...

One thing that I often find myself want to do is to check the database after I have created a resource. For example:

• Post some data to /user
• Verify that I get 201 Created back
• Check that the data in the database looks ok

I have had such a hard time finding a stable way to do this. I know that I have a little bit of a special tool chain but still… it should not be this hard.

But last night, after weeks searching for this, I got it to work. I’m so excited to share this with you.

Recently, I had the pleasure of engaging in an agile coaching opportunity in Kuala Lumpur for Nintex.

The experience was not only enjoyable but also enlightening, as coaching often leads to mutual learning and growth. It’s fascinating how verbalizing abstract ideas can give them new clarity and depth.

In this post, I’d like to share some of the insights and concepts I discussed during the three days spent with the teams at Nintex.

Setting Clear Goals for Sessions

One valuable lesson I learned was the importance of setting specific goals for each coaching session. Inspired by advice from coaching expert Dan North, I made it a priority to define clear objectives for each team interaction. This simple yet powerful practice helped guide our discussions and focus our efforts effectively.

Embracing Experimentation over Change

Throughout the coaching sessions, I emphasized the importance of framing initiatives as experiments...

The little series I’ve written on supertest and other Koa friends is moving very slowly ahead. Lots of new findings is making for a lot of innovation that I need to find out and try out.

But here are the things I’ve written so far:

• Splitting API over several files
• Splitting the API not only the test - this post
• Verify in database after ended request

In this post I will show you a powerful way of using koa-mount to create a very modular application structure. And how to test it, of course.

As before, if you want to tag along as I build this example out, grab the code from this tag, and we’ll start at the same place.

I recently returned from three days of coaching at Nintex in Kuala Lumpur. During this time, I had the opportunity to work with six teams consisting of 40 people. What struck me most during this experience was the level of trust Nintex showed in me. Despite the inability to micromanage my coaching, they placed their trust in my expertise. This trust is foundational for effective coaching and collaboration.

One topic we discussed extensively was the concept of “Order Point,” a key element in the Kanban methodology for replenishing backlogs just-in-time. Unlike traditional approaches such as planning at the start of an iteration (common in Scrum), the Order Point enables teams to dynamically manage their workload based on demand.

Understanding Order Point

The Order Point, as described in Kanban In Action, serves as a signal to replenish the backlog when it reaches a predetermined threshold. This threshold, illustrated...