How DevOps oils the Value Chain

DevOps ? a clipped compound of development and operations – is a way of working whereby software developers are in a team with project beneficiaries. A client centred approach extends the project plan to include the life cycle of the product or service, for which the software is developed.

We can then no longer speak of a software project for say Joe?s Accounting App. The software has no intrinsic value of its own. It follows that the software engineers are building an accounting app product. This is a small, crucially important distinction, because they are no longer in a silo with different business interests.

To take the analogy further, the developers are no longer contractors possibly trying to stretch out the process. They are members of Joe?s accounting company, and they are just as keen to get to market fast as Joe is to start earning income. DevOps uses this synergy to achieve the overarching business goal.

A Brief Introduction to OpsDev

You can skip this section if you already read this article. If not then you need to know that DevOps is a culture, not a working method. The three ?members? are the software developers, the beneficiaries, and a quality control mechanism. The developers break their task into smaller chunks instead of releasing the code to quality control as a single batch. As a result, the review process happens contiguously along these simplified lines.

Code QC Test ? ? ?
? Code QC Test ? ?
? ? Code QC Test ?
? ? ? Code QC Test
Colour Key Developers Quality Control Beneficiary

This is a marked improvement over the previously cumbersome method below.

Write the Code ? Test the Code ? Use the Code
? Evaluate, Schedule for Next Review ?

Working quickly and releasing smaller amounts of code means the OpsDev team learns quickly from mistakes, and should come to product release ahead of any competitor using the older, more linear method. The shared method of working releases huge resources in terms of user experience and in-line QC practices. Instead of being in a silo working on its own, development finds it has a richer brief and more support from being ?on the same side of the organisation?.

The Key Role that Application Program Interfaces Play

Application Program Interfaces, or API?s for short, are building blocks for software applications. Using proprietary software-bridges speeds this process up. A good example would be the PayPal applications that we find on so many websites today. API?s are not just for commercial sites, and they can reduce costs and improve efficiency considerably.

The following diagram courtesy of TIBCO illustrates how second-party applications integrate with PayPal architecture via an API fa?ade.

Working quickly and releasing smaller amounts of code means the OpsDev team learns quickly from mistakes, and should come to product release ahead of any competitor using the older, more linear method. The shared method of working releases huge resources in terms of user experience and in-line QC practices. Instead of being in a silo working on its own, development finds it has a richer brief and more support from being ?on the same side of the organisation?.

imgd2.jpg

The DevOps Revolution Continues ?

We close with some important insights from an interview with Jim Stoneham. He was general manager of the Yahoo Communities business unit, at the time Flickr became a part. ?Flickr was a codebase,? Jim recalls, ?that evolved to operate at high scale over 7 years – and continuing to scale while adding and refining features was no small challenge. During this transition, it was a huge advantage that there was such an integrated dev and ops team?

The ?maturity model? as engineers refer to DevOps status currently, enables developers to learn faster, and deploy upgrades ahead of their competitors. This means the client reaches and exceeds break-even sooner. DevOps lubricates the value chain so companies add value to a product faster. One reason it worked so well with Flickr, was the immense trust between Dev and Ops, and that is a lesson we should learn.

?We transformed from a team of employees to a team of owners. When you move at that speed, and are looking at the numbers and the results daily, your investment level radically changes. This just can’t happen in teams that release quarterly, and it’s difficult even with monthly cycles.? (Jim Stoneham)

Contact Us

  • (+353)(0)1-443-3807 – IRL
  • (+44)(0)20-7193-9751 – UK

Check our similar posts

Energy Audit – clearly clear?

An energy audit is an examination of an energy system to ensure that energy is being used efficiently. It is the inspection, survey and analysis of energy flows for energy conservation in a building. Energy audits can be conducted by building managers who examine the energy account of an energy system, checks the way energy is used in its various components, checks for areas of inefficiency or where less energy can be used, and identifies the means for improvement.

An energy audit is often used to identify cost effective ways to improve the comfort and efficiency of buildings. In addition, homes/ enterprises may qualify for energy efficiency grants from central government. Energy audits seek to prioritise the energy uses from the greatest to least cost effective opportunities for energy savings.

An energy audit is an effective energy management tool. By identifying and implementing improvements as identified, savings can be achieved not only on energy bills, but also equipment will be able to attain a longer life under efficient operation. All these mean actual dollar savings.

An energy audit has to be conducted by a competent person with adequate technical knowledge on building services installations, after which he/she comes up with a report recommending plans on the Energy Management Opportunities (EMO) for energy saving.

An energy audit culminates to a written report. This could show energy use for a given time period (for example a year) and the impact of any suggested improvements per year. Energy audit reports are then used to identify cost effective ways to improve the comfort and efficiency of buildings. The energy audit report therefore gives management an understanding of the energy consumption scenario and energy saving plans formulation.
Energy audit reports should always translate into action. No matter how well articulated, the energy management objectives are afterall, an energy audit (EMOs), all the effort will be futile if no action is taken. The link between the audit and action is the audit report. It is therefore important for the audit reports to be understandable for all the target audiences/ readers, all of whom may have diverse needs, hence the reason why they should be clear, concise and comprehensible.

What are the do?s and don’ts when writing energy audit reports?

Avoid technical jargon as much as possible; present information graphically; use different graphics such as pie charts, data tables. Schematics of equipment layouts and digital photos tend to make EMO reports less dry. Some of the energy audit software?s come in handy in the generation of such graphs and charts.
The climax of it all is the recommendations, which should be made very fascinating.

Contact Us

  • (+353)(0)1-443-3807 – IRL
  • (+44)(0)20-7193-9751 – UK
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.

How AI Helps Improve Field Service

Its seems that with the current rate of technological innovation that these is something new every single day.  Therefore, you’re always looking forward to a new technological innovation that’s going to help you make your business operations more efficient and automated.

One of the most fascinating milestones in the field of technology is the integration of Artificial Intelligence (AI) in business. In one way or the other, AI gives a glimpse of machine supremacy that allows computers to perform tasks that were initially performed by humans. 

Are machines going to completely replace people in the workplace?

Of course, not.  Technologies like AI and Machine Learning are designed and meant to support employees in doing their tasks too boost their productivity.

AI is predominantly used to eliminate jobs and tasks that humans find boring, demotivating or monotonous. In some cases AI is also used to do jobs that are considered dangerous for humans to preform.

Previously the most common implementations for AI were all about gaming, entertainment, and advanced science,  now it’s spreading into a number of industries including the field service industry.

FieldElite – Field Service Software , can help you optimise the day-to-day operations of your business.

AI in field service management will enhance you business capabilities with:

  • Information Sharing
  • Real Time Updates
  • Automated Workflows
  • Digital Form Data Collection
  • Data Analysis

Improved Customer Service

For Service Based companies, customer retention is vital. Primarily because It can be 5-25 times more costly to acquire a new customer than it is to retain an existing ones.

Therefore customer retention should be a primary focus.? The good news is that by making use of AI you can implement services It can be 5-25 times more costly to acquire a new customer than it is to retain an existing one.

Staying on top of and ensuring you satisfactorily address and meet you customer demands and expectations can be a daunting task.? It can also be an expensive one,? especially for small field service based businesses like :

  • Heating & Plumbing Engineers
  • Electrical Contractors
  • Fire Safety Inspectors
  • HVAC Engineers
  • Facility Management
  • Building, Construction & Trade

Implementing Artificial Intelligence and Machine Learning to automate mundane and repetitive customer administration tasks will enable your staff to be free to provide additional value added tasks for your customers. Making your customers happier.

?Think about the active Chatbots. You can always get complaints directly from customers and address them right away.??

If at any point the customer is unhappy with your services, they can always raise the issue via the Chatbots. Since the bots contain necessary customer information, you can always get back to them and fix the issue at hand.?

With AI in field service, you can solve problems before they arise, or what is otherwise known as predictive maintenance,? In that way, you’ll have better customer relations because you’ll be able to address your customer concerns before they even become aware of them.

Improved Productivity

Scheduling tasks and managing the workforce isn’t a walk in the park. It goes beyond assigning tasks to your team members in the field and giving them deadlines to meet. Whether it’s a small firm or a big organisation, it’s quite difficult to organise the workforce.?

However, adopting Artificial Intelligence can iron out the difficulties most field organisations face in scheduling and managing tasks. Some years back, most firms relied on human intelligence to dispatch jobs to the right people based on given conditions. This was quite difficult, especially that it wasn’t always successful. But thanks to AI. With field service apps like FieldElite scheduling tasks and managing workforce is only a few clicks away.?

What’s more? There?s no room for error. Therefore, you’ll always match the right people for the job. Again, your team will always get tasks on time. That means, the job completion rate will go up, and hence the workforce becomes more productive.?

Predictive Maintenance

Usually, most business operations are based on ?solve the problem as it occurs?, which is just OK. However, it’s not always safe to wait until a problem occurs so that you solve it. Prevention is better than cure, and that’s why Artificial Intelligence comes handy in Field Service.

Using FieldElite Workforce Management Software , you don’t have to wait until something breaks.? Utilizing AI in field service enables you to proactively address field service needs and prevent unforeseen failures and interruptions.?

The ability to predict field service needs through field service apps like FieldElite enables you to make more accurate forecasts. In this way, resource planning is made easier, and as such, you’ll have smoothly running workflows. Again, by taking care of unforeseen circumstances in advance, you’re flexible enough to take care of the unexpected. And that means the overall productivity of your business will go up.

Job Management

Most field service jobs involve multiple stages that can take several days to complete. In addition to this, more often than not, you have to coordinate lots of equipment and contractors at the same time. All these can’t be achieved solely by human efforts. For more successful outcomes, it’s important to incorporate Artificial Intelligence in your field service operations.?

FieldElite is the field service solution that can help you manage sophisticated tasks. The app is packed with field service management tools that enable you to assign complicated tasks and keep track of your field techs. For long-cycle jobs, FieldElite app enables you to follow up on the activities going on the field to ensure they’re completed.?

With AI, there?s no room for error even when the jobs become more sophisticated.

Data Analysis

?

Field service industry involves lots of data. Some years back, organisations depended on human intelligence to analyse big data. Well, things still worked out, but as a human is to err, the outcome wasn’t always perfect. However, with Artificial Intelligence data analysis, 100% accuracy in data analysis is achievable. Field service solutions like FieldElite provide sophisticated data analytic tools that enable you to crack massive data and offer accurate solutions.?

FieldElite data analytics capabilities give you an insight into what’s not working and what needs to be improved. In that way, you can always address matters arising and take care of the loopholes.?

It’s time to go paperless with field management software like FieldElite if you?d like to make your business more profitable. Apart from improving the productivity of your workforce, incorporating AI in your business increases profitability. If you’re still doing your usual field rounds with a clipboard, it’s time to simplify your task with FieldElite app.?

Contact Us

Ready to work with Denizon?

Contact Us Today