Many of us today believe that an agile methodology provides benefits in improved code quality, better fit to requirements, and lower risk of failure. However, a common criticism leveled at this approach is that the path of development may meander, involving rework due to a lack of up-front requirements and architecture definition.
Advisor
About The Author
Tom Bragg has over 30 years of experience working with high technology and information systems for clients in industry and government. He has defined software development processes for organizations ranging from small development firms of less than a dozen engineers, to multi-modal development processes for a Fortune 50 corporation. He teaches advanced software topics at George Washington University, and has written for Federal Computer Week and… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.