Monday, February 19, 2024

What does the 3rd Agile Principle (Frequent Delivery) look like in Action?

Many want to go Agile or claim to be Agile. The question is, are you and will you align with the Agile values and principles? In this article, I expand on the third principle to better understand what it means and attempt to identify what evidence looks like to determine if a culture change may be occurring. What is this principle?  

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale is the third Agile principle. This principle promotes the ability that when customers believe there is value in what is built, it can be immediately delivered. Identifying the elusive customer value means you can release it when the customer wants it. If it is delivered too early, the customer may not be ready for it; if it is too late, the market opportunity is missed. 

Agile thinking includes a fluid world, where changes are continuous welcome, and teams have the capability of releasing frequently. This ability to frequently release, highlights the importance of having processes and infrastructure to help with continuous integration, build, and test. This ability assumes a level of automation that needs to be in place. Automated testing increases the possibility of testing the functionality as is reasonable, including the capability of performing non-functional testing such as performance testing, load testing, and more. 

What actions exhibit frequent delivery?  
  • An established and positive relationship with customers
  • Iterative framework with Sprint Reviews to incorporate feedback quickly 
  • A release capability to incrementally and rapidly deploy software 
  • Continuous integration supported by a merging process and configuration management system 
  • A continuous build process supported by an automated build management system 
  • Test automation infrastructure that can support continuous testing  
It is up to you to determine what supporting evidence will highlight that continuous integration, build, test, and frequent delivery is occurring. It is worth experimenting with this as it will help you better understand and embrace the Agile principles. The ultimate question, do you really believe in the principle that focuses on frequent delivery?


To learn more about what the Agile Principles look like in Action, consider reading:

1 comment:

  1. Discussing in real-life scenarios always brings forth a rich tapestry of experiences and insights. It's a methodology that thrives on adaptability, iteration, and collaboration. The "crystal methodology," as explored in depth in a recent article on DevCom's tech blog, introduces a nuanced approach to Agile development, emphasizing team dynamics, communication, and flexibility. In practical terms, Agile Scrum teams navigate challenges by breaking down projects into manageable chunks and following iterative cycles, leveraging key ceremonies like sprint planning and retrospectives. Integrating insights from the crystal methodology adds depth to Agile Scrum, encouraging teams to prioritize communication, trust, and adaptability. In conclusion, Agile Scrum in real-life projects is a journey marked by collaboration, iteration, and learning, where combining methodologies like crystal with Scrum's core principles enables teams to navigate challenges with confidence and deliver exceptional results.