Posted by: SJC
Agile, CIO, Software Quality
I’d like to call special attention to one of the written principles contained in the “Agile Manifesto” relating to simplicity, “Simplicity–the art of maximizing the amount of work not done–is essential.” Yes, I agree with this statement. I also think that “feature creep” is a primary foe of simplicity, but that is perhaps for another post.
However, I wonder how many other developers such as I have experienced the “lack of simplicity” in creating software that is ultimately “simple” for the end-user. I don’t think that “simple” for the end-user is necessarily “simple” for the developer…and once again I turn to communication as a key ingredient. I find myself constantly asking the question “What will make this easier for the user?”
Fellow NEDC developer Garret Mott has published an excellent white paper called “Software as a Conversation“. I believe this is excellent reading for developers who are concerned about keeping simplicity in their application program “conversations”. Garret’s perspective in this paper can easily serve as a reminder to developers to perhaps “visualize” themselves as the user when designing.