Posts

Sample article showcasing basic code syntax and formatting for HTML elements.

The key to achieving Continuous Delivery is to focus on shortening every cycle. Continuous Delivery will follow as a natural byproduct. First we start by breaking the coupling between release and deployment. A release means the software is technically ready to be deployed; and the actual decision to deploy should be a business decision, not an engineering bottleneck. Shrink your release cadence stepwise - three months → monthly → weekly - aiming asymptotically toward zero. ...

“Continuous Delivery” has become a catchy term over the years. The real way to make this real for your team is to focus on shortening all of the cycles before it. And then naturally, the delivery will become continuous too. Years ago “Small Releases” meant monthly drops; then weekly, and today our goal is Continuous Delivery: releasing to production after each stable change. Continuous delivery isn’t only about pushing more code more often. It’s about discipline and striving for clearer scope, faster feedback, and shrinking the design, review, test, and deployment cycles. ...

Golden Stories are a small set of well-understood baseline stories that the team agrees to peg with certain point values. These are used as references for future pointing. As the team estimates new stories, they can compare them to the golden stories which act as an established agreed upon baseline. So when a story “Fix a typo in the main menu” arrives the team can compare the new story directly to the golden Stories: “Is this typo harder or easier than the “Login” golden story?”. The team calibrates the estimate and explores and hidden scope or assumptions. ...

A falling velocity usually signals code quality problems - rot - not laziness. Builders avoid refactoring when the test suite is weak, because without tests they fear changing the working code. And that fear slows down delivery. And this mounting pressure leads to story point inflation which props up the recorded velocity score to hide the actual velocity decline. Encourage the team to treat testing and refactoring as first-class work. ...