• Tag Archives value
  • Reflections On Blogging – Year One Complete

    Posted on by Tim

    For me, blogging each weekend nearly one year ago. The action to do it was inspired by my move to Improving. This post covers my reflections on blogging regularly.

    Done is greater than perfect.

    Each blog post on LinkedIn came with risk. In my mind, there are a lot of questions around how posts would be received.

    • First, would people view them?
    • Second, then read them?
    • Third, would people comment on them?
    • Fourth, then share them?
    • Finally, will the posts be valued?

    As a result, I can’t say I’m content. I am focused, like my post on Scrum value #2, but definitely not comfortable.

    Reflections on blogging

    As I write, I become more aware of what I don’t know.

    My new LinkedIn profile banner
    My old LinkedIn profile banner

    By sharing my views, I open myself up to critics. As well, I open myself up to learning.

    Blogging puts me back into the competition instead of sitting in the stands, observing others expressing their own understanding and views.

    Most of my posts don’t go viral. I rarely see more than 1,000 views on LinkedIn. I see even fewer views on this blog.

    That doesn’t stop me from sharing. By failing, I’ve learned what not to do. I’ve learned how to hurt and offend people.

    As a result, I’m not proud of my learning. I am willing to share it to help others act and choose a different path.

    I have a video posted on this blog that speaks to heroes, trauma, and finding “normal”.

    For me, blogging allows me to share the scars I earned in life. To help people understand each other and extend kindness.

    If blogging only positively impacts one person’s life, then my sharing has done what it was intended to do.


  • Agile Principle #1 – Highest Priority To Deliver Delight

    Posted on by Tim

    Part 1 in a 12-part series. This post covers continuous delivery.

    The first principle;

    Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

    Principles behind the Agile Manifesto

    For this series, think of software as products and services. Customers will not pay for crappy products and services, unless they perceive value.

    That might come as a shock.

    Allow me to provide a comparison. One of the first cars I was allowed to drive is shown below.

    Toyota Tercel Wagon

    One of the first cars I chose to buy is also shown below.

    Buick Regal Coupe

    For me, the better value was the Buick. It didn’t matter that the Toyota was a better quality product. At 16 to 17 years-old, I wanted a car that girls would ride in!

    Deliver Continuous Value

    Let’s redefine the conversation to cover more than just software. I suggest that we look at products and services based on value. Customers care about value and we have to as well.

    How do we get to continuous delivery of value? Look at Agile Value #1; Individuals and Interactions.

    First, we talk with customers and get their thoughts on value. Next, we create a small sample of what we understand from the conversation. If the sample doesn’t match the customers understanding, we fix it until we get is right. Finally, we adjust and scale to a viable product and service customers will buy based on value.

    Yeah, this is a simplified process. No disagreement on that feedback.

    What matters is the continuous delivery. Conditions will change. Preferences will change. As long as discussions are frequently happening with customers, we can deliver value and adjust as needed.

    This principle is uncomfortable to accept. I struggle with it because I want our team’s products and services to be perfect. The work done doesn’t need to be perfect, just have value the customer pays for.

    Principle 1, Principle 2, Principle 3, Principle 4, Principle 5, Principle 6, Principle 7, Principle 8, Principle 9, Principle 10, Principle 11, Principle 12