Skip to main content

Lego City Police station construction project


I just today completed the Lego City Police station construction project. Off budget to start with, and a bit late of schedule.

While doing it, I quickly noticed some similarities to a normal construction project, in my world a software system construction (or acquisition) project that is. Thought to write them up, as they felt kinda funny.


A meeting with the dev lead and the product owner
First of all, the whole thing would have been a lot easier to build without the constant pressure by the product owner...

Secondly I gotta hand it to the Lego architect - the whole thing was really nicely packed and arranged, the building instructions were fantastic, and the pieces and puzzles clearly thought through. So building something with this kind of a fantastic specification, was rather easy even though it's over twenty years I've last done something this big with Legos. Without the spec, or even worse with an incorrect one, it would have been sheer hell.

Third similarity: Some developers are better (or have more experience) than others, some are quicker and sloppier, some slower and more careful. Although I think with our dev team my wife was quick and careful and I was slow and sloppy.. Team work wasn't that easy either, but it seemed to go well after we established some kind of roles and responsibilities.

Fourth similarity: When a bug was found it usually (not always) was a lot easier to fix if found early, compared to a one found late having many layers already built on top of it. Also the rework caused by this was really frustrating. There were differences also in the ways and timelines of finding the bugs - most were quickly noticed and immediately fixed, but some were harder to spot early and were only noticed by some mysterious extra pieces, or due to integration issues with new layers.

In the end everybody involved in the project was so tired with the whole thing that nobody really wanted to use it anymore (is that a fifth one?). But it looks pretty nice! Hopefully the product owner will still grow into it..

Lego City police station - large

Labels:

Comments

Post a Comment

Popular posts from this blog

Periodical retrospectives are lame

  "You got nothing, not a single thing?! Well lets just end this here then." I remember well when I said this, being very frustrated. About ten years ago I had been working as a Scrum master for a team some months, and putting quite a lot of effort into planning our scrum teams sprint retrospectives. Lot of work also because I felt we were not getting too much out from them; not very good discussions, very few actions, and even the few actions we did come up with did not stick.  And then it happened: a retro where none of the participants came up with anything to say about the sprint. Regardless of the retro topic boxes, reading of books on retrospectives, getting inspiration from tools like retromat.org, having them in different places, using all kinds of different formats and rainbow coloured post-it notes. Not a single thing. Blank.  So then I said the words, out of frustration, mainly to myself. Why couldn't I get this thing everyone is so hyped about to work? After t
Post a Comment
Read more

I don't report bugs

I don't report bugs . Bug is such a loaded word that people understand very differently, that instead of using it and explaining what I mean by it I rather just use other words. Like observations, thoughts, surprises, ideas, alternatives, or something similar. (And no I don't use fault, defect, or error either). Bug has also quite a negative connotation. "Reporting a bug" is kind of like telling someone that they've been served. And as we are actually giving away the gift of information, why wrap it in such a nasty package? And maybe more importantly it is very likely that whatever you might have to say is wrong. If not plain wrong, then at least incomplete. So I like to approach the kind of situations with the assumption that I am probably wrong. Cutting off anything that might sound arrogant makes stuff quite a lot easier. Especially after you realise later on that you have been wrong. I leave plenty of observations unreported . I don't want to waste
Post a Comment
Read more

Testing drunk

(My first blog writing ever.) I've been thinking a long time that it's funny how many bugs I find by accident. Try to do something, make a mistake and boom - a bug is found.  Making the mistakes intentionally doesn't quite work - that's why they are called accidents I guess.. So I've thought of ways to make myself more prone to accidents, coming up with an apparent one; testing drunk. TUI (testing under the influence). So this I gotta try. More to come on that later.
3 comments
Read more