This post is on the usability of authenticating to a site. Entering your username and password, what could be complicated about that? But, surprisingly, so many sites get it wrong. The “Login Test” is a measure of one specific aspect of logging in. Continue reading
This article is about software design, and makes the case that flexibility for flexibility sake should never be your goal. There is a very delicate balance between design and implementation in order to provide both usability and capability when it comes to software. Flexibility is often held up as a axiom, but flexibility should be provided only to the extend that it is actually needed by the end user. Continue reading
Today’s post is a parable about an unfortunate designer named Pablo who lives in an imaginary universe where physical (construction) projects are like software projects in our universe. Pablo is frustrated by helpers who don’t understand the principle of “Design for the User”. Continue reading
This morning I was interviewed about being a software architect from the point of view of the general public. I have copied the questions and the (raw) answers here. Continue reading
Now that we have determined that BPM is not Dead, discussion has turned in a big way to whether BPM should be redefined. Steve Towers hosted a very long discussion of this on his BP Group on Linked In, with over a hundred comments. A lively discussion, all over the map. Peter Shooff at eBizQ todays asks the question, how would you redefined it. Continue reading
Last Wednesday I got a full scale indoctrination into the agile software development methodology called Kanban, loosly based on the Toyota Production System (TPS) mechanism with the same name. Toyota uses the kanban as a mechanism to allow for just the right amount of parts to be ordered and to be delivered just in time (JIT) in order to avoid overproduction and waste in the production line. Kanban Software Development Methodology (KSDM) brings the same lean ideas to a development team. Continue reading
This button in this situation produces an error report … therefor the button should be disabled.
I question this line of reasoning. I have observed this reasoning used at all levels, from programmers, to UI designers, to Product managers, and even to customers (users) themselves. The goal seems to be “protect the user from error messages”. Some people naively think Continue reading
Taiichi Ohno is credited with the creation of the Toyota just-in-time production system, and his book “Toyota Production System: Beyond Large Scale Production” is a surprisingly good read even today when many of these principles are considered well established.
My interest was in understanding how this philosophy applies to Agile/Lean Software Development. Continue reading
I collect nuggets of wisdom on various topics. Recently I have been going over the topic of Agile software development; what really matters? Below is a list of 26 key principles to guide an agile software development team.
- Get case 1 fully working before starting case 2. Another way of saying this to use a kitchen metaphor is: “Serve the current meal before starting to cook the next“. Continue reading
A lot of the confusion and difficulty in the BPM community is because some people think that BPM is a kind of Software Engineering.
Update: Please reference the post: One Common Definition for BPM where BPM is clearly a practice of a manager who assesses and improves the process for an organizational unit. It is not the development of the application that support activity. This post originally written in 2008, we find that even in 2014 there is still confusion on this point. Continue reading