How to balance ISO certification with agile software engineering?
Hi all -- I work at a startup that develops enterprise software. Over the years, many processes have materialized, making our process to bring value into the product cumbersome and stifling.
Any time I suggest lightening the process, management falls back on the claim that we have to stay ISO certified so we have to do XYZ!
The bratty kid inside me wants to pound on the floor and 'just get it done', but I would love to see if the folks here have worked in ISO certified software shops to understand if there's a way to balance the quality management benefits of ISO with fast paced software development cycles. Looking forward to reading people's thoughts...
No comments yet.