When I started working as a developer, I didn’t work with a tester. So I keep thinking that quality and testing of the code is developer’s job, and Gojko Adzic presentation confirms my understanding of software development process on some way. Take a look the Gojko Adzic presentation with his QA analysis about Greece crisis. …
I am rephrasing an old political proverb, but it’s true. If a manager ask you to release four days earlier, after he has promised you to postpone the release date with a week probably the chaos is so big in teams with this kind of managers that you can’t expect any quality from the software …
The real reflection of intelligence is to create order in the chaos despite of catastrophic environment!
This week I have been explaining about cohesion using materials from Prag Pub Magazine and realized something ultra very simple. The definition of cohesion is “proximity should follow dependency” which make me see that cohesion(proximity) is function of dependency. So cohesion = f(dependency) and if we want to follow Single Responsibility Principle you can just …
You can’t be lean in your job, if you don’t have lean thinking in your life.
So next time when somebody says you that he is lean in his job take a look at his life!
Today I was reading a news about “Spade Hacker”. At that moment I realized that every software company has at least one “spade hacker”. How many “spade hackers” do you have in your company ? 😉
A man who can’t read specifications, manuals, and use cases !
!!! By the way don’t forget the requirement IQ test below 90 points !!!
Today on one of my conference calls I observed very known situation from my past, and I remembered one example of the lean principle “Eliminate Waste”.
Building the Wrong Thing
“There is nothing so useless as doing efficiently that which should not be done at all.” –Peter Drucker
Today I take a look one interesting presentation about “What is Technical Debt?”. It’s very horrifying to see scissors in somebody’s chest, but it’s not horrifying when IT guys crash a business for million dollars and life of many people just because they are not well prepared to see the creeping disaster!
More than three years I was trying to transfer the jidoka approach from Toyota Production System into the software practices. Finally I find my translation, it’s very simple lean principle “Never Fix Later!”. Under the word “fix” I mean wide definition like fix the bug, make the code clean, refactor the code, redesign the code …