The 2-Week COBOL Sprint: Why Mainframe Shops Need It
The digital economy is forcing mainframe shops to change their cultures at a pace way outside their comfort zones. Many developers still believe working slow means safely preventing missteps and ensuring stability. While it’s critical for shops to establish a high-quality delivery, doing so at the pace of a tortoise gives Agile industry disruptors the time they need to bring your company to extinction.
In the last few years, many companies have realized the digital world demands they move faster than the Waterfall processes they’re accustomed to. Technology is more accessible than ever, making competition ubiquitous—even two developers in a garage can become your nemeses overnight. You need to be fast enough to release competitive mainframe software before the next guy. To pull this off, your company must adopt Agile processes, like the 2-week COBOL sprint, that let it function with the agility of a greyhound.
Why Use the 2-Week COBOL Sprint?
Before elaborating, let’s clear the air of skepticism over COBOL’s relevancy. COBOL is still relevant, considering “global capitalism still relies almost entirely on mainframe applications to transact business,” according to Compuware CEO Chris O’Malley. In essence, COBOL is the digital economy’s “foundational language.”
Despite COBOL’s steadfastness in today’s digital economy, COBOL wizards are retiring in droves, and the impact is noticeable. Figuring out how to maintain the mainframe with an impending shortage of expertise is striking fear into CIOs everywhere. And as mainframe proficiency dwindles, the upcoming generation of mainframers must confront outmoded tools and antiquated development lifecycle processes, which O’Malley refers to as “non-Agile in the extreme.” Mainframe shops who can’t find solutions to overcome obsolete methods and who refuse to adopt Agile processes will water-fall to the bottom as Agile shops rise to the top.
If you’re still wondering why mainframe shops need the 2-week COBOL sprint, the answer is that you won’t survive without it. Acknowledging this is easy, making it happen is hard. But Compuware is a prime example of how shifting to an Agile culture and using sprints can be accomplished. If you’re wondering where to begin, we’re here to coach you through the process.
2-Week COBOL Sprint Next Steps
Throughout my blog series, I’ll run you through the necessary steps to pull off the 2-week COBOL sprint, including:
- How Agile mends broken trust
- Having a critical conversation about Agile
- How to build a scrum team
- Developing a process of continuous builds
- Using Agile feedback loops
- Implementing deployment automation
- Identifying software development bottlenecks
You can read all of my “The 2-Week COBOL Sprint” blog posts in the series here.
Latest posts by Glenn Everitt (see all)
- Living in a ‘More Data, More Problems’ World with Unit Tests - September 6, 2017
- No Mock Objects for Your Mainframe? Create COBOL Program Stubs - March 23, 2017
- Why You Need Automated Unit Testing on the Mainframe - January 5, 2017