Skip to content

Progress with imperfect information

Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.

Learn more about Software Architecture & Design.
Join thousands of developers getting weekly updates to increase your understanding of software architecture and design concepts.

While I was attending Agile & Beyond last year, David J. Anderson did a great keynote on “stop doing agile, start thinking agility”.  In that keynote he said something that has stuck with me: Making progress through imperfect information. There seems to be a stigma with refactoring.  It might not be refactoring, but getting it right the first time mentality.  We want to create the right solution and fear making the wrong decision because we don’t have all the information we think we need. Make progress with imperfect information and refactor later when more is known or wait for better information?  I believe the best option is to deliver working software earlier.  This now leads into Continuous Delivery… maybe a post in the future. Remember, you can only make a decision based off of the information you have at that moment.  Is it possible that you will see a flaw in your decision and have to refactor? Of course, but embrace change!  

Leave a Reply

Your email address will not be published. Required fields are marked *