develpreneur podcast
Posted on The Agile Manifesto

Working Software Over Comprehensive Documentation

We started this season with a focus on satisfying the customer.  Since then, we have built a case for working software being the best way to achieve satisfaction.  Thus, comprehensive documentation is valuable.  However, not as useful to our primary goal.  Agile is often painted as anti-documentation so let’s dig deeper into this comment that could be used as evidence. …Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation We Value X Over Y The opening section of this summary says we value all of the listed items.  Rating one over the other does not mean the lesser has no value.  For example, you prefer breathing over food.  Would you argue... Read more

develpreneur podcast
Posted on The Agile Manifesto

Individuals and Interactions Over Processes And Tools

We shift slightly in our tour of the Agile Manifesto to focus on the opening statements.  In this episode, we dig into the value of individuals and interactions while acknowledging processes and tools.  The essential point in these opening statements is that all of these are valuable.  However, we find some to have more value than others.  This valuation should help us decide on how to make decisions and move forward with a project. We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools A Slave To Your Tools There is a well-known bit of wisdom that says when you... Read more

develpreneur podcast
Posted on The Agile Manifesto

Twelve Principles of the Agile Manifesto

We take a look at overall ideas from the twelve principles of the Agile Manifesto before moving on.  There are some challenging concepts mixed in among recommendations that are very common.  All of these can be applied in areas other than software development. Likewise, their efficacy is seen there as well. We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. The Twelve Principles When we look at these observations and recommendations, there are themes that appear.  We also can see how software projects relate to projects in other areas or lines of business.  There are foundational concepts of a good team, working together, buy-in, and communication.  Some of the... Read more

develpreneur podcast
Posted on The Agile Manifesto

Reflect on How To Become More Effective, Then Tune And Adjust

The final principle of the Agile Manifesto directs us to reflect on a project.  We follow those eleven principles and then evaluate how we did so we can become more effective.  This recommendation should not be a surprise.  We can only improve when we examine how we did on a task.  However, this principle points to the entire team taking that step. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. The Agile Goal is to Become More Effective We started the twelve principles with a focus on satisfying the customer.  This focus is our “why” for building software.  This final principle presents us with a “why” for using the... Read more

develpreneur podcast
Posted on The Agile Manifesto

Self-Organizing Teams Produce The Best Results – An Agile Principle

We near the end of the focus on the agile principles with a bold statement.  The idea of self-organizing teams producing the best results is a strong position.  They are not merely better; they make the best products.  I tend to agree with this statement.  However, it is worth defending as it is not apparent. The best architectures, requirements, and designs emerge from self-organizing teams. The Value of Buy-In First and foremost, self-organizing teams impart to each member a level of ownership.  They are given the freedom and responsibility to “get the job done.”  This structure implies that the members are trusted to find the best way to solve a problem and provide their input.  It is not different from... Read more

develpreneur podcast
Posted on The Agile Manifesto

Simplicity – Avoid Doing Busywork

Simplicity is an integral part of satisfying the customer.  Ideally, we would provide them a button to click that does everything they want.  However, that is rarely possible.  We build complex systems that require users to select how they want to proceed.  Likewise, we include or exclude features and functions as part of meeting the requirements. Simplicity–the art of maximizing the amount of work not done–is essential. Work Not Done When we think of simplicity, the focus is often on how little we have.  This principle points to what is not included in a straightforward approach.  More importantly, this principle focuses on work not done.  When you think about it that way, simplicity is an essential piece of getting things... Read more