Sharing Our Passion for Technology
& Continuous Learning
  • Teammates talking at desk with laptop

    The Day-to-Day Proof of Concept

    In the software world, there are often new technologies coming to market, new fields to explore, new techniques to use, etc. Filtering through these in itself can be a challenge. Deciding when to move forward with one in practical applications can be even harder. Many times as developers, we will...
  • default icon


    One of the tenets of the agile methodology is feedback. To provide value to your customer, you need to know that what you are delivering is correct. But as an agile coach, I often struggle with teams understanding the importance of getting feedback from the customer as soon as possible....
  • default icon

    A Better Analogy for Agile Software Development?

    For years, like many of you, I have been comparing software development to construction. But ever since adopting the agile methodology a decade ago, I have been looking for a better analogy to help me explain agile software development. I recently came up with what I think is that analogy...
  • default icon

    Pain Driven Learning

    I find that in software development, and also in life, people learn best within the context of painful experiences. I’m not suggesting that software development mentors go out of their way to create painful experiences for their teams. On the contrary, just start listening. It doesn’t take very long to identify...
  • default icon

    Agile Iowa No Estimates Puzzle Experiment

    I facilitated my own rendition of the #NoEstimates Puzzle Experiment for the September 2013 Agile Iowa user group meeting. This experiment was created by Chris Chapman to generate critical thinking and conversation concerning whether estimates are necessary to produce quality software. The meeting had a great turnout, with around 40...
  • default icon

    Pragmatic Application of Principles

    I was reminded of a profound truth as I was re-reading Robert C. Martin’s book “Agile Software Development, Principles, Patterns, and Practices”, in C# this time. It is not wise to apply (a) principle ... if there is no symptom. In this section Uncle Bob discusses the Single Responsibility Principle...
  • default icon

    What you missed at Agile 2013

    I was able to attend the Agile 2013 conference in Nashville, TN earlier this month. I had previously attended Agile 2006 in Minneapolis, MN. There was a significant difference. At this year’s conference, the overall theme seemed to be that teams needed to focus on producing value rather than following...
  • default icon

    Agile Manifesto - Responding to Change Over Following a Plan

    Is it really possible that intense planning and the ability to respond to change can co-exist within the same development process? If you are wondering this, then you are not alone. Partners regularly ask us if Agile software development teams follow any sort of plan or are they just feel...
  • default icon

    Agile Manifesto - Customer Collaboration Over Contract Negotiation

    Do you ever wish that companies would trust their employees and business partners instead of insulating themselves with contracts and policies?  For many companies, each discipline operates out of its own department requiring other areas to document exactly what they want and what they are going to do.  This provides...
  • default icon

    ThoughtWorks releases ebook on Agile Project Estimation

    ThoughWorks Studios has released an ebook titled “How do you estimate on an Agile project?” where they explore common approaches and their adaptions from real-world projects.  The book is comprised of several authors, most notably Martin Fowler. In this ebook they discuss why teams estimate, different methods that teams use...

Looking for leading technology experts to accelerate delivery?

Start a Conversation