Contact Info

One Campus Martius

Phone: 1-800-COMPUWARE

Web: compuware.com

About Glenn Everitt

Glenn Everitt joined Compuware as part of a startup acquisition. He was the Chief Architect of the startup’s core application. Glenn has architected products that run on Mobile, Windows, Linux and Mainframe platforms. He is actively involved in technical due diligence of Compuware acquisition efforts. Glenn is currently working with Product Management on product strategy and its technical feasibility.

Forget Mainframe Application Migration—Fix Your COBOL Programs

By | October 27th, 2016|Agile Dev, App Performance, COBOL|

The time and cost of migrating off the mainframe isn’t economically viable, but modernizing the mainframe with new tools and processes is. It’s time to stop fantasizing about moving off the mainframe and start modernizing, or at least fix, your COBOL programs instead.

Comments Off on Forget Mainframe Application Migration—Fix Your COBOL Programs

The 2-Week COBOL Sprint: Agile Feedback Loops

By | May 31st, 2016|Agile Dev, 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 Dev, 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: How to Build a Scrum Team

By | April 18th, 2016|Agile Dev, COBOL, DevOps|

Mainframe shops need Agile processes like the 2-week COBOL sprint to more quickly develop and deliver software for customers in the digital economy. To carry this out, you build a scrum team comprised of people across functional areas committed to daily interaction.

Comments Off on The 2-Week COBOL Sprint: How to Build a Scrum Team

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 Dev, 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 Dev, 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