One thing that is really interesting and very enjoyable is to have long time contacts over social media (in my case Twitter mostly). Many of these people I have never met in reality and I still consider them friends. We know quite a lot about each other and have learned a lot from each other. Kristof Claes was the guy that introduced me to NancyFx and SimpleData in 2011. From an excellent blog series about a photo blog (couldn’t find a link…) he thought me a lot. He has now got an opportunity to use Kanban at work and asked me a question about that. I asked him if I could blog the question and my answer and he agreed. Here you go: First Kristof’s question: I have a very very limited knowledge of kanban and I *think* kanban can help us with a situation at work, but I'm not sure. I will briefly...

The last week the blog post turned long. Sorry. This meant to just be short updates. Here’s another one. The first thing I did this week was to create a diagram over our throughput; the number of items we’re getting done per week. And it looked pretty bleak. And was about to get worse… Here’s how it looked at the beginning of the week. | | |:——————————————————————————————————-:| | | | Throughput trend at the start of the week | That’s not looking good, right. I think I can explain it… and I think that I shouldn’t care too much about data with these few data points. A lot of the things that we are doing require third part input. Someone else needs to approve, read or work with the item before we can finish it. I’ve been working with a LOT of teams that have this situation. It’s a drag…...

DISCLAIMER for frequent readers of this blog: I now work for the Salvation Army in Indonesia and they asked me to write an article from time to time in the Indonesian War Cry (the Salvation Army magazine). I of course used my normal style of writing and wrote about the thing I’ve written about here. Oh, not Javascript or Nancy maybe but Limit WIP, Lean and Kanban. But with a Christian twist and message. So if you don’t want to read this, please stop now. I’ll soon come back to my normal things. But if you want to please continue. Maybe there’s something that you can use in here. Or not. As normal on this blog, I use it to store my ideas and thoughts. END DISCLAIMER Here is the second of two short articles that I’ve written for the Indonesian War Cry. You can read the first here. This article is about Achieving more by doing less. I hope you...

DISCLAIMER for frequent readers of this blog: I now work for the Salvation Army in Indonesia and they asked me to write an article from time to time in the Indonesian War Cry (the Salvation Army magazine). I of course used my normal style of writing and wrote about the thing I’ve written about here. Oh, not Javascript or Nancy maybe but Limit WIP, Lean and Kanban. But with a Christian twist and message. So if you don’t want to read this, please stop now. I’ll soon come back to my normal things. But if you want to please continue. Maybe there’s something that you can use in here. Or not. As normal on this blog, I use it to store my ideas and thoughts. END DISCLAIMER Here is the first of two short articles that I’ve written for the Indonesian War Cry. I hope you like it. I was asked...

Every week (or in case of this week) we hold a short retrospective. It’s very informal is basically just us asking ourselves what worked and what did not. And then we change something. I think that is very important. We change something. In order to improve. Those changes doesn’t have to, and up to now most haven’t, been suggested and implemented at the retrospective meeting. But we try to improve in small steps. Often. Hmmm someone should write about that. Going into this week we decided two things to improve: Deep dive into why we don’t get reports in time Lower our work in process limit from 14 to 12. One of those were very successful and one was not… Sloppy board management I have coached more than 40 different agile teams using board, like ours (btw here's the state on this morning). Many of them has not used a...

This week was really, really interesting. The things that happened on the board and within the team was good but what happened with our interactions with others was both unexpected, a bit though and also important. I’ll try to describe both things without revealing to much details about people and events. Speaking of that, I got a comment about being this transparent with our work and there’s probably other thinking about it as well. Yes, I can see you. I can read your mind. You will give me $10000 Just kidding. But I have asked the team. I have checked the cards. There should not be anything too controversial on there. And finally, and most important, we are striving to introduce a greater degree of transparency and openness in our organization. I think it’s very important that we are transparent with our work. For us and for others that will follow...

This is a confession post. Yes, I’m a phony too. I pick up some things very late. Like JavaScript. And Node and … well a lot of things. But I’m sure that a lot of people have run into this and maybe, just maybe, there will be some others that haven’t run into it yet. So this might help someone. Or me, for that matter, when I come back to this problem later. It has to do with callbacks. The things that Node is made up of. And how they confused me a lot. And how I grew to love them, then hate them, and finally get them. And right about that point realize that there’s another way. Let’s see if I can explain this. Just as an experiment. Everything in node is event-driven (as from their mission statement on the homepage) and non-blocking. Which means that you see a...

I often blog too early. I get excited and want to tell everyone as soon as possible. I whip together a demo and then write a blog post about my experience. Sometimes that is a bit too early. Sometimes you need another look to really appreciate a tool, or to realize that it doesn’t do the job. In my blog post about Monk (which I still think is great… Monk, that is, not the blog post) I wrote that I didn’t like Mongoose that much. That was too early to say. I have now used it for real and I think I like it. Let’s me redeem my bad Mongoose-conscience and write a short post on what I’ve picked up when trying it… for real. The thing that ticked me off and actually made me turn away from Mongoose on the idea-stadium was the fact that it needs a typed...

This is just a short thing that I experienced when doing the data layer for AptiTalk. AptiTalk is an attempt to create a corporate chat, we want something like Hangout but better. Yeah, we’re not only best - we are the most humble as well! Ok, in this simple setting I learned a thing about using document databases (Mongo in this case). The data model is really simple. It’s just a Posts, Replies and Hashtags. So we created the Posts like this (using Mongoose): Let’s leave the Replies out of this discussion for now. I think I have more to say about that, but I haven’t tried it yet. The Hashtags in turn is just the Tag and a reference to all the posts that contains that hashtag. Like this: Notice the reference to the Post-collection in the pots-array. Both me and Hugo was alright with that model. I started to...

I have a wonderful opportunity on my hands. I have been given a team of 4 people that never have done agile or lean before (albeit one of the is Elin, my wife, so she should know something). I have also authorization to decide about how and what we work on, within some limits (that I don’t really know the bounds of yet). And I have three years to work with them. For the better part of my career I have been a consultant giving advice to people with power of various reach. I have often done gigs that have been ca 6 months in length. Sometime they have been prolonged but then it has always been to go somewhere else in the organization. This time I have plenty of time and direct application of my ideas, no need to try to convince the person in charge. I’ve decided to...