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

develpreneur podcast
Posted on The Agile Manifesto

Good Design Enhances Agility

We have mentioned time and again that the goal of agile is satisfying the customer.  However, each principle we explore provides ways to accomplish that goal.  The principle we focus on in this episode reminds us that we are still building software.  There are certain traits any good team or system will have.  Good design and technical excellence are tools for building the best solution. Continuous attention to technical excellence and good design enhances agility. Good Design, Not Good Documentation Some people say that Agile is an approach that avoids documentation and limits design.  Likewise, detractors accuse it of jumping too quickly into implementation.  This principle puts the lie to those accusations.  We can do all manner of good things... Read more

develpreneur podcast
Posted on The Agile Manifesto

A Constant Pace Indefinitely – Measured Development

Software development has high and low points.  Likewise, there are hectic and “slow” times that we live with as part of our work-life.  When you think of software development as a marathon, a constant pace is a goal.  You want to be able to set a pace for the team that they can run at forever.  That allows for critical success factors like embracing change and adjusting to changing requirements. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Sustainable Development Burnout and similar situations are highly detrimental to a plan.  The loss of a resource or team in such an unexpected way causes slippage or maybe even failure.  There... Read more