AGILE

Bimodal IT Mode 2 Do's and Do Not's

Bimodal IT Mode 2 Do's and Do Not's

As IT shops are adopting bimodal operations, they encounter a multitude of issues. They want to build new applications rapidly using tools like Mendix and leveraging the AGILE principles, but they need tight controls on their deployments for many reasons such as regulatory and audit controls. Enterprises have been trying to make Mode 2 “fit” into Mode 1, and attempt to control risk the same way as they do on traditional Waterfall projects. Here are a few issues I’ve encountered over the years and my thoughts.

Bug Branches - How to avoid disrupting your mainline development

Bug Branches - How to avoid disrupting your mainline development

One thing that is inevitable in software development is that you will create bugs in your software. The question becomes how and when you deploy fixes for them. Each client has differing levels of change control processes that need to be considered when dealing with these fixes. You want to eradicate the bugs as quickly as possible, particularly if they are preventing the end users from completing their work, but you don't want to affect current main line development. I'll give you a process I use that seems to be working best after much trial and error.