Requires Free Membership to View
When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.
Hannah Smalltree, Editorial Director
This is a common issue but something that can be resolved relatively easily. First, management has to make their support of security and risk management known by spreading the message and holding people accountable. Second, get your teams in the same meetings. Have developers/QA staff attend security-related meetings and security/compliance staff attend development/QA-related meetings.
Finally, get all staff members some cross-training in the respective areas. There's no reason why security/compliance staff shouldn't know the basics of software development/quality and why developers/QA staff shouldn't know the essential concepts of information security. Pull these three things together and you'll have yourself a workable solution.
Here is some more advice for development teams battling with similar struggles:
- How to get management on board with Web 2.0 security issues
Ways to get management buy-in for Web 2.0 security testing and quality assurance and to bolster application security before deployment are given in this tip.Handling the people side of Agile software development
Expert tester advises agile development teams to adopt cross functionality, use only proven agile practices and encourage strong tester and developer relationships.Tips for software testers: Getting along with developers
End software project slowdowns caused by fighting between software testers and developers with these four tips.
This was first published in January 2010