Skip to main content

Solving technical debt - Aligning the direction

The first step to solving technical debt has to be for the business and technical teams to have a common, agreed direction for the product(s). To determine the right direction, the team will need a 'map' - this is generally the company vision, which should come from the senior management team/board.

Only with a clear direction to measure their progress against, can they be sure that they're all aligned and how far along the path they are. Sure, 'Widget ABC' or 'Product XYZ' might contain lots of technical debt, but with an agreed direction, everyone can identify whether the time spent resolving any debt in a particular area takes them down the right path, or that they should concentrate their efforts elsewhere.

Ask any business (involved in software product development) to list their biggest problems; not having enough capacity to get everything done will probably be right up there. Ask any technical team to list their biggest problems and they'll probably come up with a really long list. There will probably be one hidden/undocumented problem that relates them all - not enough hours in the day (again, capacity) to work on them all. So if capacity is such a limited resource, everyone (on all the teams) needs to make sure that every bit of effort counts!

Without an agreement between the business and technical teams, everything is being left to chance that both teams know what the undiscussed direction is and are in alignment.

There are so many reasons why having an agreed and published direction is a good thing, successfully starting to tackle technical debt being just one of them.

Comments

Popular posts from this blog

Mocking HttpCookieCollection in HttpRequestBase

When unit testing ASP.NET MVC2 projects the issue of injecting HttpContext is quickly encountered.  There seem to be many different ways / recommendations for mocking HttpContextBase to improve the testability of controllers and their actions.  My investigations into that will probably be a separate blog post in the near future but for now I want to cover something that had me stuck for longer than it probably should have.  That is how to mock non abstract/interfaced classes within HttpRequestBase and HttpResponseBase – namely the HttpCookieCollection class.   The code sample below illustrates how it can be used within a mocked instance of HttpRequestBase.  Cookies can be added / modified within the unit test code prior to being passed into the code being tested.   After it’s been called, using a combination of MOQ’s Verify and NUnit’s Assert it is possible to check how many times the collection is accessed (but you have to include the set up calls) and that the relevant cookies have …

Problem installing AWS CLI

It never feels like a good start when you're trying to start out with something and the install fails with an obscure error! I was just trying to install the Amazon CLI following the instructions at https://aws.amazon.com/cli/ and ran into the following error when running 'pip install awscli': Collecting awscli Could not find a version that satisfies the requirement awscli (from versions: ) No matching distribution found for awscli I appeared to have a correct version of Python installed (v2.7) and checking "PIP -v" indicated that 9.0.1 was installed. That all seemed to tick the required boxes but digging around a little more I did see that some people had had issues with various versions of PIP so I found / ran the following to upgrade to the latest vesion: curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py python get-pip.py This installed v9.0.3 of PIP which burst into life when I re-ran 'pip install awscli' and everything seems to be ok. Like…

Injecting HttpContextBase into an MVC Controller

It is a shame that when the ASP.NET MVC framework was released they did not think to build IoC support into the infrastructure. All the major components of the MVC engine appear to magically inherit instances of HttpContext and it’s related objects – which can cause no end of problems if you are trying to utilise Unit Testing and IoC. Reading around various articles on the subject just to get around this one problem requires the implementation of several different concepts and you are still left with a work around. The code below, along with the other links referenced in this article is my stab at resolving the issue. There’s probably nothing new here, but it does attempt to relate all the information needed to do this for Castle Windsor. The overview is that all controllers will need to inherit from a base controller, which takes an instance of HttpContext into it’s constructor. It then overrides the property HttpContext in the main controller class, supplying it’s own version…