When learning something new, people often try to relate the new information back to something they already know in order to help make sense of the new concept or idea. As a psychology major now working in the software world, I’ve found myself relating a lot of what I’m learning back to the psychological theories and concepts I learned in college. Therefore, it is no surprise that upon reading The Twelve Principles of Agile Software, I’ve discovered that many of their principles map to organizational psych concepts.
Agile development theory approaches software development holistically. I believe this is one of the reasons Agile projects have become so successful. Rather than merely focusing on skill development, Agile methods foster leadership skills and teamwork among members of the development team itself, as well as between the development team, the project owner, and the stakeholders. One avenue for this is to unify the development team and project owner with the common goal of achieving stakeholder satisfaction.
The first principle states, “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” The question I had upon reading this was what do the authors mean by the term satisfaction? When thinking about satisfaction, most people think of outcome satisfaction, or the ultimate outcome of something, in this case the functionality of the delivered software project. Process satisfaction on the other hand, refers to the level of satisfaction associated with the method of developing the software, or how much the stakeholders enjoy the software development process.