Eliassen Group experts talk about the impact of automation on continuous compliance, which can lead to savings and an improvement in outcomes.
Find out how Eliassen Group has been using workshops where people develop a fully-functioning cloud pipeline in days or weeks instead of months.
Running multiple instances of Jira and Confluence can pose business problems. Valiantys, an Eliassen Group partner, helps you prepare to consolidate.
Stephen Gristock discusses how, while Linear compliance processes and Agile methods do not inherently work together, it is possible for the two to coexist.
Realizing how you’ve lost your way invites a new disruptive way of thinking that creates the possibility for a transformative change in your choices.
In Part 1 of this series, we discussed 3 primary metrics of an Agile transformation: value, flow, and quality, respectively. In the second part of the series on Agile metrics, we explore the ‘value & outcomes’ category of metrics to holistically steer an organization.
In Part 2 of “Scaling Great Heights with SAFe,” Stephen Gristock guides the reader in their continued ascent toward Agile excellence by examining some approaches for successfully leveraging SAFe.
Eliassen Agile’s Stephen Gristock advocates for the SAFe approach to Agile despite the full range of effective Agile-adoption methodologies. SAFe calls for an initial focus on defining the need for Agile with the help of active participation from Leadership.
The human drive to win can be an incredible transformational tool when harnessed and used for positive change. Asking your team three basic questions can realign and reprioritize company values, and as a unit, this drive to win can propel you ahead of your competition.
Alignment across the dimensions of Flow, Value, and Quality is critical for a successful Agile transformation, but can the abstract concept of alignment be measured? Look at these ways to interpret the tangible data.
In Part 2 of this blog post, we look at some of the pre-requisites and adoption scenarios of an Agile Playbook.
In Part 1 of a two-part series, Stephen Gristock considers the place of process in Agile, ultimately making a case for an Agile Playbook.
While there are benefits to standardization, premature standardization, or standardization with no room for experimentation leads to stagnation and poor overall performance. The pace of change and innovation in DevOps means new opportunities for improvement are arising regularly.
Use a visual guide to have a productive conversation that enables non-technical people to appreciate the need to actively and continually keep technical debt low.
Separation of duties is an important concept and to some, it might seem to be incompatible with a DevOps approach, but it isn’t. In fact, in many cases the separation of duties in the context of DevOps offers more assurance of quality, security, and audit-ability than traditional approaches.