It’s uncontested that open source communities have been at the center of innovation for decades, enabling and accelerating innovation through distributed developers’ contributions. What’s also become clear over time is that the outcomes of the open-source development model are anchored in ways of working and unsaid cultural principles and practices that enable these communities to thrive.
Red Hat, the leader in open-source, has boiled down the underpinnings of open source innovation in five principles that make up what we call open culture: transparency, collaboration, adaptability, community, and inclusivity. These principles — a bedrock to Red Hat’s innovative model for decades — have never been put to the test more than in the current climate when remote work has become the norm, and leaders rely on high-performing remote teams to continue to deliver tangible business outcomes and innovation. Business goals may need to be adapted in the current climate, but initiatives, milestones, and initiatives don’t disappear. Working in an agile manner is critical.
Continue reading “Deliver value with distributed teams through the power of open”
Automation within enterprise IT is not a new topic. Whether it’s automating the creation of a user desktop or a server, the drive has always been to automate as much as possible to achieve faster time to market and efficiency. What has changed, though, is the number of infrastructure elements one can automate within an IT org. I still remember my first job in college 15 years ago where I used a variety of tools to automatically deploy and configure Windows XP simultaneously across 50 desktop machines for a classroom lab environment. Today not only can we automate desktop computer deployments but also servers, applications, and even networking.
Continue reading “4 ways to jump start an Open Source & Agile Automation Culture”
When Cigna developers needed to improve their application testing processes, they teamed up with Red Hat Consulting to implement agile methodologies. Iterative development has helped Cigna prioritize features based on customers’ needs, and as a result, the quality of Cigna’s software has improved.
In the video below, representatives from Cigna and Red Hat Consulting discuss how working together to instill behavior-driven development principles helped Cigna:
• Increase speed to market by aligning application delivery with customer expectations.
• Reduce risk by engaging subject matter experts and stakeholders in regular reviews.
• Sustain application quality by identifying and fixing defects early in project life cycle.
• Ensure on-time delivery and predictable performance.
Continue reading “Cigna becomes more agile with behavior-driven development”
by Alan Hale (Red Hat)
This post originally appeared in DeveloperTech.
Today’s business leaders want more innovation, faster. They know that, in order to beat competitors and continue to thrive, their organisation must excel in bringing new products and services to market at speed and on consistently exceeding customer expectations.
That puts major pressure on those responsible for developing and delivering new and enhanced software functionality for the business to use. More frequent releases and shorter deadlines are increasingly becoming facts of life, but in the race to fast-track new pieces of code, IT teams often hit a roadblock.
That roadblock occurs at the boundary of application development and IT operations, an intersection where two very different cultures meet.
On one side of the boundary is the culture of the developer, where creativity, freedom to experiment and choice of tools are paramount. The developer is happiest using Agile techniques to produce a constant stream of software releases and upgrades that will get the business where it needs to be, in terms of innovation.
On the other side of the boundary is IT operations, where stability and control are what matters. Disruption is the enemy and frequent software releases can be complex to manage. IT operations agree that they want the business to move forwards – but not at the risk of critical systems falling over.
Continue reading “Getting developers and IT operations working together”