Becoming a Transformational CIO from the Best CIO Blog on the Planet!

Every once and a while I receive recognition and participate in a webinar that's worth sharing here with everyone.

First, I'm very proud that this blog, Social, Agile, and Transformation was recently listed as the #1 blog for CIOs and a top blog on agile software development.

I've been writing on these topics for over a decade here on this blog, on CIO.com, on InfoWorld, and on several other publications. The best way to keep up with all my writing is through the Driving Digital Newsletter which I send monthly with updates on all my writing.
continue reading "Becoming a Transformational CIO from the Best CIO Blog on the Planet!"

How to use Spikes and Deliver Agile POCs

In my last post, I discussed shallow commitments, an agile tool team can use to negotiate with product owners when they are asked to commit to more stories in a sprint above their velocity and comfort zone. Teams commit as usual and then define several stories that sit in the shallows. If the committed stories are finished earlier than expected, then they can pick up new stories from the shallows.

That's one tool development teams can use to make commitments easier. Another one is to use spikes, a way to define a research and development story. Spikes are typically time-boxed and may result in a failure when they are longer or more complex than forecasted. When spikes succeed, then they provide background knowledge to the team to estimate and work on the desired business feature or technical debt improvement.
continue reading "How to use Spikes and Deliver Agile POCs"

@DrivingDig Episode 3: Agility and Rigor Enable Innovation


I'm back to share a mix of tweets on topics that I write about: Agile, DevOps, Digital Transformation, CIO leadership, and AI among others.

Innovation and collaboration are common themes in these tweets and posts!

continue reading "@DrivingDig Episode 3: Agility and Rigor Enable Innovation"

How to Negotiate Sprint Commitment with Product Owners

Negotiating Sprint Commitment
It's that dreaded time again. You've gathered for the sprint commitment meeting and already have a fairly good idea of what the team will be willing to commit. Your velocity is 100 story points per sprint, and over the last three sprints they achieved +/-10% against that target. You're hoping for a 95 point commitment as there is a big meeting this week that will pull the team off task.

Only you know that the product owner is going to hope for a 108 story point commitment. She's aiming to get two more stories done this sprint, one with eight points and the other with five points.

And she'll come with all the right reasons why end-users will want the added improvements sooner. Your team has CI/CD in place but follows a release management standard of 3-sprints for a major release. Continuous deployment wouldn't work for this organization as every release requires some manual testing that can't easily be automated, documentation for SOC-2 compliance, and end-user training that can't be performed more frequently.

continue reading "How to Negotiate Sprint Commitment with Product Owners"

When Should Responsible DevOps Teams Increase Deployment Frequency

In my last few posts, I've been challenging the wisdom that more frequent deployments are better. I've also shared what DevOps teams must consider as prerequisites and processes beyond CI/CD to enable reliable deployments. Consider reading the following posts for more details:


You may also want to read one of my earlier posts where I ask whether continuous deployment is right for your business.

So the question I hope to help you answer today is, what frequency of deployment is best for your business and application? To determine this, consider answering the following questions:

continue reading "When Should Responsible DevOps Teams Increase Deployment Frequency"

7 Required DevOps Practices Before Increasing Deployment Frequencies

In my last post, I shared 7 Prerequisites on Whether to Improve Deployment Frequencies with DevOps. I firmly believe that CI/CD is not enough to support stable releases and also shared 5 pre-deployment priorities for Agile DevOps teams.

Let’s now talk about the technical practices that underpin and are required for more frequent deployments. If your goal is to increase the frequency of releases, here is my POV on DevOps practices that are necessary before agile teams should even consider cranking the speed knob.

continue reading "7 Required DevOps Practices Before Increasing Deployment Frequencies"

7 Prerequisites on Whether to Improve Deployment Frequencies with DevOps

In my last post, I advised that having CI/CD automation is very important to drive frequent and reliable releases, however, it is not a sufficient process or steps to establish responsible releases. When you’re making a production release of an application or service, it requires communication, additional testing, documentation, and other steps that go beyond the scope of what continuous integration and deployment automate.


continue reading "7 Prerequisites on Whether to Improve Deployment Frequencies with DevOps"
Share