Latest Enablement Pod offering unveiled…

Latest Enablement Pod offering unveiled…

ECS Digital announced the official unveiling of their Enablement Pod offering yesterday at DevOps World | Jenkins World, the annual gathering of DevOps practitioners using Jenkins for continuous delivery.

Understanding that business-wide transformations take time and involve multi-year programmes, ECS Digital have designed Enablement Pods to help clients effect change and realise value in the short and long term.

Enablement Pods are a collection of outcome-focused sprints that handpicks specialist teams to deliver the people, resources and capabilities their clients’ need, when they need them. These Pods help enterprises transform at scale by embedding – for short periods – in existing engineering teams to enable new ways of working, tooling and technology.

The unique feature of ECS Digital’s Enablement Pods is that they – and ECS Digital’s success – are measured against KPIs defined in Sprint Zero. By tying success to business outcomes, clients are guaranteed a real return on investment. And if ECS Digital don’t hit the agreed outcomes, customers get a return on the revenue invested.

Each additional sprint to the Sprint Zero provides an opportunity to showcase and review progress ensuring maximum value from all activities. Sprints last between two weeks and resources are dependent on specific project and sprint KPIs. Another unique feature of ECS Digital’s Enablement Pods is that their resource profile remains dynamic to satisfy the different skills requirements of sprint KPIs.

ECS Digital have begun using Enablement Pods as an essential tool to deliver transformation at scale for their prolific customers. In addition to exceeding project KPIs, ECS Digital have enhanced value by enabling internal teams so they become self-sufficient and architect solutions designed to survive tomorrow’s challenges, not just todays.


“ECS Digital’s input has added an extra level of intelligence which has enabled us to build on the capacity under their guidance. We have grown in our capabilities over these past 12 months and developed the skillsets of our internal team through additional training. If we have any DevOps or automation or platform requirements in the future, we won’t bother going to tender, we will go straight to ECS Digital.” Matthew Bates, IT Director at ThinkSmart

Enablement Pod outcomes:

  • For each £1 invested in us, we have delivered £3 of annualised savings in the development lifecycle of a Retail Bank core application
  • A 99% reduction of application environment configuration delivery timescales (from 7200 minutes to 3 minutes)
  • Increase quality of testing through automation as well as timescales of test cycles by over 50%
  • 12x reduction of application delivery cycle

About ECS Digital:

ECS Digital is an experienced digital transformation consultancy, helping clients deliver better products faster through the adoption of DevOps practices.

They are the digital practice of the ECS Group and have been leaders in digital transformation since 2003 – evolving their offerings to support their customers’ evolving needs. They believe in a better way to adopt and deliver new ways of working, processes and technology. A more valuable and outcome focused way of leveraging Enterprise DevOps and Agile testing to help build tomorrow’s enterprises today.

They’ve helped over 100 customers – including Lloyds Banking Group, ASOS, BP plc and Sky – realise the benefits of Enterprise DevOps and Agile Testing and have proactively remained relevant in the face of increasing challenges of customer expectation and market disruption. You can follow the ECS Digital community on LinkedIn and Twitter (@ECS_Digi).

Andy CuretonLatest Enablement Pod offering unveiled…
read more
Why you should invest in AWS Big Data & 8 steps to becoming certified

Why you should invest in AWS Big Data & 8 steps to becoming certified

A decision that many engineers face at some point of their career is deciding what to focus their attention on next. One of the amazing advantages of working in a consultancy is being exposed to many different technologies, providing you the opportunity to explore any emerging trends you might be interested in. I’ve been lucky enough to work with a huge variety of clients ranging from industry leaders in the FTSE 100 to smaller start-ups disrupting the same technology space.

So why did I pick Big Data?

A common pattern I’ve noticed is that everyone has access to data – large amounts of raw, unstructured data. Business and technology leaders all recognise the importance of it, and the value and insight that it can deliver. Processes have been established to extract, transform and store this large amount of information, but the architecture is usually inefficient and incomplete.

Years ago these steps may have equated to the definition of an efficient data pipeline but now with emerging technologies such as Kinesis Streams, Redshift and even Server-less databases there is another way. We now have the possibility of having a real-time, cost efficient and low operational overhead solution.

Alongside this, companies set their sights on creating a data lake in the cloud. In doing so, they take advantage of a whole suite of technologies to store information in formats that they currently leverage and also in a configuration they possibly may harness in the future. These are all clear steps in the journey towards digital transformation, and with the current pace of development in AWS technologies it is the perfect time to become more acquainted with Big Data.


But why is the certification necessary?

The AWS Certified Big Data Speciality exam introduces and validates several key big data fundamentals. The exam itself is not just limited to AWS specific technologies but also explores the big data community. Taken straight from the exam guide we can see that the domains cover:

  1. Collection
  2. Storage
  3. Processing
  4. Analysis
  5. Visualization
  6. Data Security

These domains involve a broad range of technical roles ranging from data engineers and data scientists to individuals in SecOps. Personally, I’ve had some exposure to collection and storage of data but much less with regards to visualisation and security. You certainly have to be comfortable with wearing many different hats when tackling this exam as it tests not only your technical understanding of the solutions but also the business value created from the implementation. It’s equally important to consider the costs involved including any forecasts as the solution scales.

Having already completed several associate exams I found this certification much greater in difficulty because you are required to deep dive into Big Data concepts and the relevant technologies. One of the benefits of this certification is that the scope extends to these technologies’ application of Big Data so be prepared to dive into Machine Learning and popular frameworks like Spark & Presto.


Okay so how do I pass the exam?

1. A Cloud Guru’s certified big data specialty course provides an excellent introduction and overview.

2. Have some practical experience of Big data in AWS, theoretical knowledge is not enough to pass this exam…

  1. Practice architecting data pipelines, consider when Kinesis Streams vs Firehose would be appropriate.
  2. Think about how the solution would differ according to the size of the data transfer, sometimes even Snowmobile can become efficient.

3. Understand the different storage options on AWS – S3, DynamoDB, RDS, Redshift, HDFS vs EMRFS, HBase…

4. Understand the differences and use cases of popular Big Data frameworks e.g. Presto, Hive, Spark. 

5. Data Security contributes the most to your overall exam score at 20% and is involved in every single AWS service. There are always options for making the solution more secure and sometimes they’re enabled by default.

  1. Understand how to enable encryption at rest or in-transit, whether to use KMS or S3, or client side vs server side.
  2. How to grant privileged access to data e.g. IAM, Redshift Views.
  3. Authentication flows with Cognito and integrations with external identity providers.

6. Performance is a key trend

  1. Have a sound understanding of what GSI’s and LSI’s are in DynamoDB.
  2. Consider primary & sort keys, distribution styles in all of the database services
  3. Different compression types and speed of compressing/decompressing.

7.  Dive into Machine learning (ML)

  1. The Cloud Guru course mentioned above gives a good overview of the different ML models.
  2. If you have time I would recommend this machine learning course by Andrew Ng on Coursera. The technical depth is more lower level than you will need for the exam but it provides a very good introduction to a novice about the whole machine learning landscape.

8. Dive into Visualisation

  1. The A Cloud Guru course provides more than enough knowledge to tackle any questions here.
  2. Again if you have the time there’s an excellent data science course on Udemy which has a data visualisation chapter that would prove useful here.


Exam prep

It can’t be emphasised enough that AWS themselves provide amazing resources for learning. Definitely as preparation for the exam watch re:Invent videos and read AWS blogs & case studies.


Watch these videos:

  1. AWS re:Invent 2017: Big Data Architectural Patterns and Best Practices on AWS 
  2. AWS re:Invent 2017: Best Practices for Building a Data Lake in Amazon S3 and Amazon
  3. AWS re:Invent 2016: Deep Dive: Amazon EMR Best Practices & Design Patterns  
  4. AWS Summit Series 2016 | Chicago – Deep Dive + Best Practices for Real-Time Streaming Applications 


Read these AWS blogs:

  1. Secure Amazon EMR with Encryption 
  2. Building a Near Real-Time Discovery Platform with AWS 



  1. Streaming Data Solutions on AWS with Amazon Kinesis
  2. Big Data Analytics Options on AWS 
  3. Lambda Architecture for Batch and Real-Time Processing on AWS with Spark Streaming and Spark SQL 


All of the Big Data services developer guides.


One last note….

This exam will expect you to consider the question from many different perspectives. You’ll need to think about not just the technical feasibility of the solution presented but also the business value that can be created. The majority of questions are scenario specific and often there is more than one valid answer, look for subtle clues to determine which solution is more ‘correct’ than the others, e.g. whether speed is a factor or if the question expects you to answer from a cost perspective.

Finally, this exam is very long (3 hours) and requires a lot of reading. I found that the time given was more than enough but remember to pace yourself otherwise you can get burned out quite easily.

Hopefully my experience and tips will have helped in preparation for the exam. Let us know if they helped you. 

Good Luck!!!

Visit our services to explore how we enable organisations to transform their internal cultures, to make it easier for teams to collaborate, and adopt practices such as Continuous Integration, Continuous Delivery, and Continuous Testing. 

ECS DigitalWhy you should invest in AWS Big Data & 8 steps to becoming certified
read more
Alexa: Building Skills for the World of Tomorrow

Alexa: Building Skills for the World of Tomorrow

We have all seen the TV Ads with someone asking Alexa (Amazons personal assistant AI) to dim the lights or start playing ‘The Grand Tour’ on Prime Video, and this technology is growing larger and faster every day.

Most commercial technologies like computers and internet started their lives in the hands of big businesses and large institutes that could afford the large initial RnD costs. In light of this, the Amazon team have taken a reverse approach and employed a small scale, iterative expansion of the product.

By providing developers access to the Alexa development kit and opening the voice service to the public, Amazon have made Alexa development a straightforward, painless and rewarding process.

Amazon incentivises its cult following of open source developers by rewarding those who create great skills that others want to use. Amazon announced:

“Publish a new skill this month and get an Alexa water bottle to help you stay hydrated during your coding sessions. If more than 75 customers use your skill in its first 30 days in the Alexa Skills Store, you can also qualify to receive an Echo Dot to help you make Alexa even smarter. The skill with the most unique users within its first 30 days after publishing in February will also earn an Echo Spot.”

Vocal Skills Revolution

We should all remember the mobile app revolution along with the tremendous increase in the number of smartphone users  experienced in global mobile app markets . A massive increase in the user base drove innovation, producing better mobile phones. An organised marketplace for app download, timely updates, advanced app development platforms became the norm. Most significantly, the development of some very useful and revolutionary apps have become part of our everyday lives. With the number of users almost doubling over the last 5 years, mobile app developers can reach more consumers than ever.

At ECS Digital, we believe Voice will experience the same type of growth as mobile applications did.

While consumers command more of their day to day life using voice-controlled technologies, from smart TVs to Alexa enabled electric cars, we can be safe in the knowledge that the voice revolution is coming and will change the way future generations interact with technology.

Alexa for Business

What is Alexa for Business?

Alexa for Business makes it easy for you to use Alexa in your organisation. Alexa for Business provides tools to manage Alexa devices, enrol users and configure skills across those devices. You can build your own context-aware voice skills using the Alexa Skills Kit (ASK) and conferencing device APIs, and you can make them available as private skills for your organisation.

What is an Alexa Skill?

Alexa is Amazon’s voice service and the brain behind tens of millions of devices like the Amazon Echo, Echo Dot, and Echo Show. It provides capabilities, or skills, that enable customers to create a more personalised experience. There are now tens of thousands of skills from companies like Starbucks, Uber, and Capital One as well as other innovative designers and developers.

Alexa Voice Service

The Alexa Voice Service (AVS) enables you to integrate Alexa directly into your products. We provide you with access to a suite of resources to quickly and easily build Alexa-enabled products, including APIs, hardware and software development tools, and documentation. With AVS, you can add a new intelligent interface to your products and offer your customers access to a growing number of Alexa features, smart home integrations, and skills.

What is the Alexa Skills Kit?

The Alexa Skills Kit (ASK) is a collection of self-service APIs, tools, documentation, and code samples that makes it fast and easy for you to add skills. ASK enables designers, developers, and brands to build engaging skills and reach customers through tens of millions of Alexa-enabled devices. With ASK, you can leverage Amazon’s knowledge and pioneering work in the field of voice design.

ECS Digital and Amazon Alexa

With Alexa for business being released in the US and coming to the rest of the world soon, we at ECS Digital have been using her to increase productivity and enable innovation within the office. We have been working on a few different initiatives coining the term OfficeOps.

Here are some of them:

Booking a meeting room

Working in a large consultancy,  it can be difficult to know if a meeting room is free. Moreover, booking said room can be a complicated and confusing process. The answer: create an internal/Dev skill to track the availability of a room, who has it and for how long. This skill also allows users to book a room on the spot, allowing our colleagues to interact with the booking process by literally asking the room for a booking slot .

Interactive Training

As a fast-moving DevOps consultancy, ECS Digital are always looking for innovative ways to improve our skills. For a long time now, we have been using Alexa to learn new skills and brush up on existing ones by using her as a pop quiz master. Colleagues located in our London Bridge office can ask Alexa to test their knowledge about a technology, helping them to maintain a high level of competency.


All evidence suggests that voice is here to stay, and will drive the next wave of technical innovation, both in business and at home, making those laborious, everyday tasks a little easier and futuristic. However, our assessment comes with a note: work still needs to be done in order make voice the standard, but we are confident that changes will be made swiftly.

Visit our services to explore how we enable organisations to transform their internal cultures, to make it easier for teams to collaborate, and adopt practices such as Continuous Integration, Continuous Delivery, and Continuous Testing. 

Morgan AtkinsAlexa: Building Skills for the World of Tomorrow
read more
Wholesale Banks, Agile & Quality

Wholesale Banks, Agile & Quality

In banking technology, many teams are using ‘Agile’ to get releases out to business quickly. Most Agile projects start small scale but, as experience & confidence are gained, (successful experiences in more online sides of the bank) it becomes the more mainstream mechanism.

Business sponsors engage iterative delivery & release far better from the project definition, throughout implementation to ongoing BAU. A downside is that it’s hard to say “no” to ad hoc changes and enhancements mid-Sprint as they come to mind of the business sponsors. This can cause re-prioritisation or the build-up of technical debt.

Has it always worked? No, but no project is guaranteed success, not to mention that definitions of success can be ambiguous! Including Test Automaton as a key part of ‘definition of done’ adds a lot of clarity in decisions on platform risk and ‘go live’ (as well as confidence building with each sprint).

Are robust project Agile controls always seen? Less so I’d say. ‘Heroes’ still save the day working overnight in the financial districts. Programmes with robust checks do really mitigate that situation.

The move to Agile delivery is not always synonymous with ‘baking-in’ quality from Sprint planning onwards. Again, culture change needs to evolve here.

The ultimate value of test automation derived from BDD is still in its infancy. It can be deemed as ‘not possible for us’ by those unaware of how BDD translates into test assets, and how under the UI technical testing gives a solid base for speedy delivery. Without across the board buy-in this can get tricky to deliver.

Many banks remain embedded with overly expensive, less Agile-aligned test automation tools that critically are not used by developers themselves. So, the ability to integrate development and test automation is at odds from the start.

The move to open source test automation tools has grown significantly, mostly due to the major license cost savings and highly mature capabilities on offer now. Just putting that first automated test into the CI is a key step that seems to get the ball rolling.

Certainly the move towards CI with predictable quality (and speedy business delivery) is reliant on technical testers and developers having interchangeable skills, using the aligned tools and fully respecting each other’s technical value.

The holy grail of ‘one team delivery’ is an evolution of experiences that raises the bar collectively. All that is required is an open mind.

QAWorks TeamWholesale Banks, Agile & Quality
read more
Effective Communication in Agile

Effective Communication in Agile

One of the principles behind Agile work methods is that ‘business people and developers must work together daily throughout the project.’ Even with agile methods in place this is not always as straightforward as it seems. This article looks at some of the key areas for improvement when it comes to communication between highly technical people and stakeholders.

There is no doubt that technical people are the ones that turn ideas into reality. Whether you’re an artisan programmer, an innovative DevOps engineer or an automation testing genius, we all make it happen.

But we also have project managers to answer to. They’re the ones who keep us on track and are keenly interested in making sure we build the right thing on time and on budget. While you may be technically proficient, many applicants have been denied a job offer because they lack the ability to communicate effectively to their managers and other stakeholders.

The reality is that when you’re in a large-scale project, silo working is not only unlikely but undesirable as it can lead to ivory towers being built which later on incurs rework costs.

So how can we communicate effectively to stakeholders and instil confidence in them?

From my own experience here’s some things I’ve picked up.


One of the major benefits of Agile methodologies is to encourage synergy between team members which is impossible without good listening skills. This seems like a really obvious thing to do but you’d be surprised how little people work on this skill and how often a question is misinterpreted.

A manager can ask a question like “how many web pages have been completed so far?” The developer then responds by talking about content issues, javascript bugs, browser compatibility etc.

While those issues are important, it doesn’t answer the question. The purpose of the question was to ascertain how many web pages have been completed. That answer can either be a number or an honest “I don’t know”. Once the question has been answered, then you can provide your justification. This allows your manager to get a clear and concise update and leave open the opportunity for clarification.

Listening to the question can also save you time and expended effort. Typing up a well-worded email that doesn’t answer the question wastes everybody’s time. And delivering work that nobody wants can demoralise a team.

If you need clarification, don’t be afraid to ask. Seeking clarification first is much better than delivering unwanted work later.

In a job interview, listening to a question is vital. This is your opportunity to show that a company can confidently put you in front of a client. It frustrates interviewers to see someone who is technically proficient but a poor communicator.

When asked a technical question like “What is Polymorphism?”, I like to answer it by stating what it is and then providing an example.

“Polymorphism is the ability to process objects differently based on their data type or class. It is also the ability to re-implement the methods of a derived class….

An example of this is a Dog class that can have its ‘Bark’ method overridden by the Sub class “German Shepherd” to have a different kind of ‘Bark’ message.”

In this example, I have given a theoretical definition of polymorphism and then shown how it can be practically applied. This shows that not only do I understand the concept abstractly but I can also show how it is useful.

Listening to your team members is vital whether it be in a daily stand-up or scrum. More often than not there will be a cross over in workflows and people in your team may be working on a feature that affects your work. Listening to your team members can also give you the opportunity to help them if you can.

“We have two ears and one mouth so that we can listen twice as much as we speak.” Epictetus

Communicate Progress and Blockers

When on a project, you should never work in isolation, even if you are the only one working on a task. To give your team lead confidence that a project is on schedule, provide regular and concise progress reports.

‘Regular’ is relative to the scope and urgency of the project but it should be often enough to report significant progress. This will also give you the opportunity to communicate issues that you may be facing early on so that it can be dealt with as soon as possible.

The people you report to may be able to help you by pointing you to subject matter experts who can help you or tools that can solve your problem.

Regular reporting also can show your project leads if you are on the right track and if the right tasks have been prioritised. In so doing, leads can reprioritise your tasks or discuss your course of action if they feel it goes in the wrong direction.

The cost of rework can be unacceptably higher if a solution is developed in isolation.  It may be delivered on time but often fails to meets requirements.

The following example shows a status report that concisely defines subtasks, the ETA, status, duration and comments:

This table is easy to update as opposed to writing a paragraph every time status is required. The table can also be used by your leads to easily provide status to other stakeholders.

Copy the right people into your email so that everyone can be updated at once, avoiding the need to make duplicate communications.

If you’re working with agile planning and tracking tools like QABook and Jira then regularly updating your tickets is just as important as your team can get up to date information without having to come to you directly. Team leads can then rely on your updates to produce accurate burn down charts and other useful metrics.

Know Your Audience

There are some people who are technical and there are some that aren’t. There are some who are details orientated and some that are more headline orientated. In any case, know your audience. As you get to know your colleagues you’ll soon find out what information they are trying to get when asking you a question and what information they consider important when they are communicating with you. Try to tailor your communications accordingly so that they can better understand you and you can better understand them.

Talking to a non-technical manager about thread safety issues when all they are really interested in is an ETA on a feature is not going to get you very far.

Knowing your audience can lead to more efficient communications and allow you to tailor your conversations so that your concerns can be clearly communicated to the people you answer to and resolve issues quickly.

For example, if there is a bug in your code that is causing a problem, rather than explaining the details of the bug, it might be better to explain the impact the bug has on the deliverable.

Another instance might be when you feel prioritisation of tasks have been incorrectly set, then expressing your opinion on the impact of that with respect to the project timelines. This might better than talking about the technical impact.

When dealing with a more technical audience, it might be more appropriate to discuss design decisions when performing a task and why it is better to use one approach over another.

Be Concise

Nobody likes to read a page long email in order to get an answer to a simple question. As you are probably busy getting your own work done, I’m sure you want to spend as little time as possible writing emails or giving status reports.

Less is more. Answer the question, provide context if needed and provide any necessary references.

A picture says 1000 words. If you can show a screenshot to describe a situation, do so. Rather than pasting in the entire stack trace, copy in an extract and attach the entire stack trace as a file for reference. If you are talking about a list of things that need to be done it might be good to use a bullet pointed list rather than writing it all in one line.

When updating a kanban board, being concise is ideal as you can avoid having a bloated ticket that team leads find difficult to read.

Being concise is also important in a sprint retrospective. Feedback needs to be given accurately and specifically to make sure than the next sprint runs better than the previous. When in a retrospective, talk about things that can actually be acted upon and ideally be measured for future improvement monitoring.

Spelling, Grammar and Confidence

I’ve learned the hard way how embarrassing it can look to communicate to senior staff with spelling mistakes and bad grammar in an email. It can impact your own reputation regardless of your technical proficiency and it can even cause clarification emails to be sent back to you wasting further time.

Proofread your emails and don’t rely on spell checkers as the sole form of QA. Get your peers to read important emails if need be. Speak confidently and clearly with verbal communications and minimise slang when giving formal presentations. In a globalised economy, you are likely to talk to key influencers from around the world who may not understand your culturally specific colloquialisms.

In conclusion, your communications should be tools to get good quality work completed efficiently. They are a window for people to see how skilled you are and how valuable of an asset you are to their business. Communication should be a platform to success not a hinderance.

“The single biggest problem in communication is the illusion that it has taken place.”- George Bernard Shaw

Chris GungalooEffective Communication in Agile
read more
The Evolution of DevOps and the Agile Organisation

The Evolution of DevOps and the Agile Organisation

DevOps has become the latest ‘must have’ in the IT environment.

As software has become a key differentiator between many organisations, collaboration and the ability to respond to change is now vital. Although DevOps has become a bit of a technology buzzword – seen as the solution to the pain of an IT infrastructure unable to keep up with the demands of business – this is perhaps out of sync with where businesses are today and the value that DevOps delivers in the current environment.

A recent lunch debate between a group of business technology leaders came to the conclusion that DevOps is in fact no longer purely about tech, it actually has the opportunity to change business culture. And it’s true – what started out as a specific solution to something that was seen as a tech problem has now evolved into an organisational culture that allows companies to respond quickly and effectively to change.

Taking it back to the beginning: The birth of DevOps

Whilst it sounds like a technical methodology or process, DevOps is actually about changing the culture around the application of technical or software changes. 

Just over seven years ago, the DevOps way of working was established to help organisations with non-collaborative cultures to kick-start collaboration. Initially centred around IT, DevOps promised to remove the “wall of confusion” between Developers and Operations; to help Developers become closer to the teams testing and operating their software, so that they could deliver in a more agile way.

Think back seven years and it’s clear that organisations operated quite differently back then to how they do today. In many organisations change was viewed as “risky” – especially within IT departments, where their role had always been to help companies avoid risk and to a certain extent, protect the status quo.  As business started to push IT harder, something tangible needed to be bought in to encourage the interaction of different teams.

The DevOps explosion

Today, organisational culture has changed.

Change is no longer viewed as risky, but profitable. In fact, a recent Puppet survey suggested that the change success rate between high and low performers in IT can be as much as 60x. The same survey tells us that when employees have high satisfaction, underpinned by collaborative processes, they perform better.

As a result, agility is no longer just a methodology for IT, but a way to improve outcomes across an organisation. 

The wider business has seen the benefits on offer, and many are looking to apply these principles further.  Companies are no longer buying into a buzzword, but the outcome of increased performance that a collaborative culture brings with it.

Of course, when it comes to agility, there are companies that understand and apply agile principles within their organisation, and those that don’t.  Those companies that have already adopted agile are not necessarily looking for a catalyst, but for something that fits with this new way of working.

The evolved DevOps

So how can DevOps continue to support when companies are beyond the catalyst stage?

Members of the afore mentioned lunch debate reached the conclusion that “organisations with a community that came together were able to use DevOps to greater success”. Of course, DevOps is applied in this case to achieve a slightly different set of outcomes, and so, has evolved to fit the organisation.

In such situations, DevOps needs to be more than a “catalyst” for agility, and instead a way to match the speed of the rest of the organisation. Put simply, for collaborative organisations, successful DevOps allows the effective application of continuous delivery.

The Agile consultancy

The DevOps evolution means that the role of consultancies like ECS Digital has changed. Consultancies need to increasingly understand the cultural shift towards collaboration and how DevOps can be adopted by different organisations, in different ways.

It is now more important than ever that customers find the right DevOps partner: they need to kick the tyres and find out whether their partner will encourage a long-term cultural change or whether they’re just about making software delivery faster.

Andy CuretonThe Evolution of DevOps and the Agile Organisation
read more
Backporting DevOps: Bringing Agile and CI/CD to Enterprise Legacy systems

Backporting DevOps: Bringing Agile and CI/CD to Enterprise Legacy systems

A recent survey sponsored by Rackspace found that 79% of enterprises that have not already embraced DevOps plan to start the journey by the end of 2015. The Enterprise customers we are working with that have started the journey are finding that despite DevOps, Agile and Contiuous Delivery increasing their pace of innovation internally, the pace of innovation to their customers is constrained by core legacy systems. Like the iceberg it is not what you can see that is the problem.

Replacing or rewriting legacy and often back office applications that form part of critical processes is rarely achievable in an acceptable time frame or cost. This presentation given at DevOps London discusses the challenge in more detail and how Automation offers a real alternative. The case study presented discusses Siebel and the @Automic ARA for Siebel solution.

We would love to hear from you and discuss the challenges you are facing in your environment. Click here to give us a little information and we will get in touch asap.

Andy CuretonBackporting DevOps: Bringing Agile and CI/CD to Enterprise Legacy systems
read more