Scale and enhance your DevOps toolchain

Implementing and adopting all the possible opportunities to improve a team's DevOps effectiveness is likely to be only possible in multiple iterations - there's no need to "leap a tall building in a single bound"!

Having completed an iteration of the planned approach, this is the time to reflect on the progress made and to evaluate the next steps.

Examples of topics to consider could include:

• Do the product or service planning processes create a pipeline of tasks that work well with agile development working practices?
• Have you realized any other older processes can be better aligned with a Git-native approach? For example, are you using pull requests effectively as a quality gate that promotes knowledge sharing?
• Can technical debt be addressed more effectively? For example, your team's main branch can be kept clean of dead code (if it is not already). With the complete history of the code base available in the Git repository, the team can rest assured that even if the dead code is deleted in a commit, it can be easily restored from an earlier commit in the history if needed.
• If you have not yet moved away from static environments for testing and the route-to-live process, is it time to adopt a more dynamic provisioning approach?

To see how others are taking advantage of the opportunities, visit the Development and Pipeline Community on IBM® TechXchange, where you can get the latest IBM Z® DevOps news, share your questions and thoughts with the wider community, access additional useful resources, and more.