GitHub unveiled an upgrade of its Actions workflow automation and customization solution today that comes with a new bundle of continuous integration and deployment (CI/CD) capabilities. The new version is now in beta.
What makes Enterprise Agile different from plain ol' ordinary agile? Our Agile Architect returns with a series of columns exploring what we can gain from enterprise agility.
Compuware kicked off the new year by unveiling a new set of enhancement for its Topaz mainframe DevOps solution, including new functionality in Topaz Team Profiles that facilitates knowledge-sharing between experienced mainframe developers and newer generations.
If you think this is going to be an article on evil product owners and how they just want everything, you're going to be disappointed. Our Agile Architect explains how 'Greed-Accelerated Development 'is the completely achievable desire to want more from your work than just the immediate benefit while not paying any additional price for it. Bwa Ha Ha Ha!
Safety is an important ingredient in any agile retrospective. If team members don't feel safe, they may not be candid and honest with their input, negating the effectiveness of the retro. Our Agile Architect shares some of his techniques for measuring and maintaining safety.
Tim Buntel, DevOps Advocate at XebiaLabs, advises companies to focus on a combination of global measurements (traditional metrics from across the organization) and outcomes (delivery of software with speed and stability).
There has been a lot of misinformation about the nature of DevOps and its relationship to (Big A) Agile. Our Agile Architect explains why DevOps is an important component of (little a) agile, plus offers the top five DevOps misconceptions dev teams often have.
Quality assurance has long been an important component of an agile team. But times change. The introduction of new capabilities like ubiquitous cloud computing, containerization and microservices changes the way we think about QA. Here's how.
While more enterprise developers and their teams are adopting DevOps practices across both applications and databases, a Redgate Software survey suggests some industry verticals are "turning their backs on DevOps."
Our DevOps specialist dives into predictions for the coming year concerning DevSecOps, serverless architecture, "after agile" and more.
Agile is not a hard science like physics or chemistry. There is no fundamental theorem of agility. But practices in agile act along empirical scientific principles in that experimentation can lead to measurable results, reproducible across teams in similar conditions. So why does each agile team feel compelled to rediscover this again and again?
For anyone out there still harboring doubts about enterprise interest in DevOps, consider Toptal's recent launch of a new on-demand talent specialization focused on "meeting the rising need for skilled DevOps engineers."
The low-code development specialists at OutSystems aren't going to be left out of the DevOps revolution, having added a new set of DevOps features to its namesake development platform specifically designed to help enterprise IT shops adopt low-code practices that accelerate app delivery.
Our Agile Architect recently celebrated his 10 year work anniversary and uses this as an opportunity to look back and see how agile has changed over the last decade.
Compuware took another step along the trail it's been blazing for the past year to "mainstream the mainframe" by making its Topaz suite of development and testing tools available on the Amazon Web Services cloud.
Toad DevOps Toolkit addresses a potential bottleneck in the continuous integration/continuous delivery (CI/CD) pipeline: Oracle database changes.
Things agile developers want to tell you but won't.
"We're asking, what's the next step? How does Agile evolve? How do we extend the reach of enterprise teamwork?"
John finds two new solutions marking the next step in the evolution of DevOps: CloudBees DevOptics and ElectricFlow 8.0.
Our Agile Architect talks about the benefits of T-shaped people in agile and the dangers of stressing broad knowledge and participation over deep expertise.