8 Best Practices To Reduce Technical Debt

When past actions in software development return to haunt you…

Is your business being bogged down by technical debt? Let’s look at measures that you can take to reduce it and scale your operations without the weight pulling you back. 

 

Work with a flexible architecture.

Right from the word go, you want to use architecture whose design is malleable, especially with the rapid rate of software evolution witnessed today. Going with an architecture that keeps calling for too much refactoring, or whose design won’t accommodate future changes will leave you with costly technical debt. Use scalable architecture that allows you to modify or add new features in future releases. While on this, complex features required in the final product should be discussed at the planning stage, that way simplified solutions that will be easier to implement can be identified, as this will lead to less technical debt in the long run. 

 

The Deal with Refactoring 

This is basically cleaning up the code structure without changing its behaviour. With the updates, patches, and new functionalities that are added to the systems and applications, each change comes with the threat of more technical debt. Additionally, organisations are increasingly moving their IT infrastructure from on-premises facilities to colocation data centres and deploying them on the cloud. In such scenarios, some workarounds are often needed to enable the systems to function in the new environments, which they hadn’t been initially developed to accommodate. Here, you will need to take some time to refactor the existing system regularly, streamlining the code and optimizing its performance – and this will be key to pay down the tech debt. When working with a flexible architecture from the start, the amount of work that goes into this will be reduced, meaning there’ll be less tech debt involved. 

 

Run discovery tests

Discovery testing essentially takes place even before a line of code is written for the system or application. This takes place at the product definition stage, where human insight software is used to understand the needs of the customer and is particularly helpful in setting priorities for the development work that will be carried out. It gives your business the opportunity to minimize the technical debt by allowing customers to give you a roadmap of the most pertinent features desired from the product. 

 

Routine code review

Getting a fresh look at the product or application from different sets of eyes in the development team will improve the quality of the code, thus reducing technical debt. There’s a catch though – this should be planned in a convenient way that doesn’t end up becoming a burden for the developers. Here are suggestions:

● Break down pull requests

Instead of having complex pull requests where numerous changes in the code are introduced at a go, have this broken down into smaller manageable pull requests, each with a brief title and description about it. This will be easier for the code reviewer to analyse. 

● Define preferred coding practices

Documenting the preferred coding style will result in cleaner code, meaning the developers will focus their effort on reviewing the code itself, not losing time on code format debates.

 

Test automation

Relying only on scheduled manual testing opens you up to the risk of technical debt accruing rapidly, and not having sufficient resources to deal with the accumulated problems when they are identified. Automated testing on the other hand enables issues to be uncovered quicker, and with more precision. For instance, you can have automated unit tests that look at the functioning of the individual components of a system, or regression testing where the focus is on whether the code changes that have been implemented have affected related components of the system. However, establishing and maintaining automated testing will require quite some effort – making it more feasible for the long-term projects.

 

Keep a repository that tracks changes made

Do you have a record of changes made in the software? Keeping one in a repository that is accessible by the development team will make it easy to pin-point problems at their source. For instance, when software is being migrated to a new environment, or legacy software is in the process of being modernised, you will want to have an accurate record of changes that are being introduced, that way if there is an undesired impact on the system this it will be easier to zero-down on the cause.

 

Bring non-technical stakeholders on board

Does this conversation sound familiar?

Development Team: “We need to refactor the messy code quickly”

Product Team: “We have no idea what you are saying”

On one hand, you have the management or product team defining the product requirements, creating a project roadmap, and setting its milestones. On the other hand, there’s the software development/engineering that’s primarily focused on the product functionality, technical operations and clearing the backlog in code fixes. Poor communication between the two teams is actually a leading cause of technical debt.

For you to take concrete steps in managing your technical debt, the decision-makers in the organisation should understand its significance, and the necessity of reducing it. Explain to them how the debt occurred and why steps need to be taken to pay it down – but you can’t just bombard them with tech phrases and expect them to follow your thought process. 

So how do you go about it? Reframe the issues involved with the technical debt and explain the business value or impact of the code changes. Basically, the development team should approach it from a business point of view, and educate the management or production team about the cost of the technical debt. This can include aspects such as expenses in changing the code, salaries for the software engineers especially when the development team will need to be increased due to the workload piling up, as well as the revenue that is lost when the technical debt is allowed to spiral. 

The goal here is to show the management or production team how issues like failing to properly define the product requirements will slow down future software development, or how rushing the code will affect the next releases. That way, there will be better collaboration between the teams involved in the project. 

 

Allocate time and resources specifically for reducing technical debt

With management understanding that working with low-quality code is just like incurring financial debt and it will slow down product development, insist on setting time to deal with the debt. 

For instance, when it comes to the timing of application releases, meetings can be conducted to review short- and longer-term priorities. These meetings – where the development team and product team or management are brought together, the developers point out the software issues that should be resolved as a priority as they may create more technical debt. Management then ensures that budgets and plans are put in place to explicitly deal with those ongoing maintenance costs.

 

Retire old platforms

While most of the resources are going into developing new applications and improving the systems being used, the organisation should also focus on retiring the old applications, libraries, platforms, and the code modules. It’s recommended that you factor this into the application release plans, complete with the dates, processes and costs for the systems involved. 

 

Total overhaul

When the cost and effort of dealing with the technical debt far outweighs the benefits, then you may have to replace the entire system. At this tipping point, you’re not getting value from the technical debt, and it has become a painful issue that’s causing your organisation lots of difficulties. For instance, you may be dealing with legacy software where fixing it to support future developments has simply become too complicated. The patches available may only resolve specific issues with the system, and still leave you with lots of technical debt. Here, the best way out is to replace the system in its entirety. 

 

Final thoughts

Every software company has some level of tech debt. Just like financial debt, it is useful when properly managed, and a problem when ignored or allowed to spiral out of control. It’s a tradeoff between design/development actions and business goals. By taking measures to pay down your organization’s debt and address its interest as it accrues, you will avoid situations where short term solutions undermine your long-term goals. This is also key to enable your business to transition to using complex IT solutions easier, and even make the migration between data centres much smoother. These 8 measures will enable you to manage your technical debt better to prevent it from being the bottleneck that stifles your growth.

Check our similar posts

Technology and process improvement

Tightening organisational flow to improve productivity and minimise costs is a growing concern for many businesses post the Global Financial Crisis. Businesses can no longer afford to waste time and personnel on inefficient processes. Organisations using either Six Sigma or Lean techniques better manage their existing resources to maximise product out-put. Both of these techniques involve considerable evaluation of current processes.

What is Six Sigma?

Six Sigma is an organisational management strategy that evaluates processes for variation. In the Six Sigma model, variation equates waste. Eliminating variation for customer fulfilment allows a business to better serve the end-user. In this thought model, the only way to streamline processes is to use statistical data. Each part of a process must be carefully recorded and analysed for variation and potential improvements. The heart of the strategy embodied by Six Sigma is mathematical. Every process is subject to mathematical analysis and this allows for the most effective problem solving.

What is a Lean Model?

Lean businesses do not rely on mathematical models for improvement. Instead, the focus is on reducing steps in the customer delivery cycle, which do not add value to the final deliverable. For example, maintaining excess inventory or dealing with shortages would both be examples of waste behaviour. Businesses that operate using Lean strategies have strong cash flow cycles. One of the best and most famous examples of Lean in action is the Toyota Production System (TPS). In this system, not only is inventory minimised, but physical movement for employees also remains sharply controlled. Employees are able to reach everything needed to accomplish their tasks, without leaving the immediate area. By reducing the amount of movement needed to work, companies also remove wasted employee time.

Industry Applications for Lean and Six Sigma

Lean businesses reduce the number of steps between order and delivery. The less inventory on hand, the less it costs a business to operate. In industries where it is possible to create to order, Lean thinking offers significant advantages. Lean is best utilised in mature businesses. New companies, operating on a youthful model, may not be able to identify wasteful processes. Six Sigma has shown its value across industries through several evolution’s. Its focus on quality of process makes it a good choice for even brand new businesses. The best use is the combination of the two strategies. With the Lean focus on speed and the Six Sigma focus on quality combined, the two organisational processes create synergy. By itself, Lean does not help create stable, repeating success. Six Sigma does not help increase speed and reduce non value-added behaviours. Combined, these two strategies offer incredible value to every business in cost savings.

Using Technology to Implement Lean Six Sigma

Automation processes represent an opportunity for businesses to implement a combination of both Lean and Six Sigma strategies. Any technology that replaces the need for direct human oversight reduces costs and increases productivity. A few examples of potentially cost saving IT solutions include document scanning, the Internet, and automated workflow systems.

  • Document Scanning – Reducing dependency on paper copies follows both Lean and Six Sigma strategies. It is a Lean addition in that it allows employees to access documents instantly from any physical location. It is Six Sigma compliant in that it allows a reduction on process variation, since there is no bottleneck on the flow of information.
  • The Internet – The automation potential offered by the Internet is limitless. Now, businesses can enter orders, manage logistics and perform customer service activities from anywhere, through a hosted portal. With instant access to corporate processes from anywhere, businesses can manage workflow globally, allowing them to realise cost savings from decentralisation.
  • Automated Work Systems – One of the identified areas of waste in any business is processing time. The faster orders are processed and delivered, the greater the profits for the company and the less the expense per order. When orders sit waiting for attention, they represent lost productivity and waste. Automated work systems monitor workflow and alert users when an item sits longer than normal. These systems can also reroute work to an available employee when the original worker is tied up.

Each of these IT solutions provides a method for businesses to either reduce the number of steps in a process or improve the quality of the process for improved customer service.

Identifying Areas for Lean Six Sigma Implementation

Knowing that improved processes result in improved profits, identifying areas for improvement is the next step. There are several techniques for creating tighter processes with less waste and higher quality. Value Stream Mapping helps business owners and managers identify areas of waste by providing a visual representation of the total process stream. Instead of improving single areas for minimal increases in productivity, VSM shows the entire business structure and flow, allowing management to target each area of slow down for maximum improvement in all areas.

Seeing the areas of waste helps management better determine how processes should work to best obtain the desired outcomes. Adding in automated processes helps with improved process management, when put in place with a complete understanding of current systems and their weaknesses. Start with mapping and gain a bird’s-eye view of the situation, in order to make the changes needed for improvement.

Contact Us

  • (+353)(0)1-443-3807 – IRL
  • (+44)(0)20-7193-9751 – UK
7 Challenges Facing Mobile Field Service ? And Overcoming them with FSM Solutions

Managing a mobile workforce comes with its set of challenges. There are multiple coordination levels, administrative hurdles when distributing tasks amongst your employees, the need to meet your customers? expectations, whilst still operating profitably. Your goal is to rake in more revenue, while striking a balance between the number of employees and the quality of the service being rendered. Under utilisation of the company resources may be misinterpreted to mean that you need more employees- which will affect your bottom line. Repeat visits with older jobs affect the response time for new client appointments. Clients get frustrated when their needs are not met on time. Remember that, for your client, their priority is getting their issue sorted- be it that pipe leak, electrical fault, damaged gas valve, or window installation completed on time. Administrative challenges on your end will simply come off as excuses, costing your brand dearly. The different fields share similar challenges- from utility firms, pest control, installation and repair services such as with plumbers and electricians, those running residential and commercial window cleaning companies, to property managers in charge of different buildings. Here are some of the obstacles faced:

1. Coordinating your team

Running things from the office can get hectic when your technicians are out on ground, and clients are at different locations. From appointments being delayed because the workers met traffic on their way, those calling in sick and requiring you to find replacements on short notice, clients who cancel appointments without notice- they all present a logistical nightmare. There is also the need to have a skill-based task distribution in place. Here, the focus is on getting the right technician for the job, not someone who has simply “dealt with it before as they helped their colleagues on a similar job“. With your firm having different personnel, you want to ensure that you spend the most appropriate technician to your client. This also aids the employees themselves, by increasing their morale as they will be dealing with tasks that they are particularly adept at, score you a high first-time fix rate, and avoid having to do follow up visits to resolve issues that were not properly addressed the first time round. 

Capterra undertook a field service software survey, which showed that 82% of organisations adopting FSM solutions saw an increased rate of first-time fixes, and a 90% rise in actual conversations from quotes.

Capterra

How field service job management software impacts businesses. Source: Capterra

 Follow-ups tend to cost extra with the additional dispatch, and take away your fiend agents from the work that had been scheduled to be handled. Resolving these logistical issues with traditional approaches can be problematic, especially with all the paperwork involved. In fact, let’s delve into that.

2. Mounds of paperwork

Having loads of data streaming in from your field workforce can put one on edge. Organising the documents, creating the spreadsheets and typing away at calculators, sorting the files in cabinets and the stress that comes when a single file appears lost in the heaps of sheets – it creates a bottleneck for your operations.  Manually handling the data at the central office also compromises on the accuracy of the process due to human error, from syntax issues when transferring information, incorrect inputs, to duplicate errors- which is expected to occur with increased frequency due to the tiring nature of the process. Actually, 46% of the respondents surveyed by the Service Council said that paperwork and admin work was the worst part of their day.

The field worker is also affected by the paperwork. From having to come to the office each morning to collect the documents needed for the day, walking with the bulky files from one site to another, perusing through lots of sheets whenever they want mire information about a particular customer or the job description- and the frustration that comes when some documents have been forgotten back at the office- it hampers productivity. Running out of copies of paper will also be unavoidable when your staff are away from the office- and more time will be spent coming back to restock. There are also additional issues like the forms getting soiled or torn, and even the wind blowing them away as your technicians are out in the field.  Dealing with the contracts, collecting signatures for each job that is handled, jotting down notes concerning the particular tasks that they are taking care of- it increases the workload. In fact, this often results in errors in data entry, and jobs being poorly documented.

Fortunately, this doesn’t have to be the case for your firm. Technological advancements have seen solutions being developed to minimise the paperwork involved. These mobile service management software allow the field worker to access all the details of the job via handy apps on their smartphones and tablets- as is the case with FieldElite. Instead of walking around with the documents and files, the information is stored via cloud, and is accessible in real-time. The job documentation- from photos, notes to the customer?s e-signature are all collected through the app, and the information is securely stored and immediately available to the personnel back at the head office. 

Service analytics- where you get to observe product demand, performance of your workforce and analyse your customer base growth through the dashboard reporting modules that come with the FMS software is a key tool for decision makers of the company. You get to optimise your performance without having to resort to adding more work hours, or pushing your employees into overtime. Field service analytics has been shown to increase profitability for leading companies by 18%, going by the ?Get Smart: Business Intelligence and Analytics for Service Organizations? study done by Aberdeen Group.

3. Scheduling conflicts

First, there are multiple jobs that need to be attended to- and disappointing your clients will lead to backlash. Secondly, you have a large team of workers- and you want to optimise on their productivity at an individual level. From an administrative perspective, you are also required to provide proper work structures that incorporate your employees? safety during the jobs being handled- and not to run them like mules, overworking them in a bid to hit your targets. Thirdly, the workers have different individual hours of operations- or they work in shifts. Running all this from a central point, allocating the jobs as needed and managing the different schedules, can be a tall order without the right field service scheduling software.

When your customers book an appointment, they expect that your company will deliver on its mandate, providing the services that they are paying you for as required. On the other hand, as the company, you are relying on your employees to meet those expectations. This means that you should have structures in place to ensure that your field workers stick to their assigned schedules. For this you will need to know their location in real-time, track their performance, and check on their adherence to the set schedules. Working with field service job management software allows you to handle the logistics of every task from one dashboard. By tracking your technicians while they are out in the field, you will be able to allocate orders faster, monitor the incoming customer requests, and manage the task distribution more efficiently. When you have an FSM that allows your workers to coordinate with the head office via mobile app, there will be an increased rate of job completion, and a reduction in overtime. Both your clients and employees get to be happy at the end of the day.

4. Lonely workers

Working in the office has its perks. You are surrounded by your colleagues, and can easily get the attention of anyone in management if needed. However, while out in the field, the workers can feel disconnected from the company structure, left to their devices while still bearing the responsibility of presenting the company in positive light- as they also double up as your brand ambassadors. The loneliness can get to them, with a report by the Service Council showing that isolation was the worst part of the work day for 21% of technicians. The chat feature that comes with the mobile service management software apps is one of the reasons behind their popularity, keeping the employees connected to the rest of the manager at the central office, and even other field employees- which makes them feel as part of one large family.

Safety is also a concern, especially for cases where your field staff will be working in hazardous situations – like conducting repairs on top of radio towers, dealing with gas equipment in concealed spaces. The central office needs to remain in constant communication with the workers, and have the appropriate structures in place to handle emergencies. You don’t want to lose employees because they don’t feel that their safety is a priority to you. A skilled technician is an asset that should be protected- and certainly you wouldn’t want to incur extra funds to hire and train personnel- which will end up being an additional strain to your budget over time. Field service job management software with features that allow your employees to check-in remotely via app will be handy in notifying the head office of their arrival at the job site, and in case of any incident, the field manager can quickly see the employees? last location, and dispatch help to them. 

5. Difficulty in assessing performance metrics

When you have a situation where timesheets are only handed in after the workday- and in some cases at the end of the week, it becomes difficult to assess the level of productivity of your field workers. Are you getting value for your money with the wages that are being paid out? Are there lots of lost work hours due to logistical hitches- or cases where the field worker delay the tasks, or take out sections of their day to attend to matters of personal interest- and still bill you for it? All this translates to poor customer service, with issues ranging from cancelled and rescheduled appointments, unmet targets, disagreements based on the scope of work being handled, to client dissatisfaction for not having their issues addressed in a timely manner- which becomes a hit on your brand.

FSM comes in to enable the field service manager to always be in the loop during the entire process- knowing exactly how long the workers are spending on each particular task, the jobs that are pending, cancelled or rescheduled, in order to constantly review and optimise the planning of the firm?s activities. With software like FieldElite, you even get a birds-eye view, as the work areas are mapped out, that way you will be in a position to direct your field workers on aspects like the best routes to take to avoid traffic gridlocks.

6. The break factor

How do you plan for breaks? Jobs are different, and there will be unexpected issues cropping up regularly. However, the field worker is still entitled to breaks during the working day- such as the all-important lunchtime. The problem arises when there is unextended time on some job sites, and cases of unscheduled breaks being taken. These have a ripple effect, as they will cause delays on other projects that are on queue, and you can also expect customer complaints to be coming in hot and hard. From a management point of view, you want to have the ability to respond to the issues as they arise, and reassign the jobs accordingly. Mobile service management software gives you this power.

7. Customer relationship management

Customers want to be part of the process, staying in the loop with the service appointments that have been scheduled- and understandably so. From the booking process, to following up on the progress of the job- it all factors in. In case there are issues that crop up- like service vehicles being delayed, situations where extra parts need to be ordered, or the session cancelled and scheduled on a different day- being fully transparent with your customers will be a great boost to your brand. Gaining new clients and retaining the current ones requires the firm to maintain a quality customer service.

Negative feedback because of your customers? feeling neglected will be a setback for your business. Integrating the customer relationship management into the field service will go a long way in enhancing their experience. Here, software solutions like FieldElite have also got you covered with a customer self-serve portal, accessible online through their browsers. This has the welcome benefit of reducing the number of calls as they conduct follow-ups, since they will be in a position to track the project right from the comfort of their homes and office desks, thus increasing customer satisfaction.

Are Master Data Management and Hadoop a Good Match?

Master Data is the critical electronic information about the company we cannot afford to lose. Accordingly, we should sanitise it, look after it, and store it safely in several separate places that are independent of each other. The advent of Big Data introduced the current era of huge repositories ?in the clouds?. They are not, of course but at least they are remote. This short article includes a discussion about Hadoop, and whether this is a good platform to back up your Master Data.

About Hadoop

Hadoop is an open-source Apache software framework built on the assumption that hardware failure is so common that backups are unavoidable. It comprises a storage area and a management part that distributes the data to smaller nodes where it processes faster and more efficiently. Prominent users include Yahoo! and Facebook. In fact more than half Fortune 50 companies were using Hadoop in 2013.

Hadoop – initially launched in December 2011 ? has survived its baptism of fire and became a respected, reliable option. But is this something the average business owner can tackle on their own? Bear in mind that open source software generally comes with little implementation support from the vendor.

The Hadoop Strong Suite

  • Free to download, use and contribute to
  • Everything you need ?in the box? to get started
  • Distributed across multiple fire-walled computers
  • Fast processing of data held in efficient cluster nodes
  • Massive scaleable storage you are unlikely to run out of

Practical Constraints

There is more to Hadoop than writing to WordPress. The most straightforward solutions are uploading using Java commands, obtaining an interface mechanism, or using third party vendor connectors such as ACCESS or SAS. The system does not replace the need for IT support, although it is cheap and exceptionally powerful.

The Not-Free Safer Option

Smaller companies without in-depth in-house support are wise to engage with a technical intermediary. There are companies providing commercial implementations followed by support. Microsoft, Amazon and Google among others all have commercial versions in their catalogues, and support teams at the end of the line.

Ready to work with Denizon?

Contact Us Today