Securing Software Development: Integrating InfoSec and Scrum Teams

If containers were not standardized, ships wouldn’t be able to carry as much cargo in such a short amount of time

Originally published at https://hopefullysurprising.com.

As a manager or a software engineer working with Scrum methodology, you might be very well aware of the underlying principles of an effective workflow that maximises the outcome of efforts by establishing a universal pipeline for feature requests from business to the market and back. But it shouldn’t be surprising if not all the parts of your organisation follow the principles of the Agile process and Scrum in particular. Each organisation unit, each part of the overall process should be free to choose the approach that works the best.

In a situation when requirements for a development team using Scrum come from external sources, it’s critical to establish correct expectations on input and output of the sub-processes driven by different yet interacting teams.

The key to creating successful process here is understanding that a robust Scrum team operates as a streamlined and effective pipeline, efficiently translating formulated business requests into tangible outcomes. However, when these requests arrive in unfamiliar formats, a disconnect emerges, hindering the realisation of objectives. In the worst cases, that might significantly impact feature delivery (for the whole team) due to prolonged investigation and/or…