In traditional agile approaches, retrospectives are valuable to team improvement. However, when teams encounter organizational issues beyond their control, such as project structure, interorganizational communication, or resources, it's more difficult. Here's how to expand continuous improvement to the whole company.
Alan Crouch is a senior software security specialist with Coveros, a Virginia-based firm focused on agile, software quality, and application security. Alan has worked closely with federal agencies and private companies to advise, audit, and support IT security and governance teams. In addition to his cybersecurity experience, he has a strong background in software engineering, test analysis, test automation, and security testing. Alan has focused his career on building secure software and developing better software security practices. You can contact Alan at [email protected].
Connect with Me
All Stories by Alan Crouch
The Equifax cyber security breach compromised millions of people's confidential information. If you’re worried about how you can prevent an IT disaster of this scale at your own organization, there is an answer: DevSecOps, which incorporates security into DevOps practices to ensure weaknesses are exposed early on.
Many organizations turning to agile believe it means you don't have to do any planning. This couldn't be further from the truth. A healthy agile team does just as much (if not more) planning than a team using a waterfall methodology. Preparing and setting goals sets up the team for a more successful agile adoption.
Security practices traditionally have followed a waterfall model, adding security testing on at the end. Organizations need to coach their security programs and testers to prioritize analysis and risk, much like we do with agile stories, to better incorporate security defects with other feature work along the way.
Most mobile app development teams lack a security testing practice, or if they do have one, it lacks the maturity to be effective. But the great security practices are not necessarily those that spend the most money or have the most engineers. It’s the ones that have adopted these three fundamental concepts.