#systematic reuse

A lot of teams are building services for clients both internal and external to your organization. Typically, there is quite a bit of focus on succeeding from a functional sense – did we get the key requirements addressed? does it cover the plethora of rules across markets / jurisdictions? and so on. Some of the more experienced teams, consider the non-functional aspects as well – e.g. logging,…

Systematic reuse takes conscious, disciplined effort – question is – where are the systematic reuse opportunities? how can we maximize these opportunities? – it may or may not surprise you that there is rarely a special, designated ‘project’ to achieve reuse or build a reusable API. Teams are busy and they want to solve tangible problems – they work on projects more often than reusable libraries…

Don’t Implement Reusable Assets Unless Necessary

Resisting the temptation to implement a story is very hard for a dev team – it is all too easy to get carried away in introducing a new idea as a reusable asset. However, these are the moments where you must pause and ask yourself a few basic questions before rushing to write code:

Is this a one-off requirement or part of a recurring theme? Remember – when in doubt, don’t plan for reuse but…

Getting Developer Buy-in for Systematic Reuse

Too many systematic reuse initiatives fail because they fail to get heir most important constituency. Below are a few tips to get developers to buy into reuse efforts.

Make every design and implementation artifact available for active engagement and feedback. If you say something must be used as a mandate – make sure your developers can actually use and benefit from that capability. This isn’t…

There are certain key interception points during the development process that can greatly increase the likelihood of systematic reuse. Some agile practices can really help:

Estimating User Stories – constantly seek synergies and ways to connect new…