Software componentization has made software more unpredictable because unforeseen conditions can cause components to interact in ways we hadn’t imagined. Greater complexity, increased user expectations, and our desire to use agile with ever increasing velocity require that we actively manage uncertainties and risks. Classic risk management identifies risks and prioritizes them to determine impact to the project, but how does that differ in an agile project? Agile is designed to handle uncertainty in requirements as new features are requested and priorities shift. What about the...
Philip Lew
XBOSoft
After working in various management and technical positions in software development and product management, Philip Lew leads XBOSoft’s direction and strategy as CEO. A speaker at numerous trade and academic conferences, Phil has worked with hundreds of organizations to assess the quality of their software, examine software quality processes, and set forth measurement plans to improve software quality using systematic methods. His Ph.D. research in software quality and usability resulted in several IEEE and ACM journal publications and in various trade journals as well. Find out more about Philip at xbosoft.com.