Can Governance and Agile Get Along?
Traditional testing practices are the hands that slow agile teams to a stagnant, waterfall state. Testing itself isn’t bad or anti-agile. How you think about testing can make or break your agile success though.
For companies building solutions in regulated industries, fear of innovating on traditional testing practices will likely lead to the undesired outcome of poor quality solutions. Negative outcomes reinforce the fear of innovating, and leadership may choose to side with recommendations from legal and governance groups rather than development teams advocating newer testing practices that require new skills, tools and culture changes.
Can governance and agile get along? Yes. But you cannot start your agile journey from your familiar waterfall practices and status quo; no ship ever left a harbor while firmly tied to a pier. Similarly, your traditional testing practices anchor you to waterfall—no matter how many Scrum ceremonies you adopt.
An organization working in a regulated industry (healthcare, finance, etc.) has several masters. There is the organizational leadership, and there are external agencies that will shut you down if you create the potential to harm the general public. Naturally, this puts some stress on your corporate leadership as no one wants an outsider to come into their home and shut down operations.
To keep things
Please log in or sign up below to read the rest of the article.