Agile

September 28, 2016

The reason Gartner brought the idea of bimodal IT to light was to create breathing space so that organizations could transform and innovate without crashing and burning. The reason that Agile was created, for instance, was to enable a faster, more responsive process than waterfall practices can offer. However, switching to continuous delivery and integration mode too quickly could prove disastrous for certain systems, as some change carries more inherent risk than other changes. Following are key elements to consider when transitioning to ensure that applications continue to run at optimal levels ...

September 26, 2016

Sometimes a phrase or concept becomes so popular that its original meaning gets buried beneath people's alternative meanings or outright misappropriations. This is what has happened with "bimodal IT." Consequently, organizations have expectations and assumptions that differ from the original term, leading to confusion, disappointment and even disillusionment in some cases. Let's examine what this term "bimodal IT" actually means, why it makes sense in some cases and how to ease the pain of transition ...

September 07, 2016

In an industry where failure is unavoidable, learning and innovating through feedback loops is your best course of action. Instead of focusing on increasing the time until your next failure, you should focus on decreasing the time it takes for your systems to recover following a failure ...

August 31, 2016

DevOps means a mindset of getting better at getting better. You need to get better to fulfill customer needs, and therefore you need to get interested in what your customer wants and make sure the feedback loop will be as short as possible. How do you reach the state of "get better at getting better"? ...

August 29, 2016

When I was an active football player one summer I wanted to do extra training. I skipped the leg training, because I did some running as well, but the trainer said "never skip a leg day". What does this have to do with DevOps? ...

August 03, 2016

As dev teams and product owners begin the Agile development process, they meet to discuss how users will interact with their applications. They write these user stories down on sticky notes or index cards, arranging and re-arranging them into an order that they feel makes sense. These stories create the basis of their Agile requirements process. When done poorly, user stories lead to missed or misunderstood requirements which 96% of application development and delivery professionals blame for project delays and rework ...

February 08, 2016

While 88 percent of organizations say they have adopted agile development, only one in five have fully implemented the five best software testing practices typically associated with a mature agile development process, according to Testing Trends in 2016: A Survey of Software Professionals ...

February 01, 2016

Here are three examples of SLI patterns that you will encounter as you embark on your SAFe implementation journey, as well as ways in which you might use them ...

January 29, 2016

Factories scale well and have a strong tendency to get more efficient as they get bigger. So why is it, then, that building software seems to have the opposite effect of reducing efficiency as you scale up? Dean Leffingwell, the creator of Scaled Agile Framework (SAFe), noted that building large scale systems is fundamentally a social event – not a manufacturing event ...

November 02, 2015

Times are changing. With the imperative to deliver applications faster, developers are increasingly stepping outside their traditional skill-zones and leveraging new automated capabilities – allowing them to develop and test in parallel, while releasing software continuously. In essence, they're not only writing great music, but also building the instruments upon which to play it ...

February 24, 2015

A shift to continuous integration (CI) and other agile methodologies is driving a massive change in the way that development and testing professionals approach testing, according to an independent, global developer survey titled Web and Mobile Testing Trends ...

June 06, 2014

Although the exact role and responsibilities of DevOps may not be defined across the board, it has to be able to rapidly deal with issues rising from the code and from the connection between the code and production environment. These responsibilities may include release management, configuration management, and dealing with problems (bugs) that find their way to the production environment. In this blog, I will focus on the latter and examine the tools and methods that can help expedite this process in order to cope with these continuous changes ...

Pages