Plutora Brings DevOps to the Enterprise

Plutora Blog

Subscribe to Plutora Blog: eMailAlertsEmail Alerts
Get Plutora Blog: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Latest Blogs from Plutora Blog
“To keep up with increasing demand for high quality, rapid software releases, IT organizations must shift to Disciplined DevOps — an approach to software release collaboration that blends agile delivery with risk management and governance that support delivery assurance” DevOps has bec...
“In many real-world case studies, Plutora has resulted in returns exceeding 600% and more. A typical return is around 400% depending on the depth of using the Platform. Adding in the additional savings from Environment reclamation and reduction in capital spending on servers or Cloud E...
An enterprise release manager (ERM) is a new role in the enterprise and it is a by-product of several factors. First, enterprises continue to report larger portfolios with an increased number of smaller, more independent projects. At the same time more companies are decentralizing depl...
Your IT team has adopted DevOps approaches to enable a faster and more reliable way to move initiatives between development teams and operations. However, you’re still witnessing inconsistent results despite a concerted effort to move towards continuous delivery. Why? Automating variou...
Decades ago, when software projects were larger and more monolithic projects moved very slowly. Developers didn’t build micro-service architectures in weeks using modern software tools and processes such as Agile. They worked on projects with timelines measured in months or years. Comp...
The future of software releases is clear. Continuous delivery is here to stay. But does that mean that legacy software systems and infrastructure need to be altogether abandoned? If you polled the people busy redefining best practices today, they’d agree that in a decade we’re going to...
Improve your release test delivery. We’re launching Stryka soon, next generation test case management software.A SaaS tool to support agile and DevOps in the enterprise. Learn More and Sign Up to Beta > The post Stryka – Next generation test case management software app...
"Complexity" is often viewed as a negative. This is perhaps even more the case at scale, where some degree of complexity is unavoidable. Any unnecessary complexity, states the conventional wisdom, is public enemy number one. But does that wisdom ring true? Let's look a little closer at...
If you work for a large company, you'll often look around and wonder if moving to a daily release cycle or automating deployments is even possible given the number of meetings and the amount of process your releases are subject to. Between the CAB meetings, the QA schedules, and the co...
Of all the jobs we’ve described in our series of posts focused on hiring, the application release manager role is the role that has been the most constant over the past several years. Deployment managers and test environment managers are relatively new job roles emerging only as the nu...
When your company conducts a high-risk migration to a new platform or when you are faced with a challenge to preserve uptime on a critical day, you plan for every possible contingency and you look at every single facet of your enterprise to identify the weakest link. You prepare. Relea...
Continuous Delivery is a trend that is taking the software industry by storm, and Continuous Delivery Management (CDM) is a new approach to release management that provides both transparency and a governance structure to manage continuous delivery across a large software enterprise. CD...
We've said it on this blog before, and we'll repeat the same message: Solving a software engineering problem is simple physics. It takes a set amount of energy to move a project from point A to point B, and changing the process or path doesn't change the unavoidable fact that difficult...
The executive concern regarding software development used to revolve around the choice between a waterfall approach or agile teams. Now, the development world is almost decidedly convinced that agile is the way to go. With agile projects seeing 350% to 600% greater success than waterfa...
The software industry is constantly changing. Whether we’re developing for new mobile platforms, adopting the latest languages, or upgrading our methodology there are few constants when it comes to software. As timelines for software delivery projects tend to shorter, more continuous a...
Happy 2016. To help you think about the Environment Management year ahead, we've assembled a collection of resolutions for you to try out. Resolution #1 - I will plan ahead for environment requirements. Many environment managers operate in a reactive mode. They make some wildly inacc...
Gone are the days of the “Golden Master.” In fact, those days are so far gone that programmers new to the industry may not even recognize the term. If you don’t know what that term means we have to travel back in time for two decades, back to a time when most software was sold in shrin...
To follow up our previous post on environment management resolutions for 2016, here is a post focused on specific resolutions for Test Environment Management (TEM). Most of the challenge for TEM relates to unknowns surrounding the testing process: How long is a testing process going to...
A deployment plan can model anything: infrastructure changes, software releases, or configuration changes that span multiple departments.  While many of the core software deployment tasks that enterprises face today can be automated most systems still require a plan.   M...
Years and years, decades: that’s how long some of the release processes we support have been running. In a sector that is so focused on the newest technologies it can be challenging to design systems that last more than a few years, but when you support software development at the larg...
If you work in a large enterprise you know what I’m talking about. Some teams move fast (maybe too fast) while other teams still operate as if they are in 1985. How do you get these teams to move faster? There’s such a wide range of capabilities in today’s enterprise it can often feel ...
Most large software enterprises are facing a tough choice: on one hand you have the control and stability of traditional ITSM, and on the other you have the self-service freedom and agility of more modern approaches such as DevOps.   As organizations move toward self-service releases a...
Bimodal IT is a trend identified by Gartner that describes a common challenge for IT departments – how to support two modes of operation within the same IT department.   According to Gartner’s definition: “Mode 1 is traditional and sequential, emphasizing safety and accuracy. Mode 2 is...
Large organizations engaged in enterprise release management seldom have a single "enterprise release manager." Instead of a single, "enterprise-wide" responsibility, most large, decentralized organizations assign responsibility for more strategic, release management functions to seve...
Gartner has put a name on a common experience across all industries – IT departments often support two different approaches to IT.  One side is focused on agility and rapid time to market while the other is focused on stability and traditional service management.  With Bimodal IT you h...
Enterprise software development has undergone a dramatic transformation in the last decade as most companies have transitioned to more iterative, agile approaches to software delivery.  This overall acceleration of the software development effort has been focused squarely on more tacti...
Across industries time to market for new software initiatives is decreasing over time and the frequency with which releases are transitioned from development to production is increasing. Put simply, every major company is turning into a software company and software is being delivered ...
With Enterprise Release Management (ERM) organizations can achieve real agility above the level of individual projects.  When management functions are informed by feeds updated continuously and when multiple departments agree upon consolidated dashboards of release progress organizatio...
There are three characteristics that drive the need to establish a strong Enterprise Release Management (ERM) practice and they are all related to the complications that accompany scale: Team Size – The number of people involved in an enterprise release. System Scope – The scope of an ...
Enterprise Release Management (ERM) is an emerging set of practices designed to support enterprise change initiatives and software delivery across multiple projects within large organizations.  ERM is the management of the software delivery lifecycle across multiple projects and depart...
Many of the well-known examples of DevOps success we read in blogs on the Internet paint an idyllic picture of DevOps productivity. A team was facing a stodgy, slow-moving operations department, teams weren’t delivering software on time. Those teams moved to DevOps, became proactive ab...
This week we're attending SYS-CON Event's DevOps Summit in New York City. It's a great conference and energy behind DevOps is enormous. Thousands of attendees from every company you can imagine are focused on automation, the challenges of DevOps, and how to bring greater agility to so...
When you read about DevOps in the technical press you come away with the idea that infrastructure automation has solved the problem of complex releases. These images of success are backed up by vendor assertions that businesses are no longer burdened by complex releases spanning multip...
Last week wasn’t a good week for the stability of high-profile systems.  United airlines had a ground-stop due to an “automation failure”, the New York Stock Exchange suffered a problem that caused an interruption of trading, and the Wall Street Journal had issues with site availabilit...
Release managers understand what it means to have a triple-booked Outlook calendar.  They have calendars subject to rapid last-minute changes as project timelines slip and environments issues cause a series of fire-drill emergencies to be solved right now.  Most release managers spend ...
“Hey, can we get another QA environment?” That question can ruin an environment manager’s day. A large organization plans for capacity, purchases enough infrastructure to support as many environments as the organization needs at once, and even “on the cloud” resources have a price. Sev...
We’ve compared release managers to air traffic controllers in previous blog posts. For test environment managers we use a different analogy, instead of air traffic controllers a test environment manager job’s is more akin to assigning and preparing gates for flights arriving to and tak...
When Forrester analysts Amy DeMartine and Kurt Bittner wrote “The Seven Habits of Highly Effective DevOps” the habit I focused on was habit number one: “Establish trust and transparency between Dev and Ops.” This is at the core of release management: DevOps Trust and Transparency ̵...
Do you think development teams really update those BMC Remedy tickets with all the changes contained in a release? They don't. Most of them just "check the box" and move on. They rose a Risk Level that won't raise questions from the Change Control managers and they work around the...
This post could have also been titled “Questions Release Managers should be Prepared to Answer.”  Imagine you report to a VP who is asking you questions about how prepared you are for releases and how you are addressing a set of emerging issues. Everyone who has participate...