Banking Technology Experts

If you're looking for unbiased information on how to move your mainframe development team to an agile development process, then Banktek's Mainframe Agile is what you're looking for.

When we can, we will be publishing new articles on some of the issues and problems related to the migration of mainframe development shops to the new agile methodologies which are generally centered around Object Orientated systems.

Check out Mainframe Agile

Agile methodologies have a very different documentation output than traditional methodologies. So how does agile manage the business signoff process?

I am currently working on a mainframe system implementation using a very pure version of agile - including Test driven development, and automated acceptance testing. I have had a number of people on the project (and their managers, and their managers managers) comment about the lack of documentation, approvals and audit for the project. While I would note that many of these concerns can be dismissed as lack of education on the agile process, many of then come from years of beat up from the business on unfulfilled promises and the need for IT to protects it's behind (the usual IT/Business wrestling match). In order to make people comfortable with the agile way, it's important for people to understand what practices in agile replace the formal acceptance and sign off processes of the waterfall software development life cycle.