Personal Kanban Mapping work | Navigating Life

Personal Kanban Mapping work | Navigating Life by Jim Benson and Torianne DeMaria Berry.

i have an interest in lean or agile development , be cause it gives great opportunities for making improvments in a place where you don’t have fixed processes. Kanban is one of the principles related to ie scrum. It is a little different how you are visulatizing the data.


Personal Kanban is about visualizing the work you are doing so you are able to handle it. I think the kanban part is really important because it gives some great options for users. This is normally done on a board of some part.


An important part is to limit your Work in progress (WIP). This is all the task that you are currently working on in any way. If you can reduce the number of distinct items you are working on at any one point you have more mental capacity and it will be easier to handle the different work items.


With the visualisation you will be able to see what your throughput is and how long time it takes to handle any one task.


We are dealing with the real world, so it is not always that we are able to block everything off and just work on what we want. A good example is now when I was just interrupted by a Text message that I choose to react to. It could be import, but it was not.

Personally we often get stuck in the state over complication, where we make everything way to complicated to handle.

The goal is to have task that are pulled, where you as a person decide which one to use. Push is just to take the first thing in the inbox and react on it.

A list programmer is most often superior because they take the time to know why they are building the software in the first place. This gives some clarity and makes it more compelling to workon. I guess that it is something like building a wall or a cathedral. The clarity helps with giving growth.

I you cannot see the work it is uncontrolled and we should never do more work than we can handle. I guess that it is an important part that we are able to know what we can do and not do more.

Currently I think I have too many tasks on that I’m working on to be successful with it. I know that it is difficult to say no to projects whey they are there and you think it is good for you.

The last thing is the POMODORO principle where you are focusing on some work for 25 minutes and then take 5 mintus of. This will help build your focus and make sure that you can get much longer in your progress. It is a really difficult discipline to use and it requires a lot of self control. It is so nice and much easier to work on other peoples projects than our own.

I’m currently reading about how to use normal Kanban in product development.

I did like the book it gave an overview of what kanban is about and the importace of stopping with all the work that you are doing.

Great by choice by Jim Collins and Morten Hansen


Great by choice by Jim Collins and Morten Hansen


This book is the sequel to Build to last and Good to Great. It is also a research focus book, where they are comparing a bunch of different companies of different perspectives. The book validates the principles of the previous books.

They have found 10 different companies and have compared how they are performing compared to other companies in similarly niches.


They companies they have selected did a lot better. And they introduced the concept 10 x companies to identify the behavior of the better performing companies.


The things they are finding the companies are doing better are the following.

  • They are performing constituent. They don’t grow because they thing the market can bare it. They strive for a 20 mile walk everyday to make sure that people are not getting too tired have something to go for. This is like Southwestern which only open a few new routes every year. For every year they have started new routes.
  • They try to experiment with something. Shoot bullets and when they find something where they can excel in they do the bet for it. They need to have the time to bet on next big and work on solving the problems.
  • Innovate but still keep the old ideas that work. Know when to kill the products.
  • Have a deadline, for when the product can no loger be used or when something should be done before. If we cannot make it to the top today, we have to turn around.
  • Luck there does not seem to be any indication on if one or the other part is doing any bether. They seem to have been gotten the same number of luck. The difference is that the 10x was able to use the unluck to propel them forwards.
  • They are Specific Methodolical and consistent (SMaC ) with their content. It makes a difference in the way to are able to communicate. It could be like the bill of rights where they have a clear understanding of what will work in the future.


To contain the presentation they are using a framework. It does make it a bit more clear on what they are doing and how things will be explained.



One thing I like about the book is there is some questions that you can ask your self at the end of each section on how this apply to my organization. This really helps and makes it much more interesting to read. The questions give a sense that there is something that I’m cheating when I don’t answer the questions.


There is also use of explores to show how the ideas works for them. It could be the comparison between Scott and Amundsen South Pole journey. They use a lot of the same principles as the 10x companies.

Steve Jobs biografi af Walter Issacsons

Mine ideer fra Steve Jobs biografi.

Den integererede løsningen vil være lagt bedre, da man herved har mudlighed for at kontrolere end 2 end. Det var stor fokus på hvilke approach der var bedst.

Man skal fokusere på nogle enkle løsninger, og ikke forsøge at komme rundt om alle de mulige ting som man kan lave. selv en stor virksomhed som apple har kun mulighed for at fokusere på et begrænset antal områder. Det skal man hjælpe med at håndtere og vælge de områder der giver mest emnign.

Man skal have en ærlig virksomhedskultur, hvor folk er istand til at arbejde sammen om at komme frem til nogle løsninger. Det gjorde Steve ved at fortælle sig mening. Det kan lyde meget hårdt at komme med de udtagelser, og folk er ikke glade for dem når det sker. Men efterfølgende skulle de virke meget godt.

Han virkede heller ikke så sympatisk den måde han reagerede på over for folk. MEn det er nok hans måde at sige at det skal være bedre den måde tingene køre på.

Han har forstået at få det rigtige team omkring sig, og det er en del af successen at kunne få de folk til at hjælpe med at drive virksomheden.

Han havde et fokus på at han skulle være en kunstser, og ikke ingenør. Der er en forskel i hvad det er for product det giver. Kunsteren vil have det skal være pænt og estitikken skal være god. Engineøren vil have noget der er nemt og billigt at producere. Det giver forskellige produkter.

Man skal nok også huske at vi alle skal dø og derfor bliver vi nødt til at fokusre på at lave noget der giver en legacy. Hvordan kan jeg sørge for at få lavet noget.

Vi står alle på skulderne af giganter. Vi bruger noget som andre har valgt at lave til os,som vi bliver nød til at bruge, hvis vi vil frem i verden. Giv dem kredit.

MAn skal måske ikke være så generet og ikke ville spørge folk som er på andre niveauer end en selv. Jobs ringede til HP direktør da han var lille. Det samme er muligt i andre sammenhæng.

#SAPPHIRE youtube challenge: Meet the right people for you

I’m leaving from home in a few hours for SAPPHIRE, and really looking forward to meet all the really cool people there. But you mostly meet people at random, some will help get your objectives. But you have to be lucky.

So I thought that it could be interesting to see how was at the event that could make a difference. The ideal people for me to meet would be people working with SAP Process Integration (PI). It is difficult to find them and you have to meet a lot of people, which is nice though.

I decided to make a video saying how I wanted to meet. It would though probably be nicer if other people did the same. So if you are up for the challenge. Create a youtube video about how you want to meet. The format can be whatever you can make. If it is with your mobile phone it is also great.

Just make a video reply to my movie and tag the video with #sapphire and #sapphiremeet.

Hire is my video.


Book of the week: Cradle to cradle and SAP development

This week I was reading Cradle to Cradle from Michael Braungart and William McDonugh. The book gave room for thought. Both on how we create more enviormental friendly products. But was triggered me most was how it also applys to the usage in SAP.

Vishal Sikka mention the timeless software. Where software can continue to run for ever, but just get a new front.

As a developer you can also apply some of this. How do you make software that is easy to get started with.

See the video hire.

Book of the week: Resonate

Yesterday I was reading Nancy Duates Resonate. About how to create extraordinary presentations that changed the way people felt. It is a really nice graphical book. Something that other also could inspire to do.

Nancy is using a model to describe the way presentations should go. There should be something about the present and what why that is not enough and a frustration. Then there should be alternations to what is supposed to/or could be. If you change between these to stages in the presentation people will feel like there is a reason to change. Nancy applies the model to both Steve Jobs Iphone launch and Martin Luther Kings I have a dream. They can bot be described using this way.

One part that I particularly enjoyed was a case story from Cisco, where they had a slide describing a technical solution. Instead of starting with why the technical solution they change to start with a story about a beer producer and a problem that he was facing. Then they had a cliffhanger to make sure people were listening to the technical solution. After the technical details were described they could come back and tell the story with beer producer. It seems to give a much better flow in the presentation.

One thing that I found interesting was only to have one idea per slide. And it should be as brief described as possible. People should not have to spend a lot of time reading the presentation, because then they are losing focus on you. The slide should more serve as an anchor for the message. The long slides are more of a report, but that is a different ball game.

Also only spend max 2 minutes pr slide. This is a loft different from what others are getting. I have heard that you should spend up till 5 minutes a slide. So it is a large difference. But if you are only allowed to have one idea on a slide it is easier to describe the change.

One final thing that struck me was the practices it requires to make a presentation. If it has to be good you should have focus groups. Most people do not give time for creating more than one draft or practice. We have become a culture of first drafters with blogs, a emails, and presentation.

Supporting and acknowledge in sports

I was helping out at Islev Triathlons yearly Duathlon (5 km run, 25 km bike and 5 km run and a half distance). I was watching one of the crossings one the bike course.

I was supposed to watch and notify the cars on the bike riders and make sure they stopped and saw the cars. There was only a few times where we had to watch for the cars, mostly seem to work out without any problems.

To spend the time I started to cheer on the riders. I remember when people cheered at me, when I was out on my bike or other places, it gave an extra kick. Think that somebody is watching what I’m doing and helping me gives energy. I don’t want to let the people who believe in me down.

I have not been cheering that much on foreign people. But this time I was able to give comments that hopefully inspired a few. I became almost high from giving them feedback. I’m not sure if it is the unselfish act that triggers this energy or the use or an alternative way to give more.

Some of the drivers how drove by gave a few signs of thank you. It was nice to know that they linked the feedback and it made them perform at a higher level.

Some of the car drivers, how drove by, also waved to me. It was as they liked the part of having energetic people around. It would be interesting if this showing extra energy also affect other people not involved with the race.

It was a fantastic day and I had a lot of fun and enjoyed being outdoor for the morning. Even though I was unable to see the Formula One Race in Malaysia.

Book a Week: SAP Netweaver Process Integration 2nd edition

This week’s book is probably not the most interesting unless you are considering to use SAP Process Integration. SAP NetWeaver Process Integration Mandy Krimme and Joachim Orb. It is updated to SAP PI 7.1, so by now it is time for a new version.

I have been working with SAP Process Integration for a long time. I though found some areas that I could improve in.

  • For my use of Java mappings the book described the use of AbstractTransformation, which gives some extra options for getting extra payloads.
  • There was a good short description of the use of CCTS.
  • I became a bit clear on when the ccBPM created new transactions and when not. This does clear up some misunderstanding
  • There was a good example of modeling with Process Component model and Integration Scenario Models. This does make the usage of the different components clear.

It is a quite technical book on how to use each of the tools. The basis of the book is to describe each of the different components, which makes it a good induction to what is going on.

It is a book that will take you thru the basis usage of SAP PI.