Contact Info

One Campus Martius

Phone: 1-800-COMPUWARE

Web: compuware.com

In this blog series, discover how the 2-week COBOL sprint is an Agile software development process that reduces timespan of the application development lifecycle into two-week iterations.

The digital economy’s increasing pace is forcing companies to innovate the tools and processes they use to develop and deliver software. This is feasible on the mainframe only by way of Agile and DevOps processes, such as the 2-week COBOL sprint, that support more efficient application development lifecycles. By breaking up the development of large chunks of application functionality into smaller features that can be developed in short amounts of time, mainframe shops can deliver minimum viable products much quicker to meet the immediate needs of their customers. This enables more frequent testing and leaves room for customers to provide feedback before an entire application or piece of software is developed.

If your organization seeks a way to improve the pace and efficiency at which it develops and delivers functionality to its customers, it’s worth considering how the 2-week COBOL sprint can help. Read the posts in this series to learn more about what this Agile process does and how it improves application development.

The 2-Week COBOL Sprint: Agile Feedback Loops

By | May 31st, 2016|Agile Development, COBOL, DevOps, Featured|

A word of advice: I’d make sure you have feedback between customers and development, development and operations, QA and customers, and QA and development. Having multiple feedback loops circling between these groups will yield some amazing results, enabling your mainframe shop to develop and deliver software at a remarkable pace.

Comments Off on The 2-Week COBOL Sprint: Agile Feedback Loops

The 2-week COBOL Sprint: Developing a Process of Continuous Builds

By | May 3rd, 2016|Agile Development, COBOL, DevOps|

Most IT teams use a lengthy process that hides broken builds and software integration issues until the end of a release cycle. By then, identifying people responsible for breaks and diagnosing their missteps is an exhausting chore. A process of continuous builds will help your team more quickly identify the origins of broken software.

Comments Off on The 2-week COBOL Sprint: Developing a Process of Continuous Builds

The 2-Week COBOL Sprint: Having a Critical Conversation About Agile

By | March 23rd, 2016|COBOL, DevOps, Workforce|

Perhaps you've realized how poisonous distrust is to your organization. Productivity is suffering, but you’ve discovered Agile can help. Now it’s time to start a conversation with business leaders about becoming Agile and adopting processes like the 2-week COBOL sprint.

Comments Off on The 2-Week COBOL Sprint: Having a Critical Conversation About Agile

The 2-Week COBOL Sprint: How Agile Mends Broken Trust

By | March 7th, 2016|Agile Development, App Performance, COBOL, DevOps|

The bottom line is communication and transparency lead to improved trust among all groups in an organization. Starting with the initial process of establishing business requirements, to the last stage of operating the resulting programs, high frequency communication improves the trust and speed of getting new software to production.

Comments Off on The 2-Week COBOL Sprint: How Agile Mends Broken Trust

The 2-Week COBOL Sprint: Why Mainframe Shops Need It

By | February 9th, 2016|Agile Development, COBOL, DevOps|

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.

Comments Off on The 2-Week COBOL Sprint: Why Mainframe Shops Need It