Vienna, Austria – January, 18th-21st, 2016: It’s all about “Simple, Good, Working Software” 350 Quality Assurance experts from throughout Europe spent 2 days at the Software Quality Days Conference in Vienna, Austria sharing innovation, ideas and strategies on software QA and delivery. There were 6 tracks over 2 days. QACube presented its latest version of QA visual analytics and dashboards to solve the QA Big Data problem of automated data aggregation and consolidation. QACube saves valuable time for the software delivery teams by eliminating the need for manual QA reporting with visual graphics that support the QA process. There were many excellent tracks and one entitled “Beyond breaking bad. Quality and efficiency in agile in ten easy lessons’’, by Sander Hoogendoorn, CTO of a major insurance company in the NL, that was quite provocative and provided practical approaches to the challenges of delivering “simple, good, working software”.
RE Think Tight Sprints
I managed to get one of the last available seats in the room directly behind Tom Gilb, Independent Computer Software Professional, aka the grandfather of agile, as Sander provided some very practical points about software quality. OK, so there were some points about sprint cycle times being a bit too rigidly adhered to, as not everything makes sense for a 2-4 week sprint Here are some of the things that resonated from Sander’s Keynote:
Your Requirements Will Change
“25% of requirements will change in a project. They will simply disappear. Often you may need to go back and change what you have done before in an iterative process. Agile is not a silver bullet either, as you must define what success and failure in a project is. Software Development is more like a big puzzle to solve where you have to find the right direction, where you provide nice, clean, simple code. It’s a highly creative process - not like building a car on an assembly line. Developers don’t always know how long it will take. It’s a non-linear process.’’
Visualize Your Flow
Sander also talked about “visualizing your flow in projects” and going beyond the 3 Big Scrum Board Categories of “To Do”, “Work in Progress (WIP)”, and “Done”, while breaking down the flow of the WIP items and managing the bottlenecks. “The workflow is only as strong as the weakest link.”
What Value is Being Delivered?
“The traditional Quality Triangle, with the benefits of achieving the scope/requirements, with the right budget/resources, and on time/schedule, is now under scrutiny for the new dimension of value.” “How do you know that you delivered the right value for the optimized time and budget and with the requisite quality? Providing a minimally viable product first, and then enriching out the feature set later, can be more efficient and effective in getting results.” As we discussed a few of these things, I realized that asking “why?”, and even “why not?, can lead to some interesting answers. “What is the value?” of what is being delivered is one of the key things that should be known by everyone involved in the process, of delivering what Sander calls, “simple, good, working software”.
QACube enables software testing visibility and transparency with QA Visual Analytics and Dashboard Reporting. Banks, insurance companies, financial services and telecommunications providers can reduce risks and make better decisions through role-based, graphic reporting while simultaneously lowering costs, optimizing collaboration and improving time-to-market. www.qacube.com