Posts Tagged "quality models"
Understanding a technical debt model
Oh yeah! Technical debt, here we go again. Everybody working in quality assurance these days has heard something about technical debt. We are even talking -a lot- about it, if you visit this blog often you have surely read some of the articles devoted to this popular, but sometimes not so well understood, topic.
The key for success of any technical debt model is how to transform quality defect units (abstract and not linear) in monetary units (concrete and linear) to help understand the size of the aggregated problem.
Read MoreOptimyth Software’s infancy and first steps
Today we will review the origins and infancy Optimyth through one of the first Optimyth’s implementation projects in a customer in the insurance industry(*). We are talking about one of the leading insurance companies in Spain and South America, which relied on Optimyth Software to take its first steps in the world of quality based on static analysis only, when checKing QA was still a project and Optimyth began its career with its static analysis engine, QAKing. In fact, thanks to the work done on this customer, Optimyth’s products took a quantum leap in their evolution developing the embryo of what now is checKing QA.
Read MoreThe destiny of your software (and your business) is in your hands
When I was a kid I discovered the “Choose your own adventure” game books. The concept has probably evolved with the years but in those days it was innovative and simple at the same time. They were books written from a second-person point of view, with the reader assuming the role of the protagonist and making choices that determine the main character’s actions and the plot’s outcome.
This kind of children’s literature came to my mind when trying to explain what it means for a company to make investment decisions regarding application development.
Read MoreALM SQA Certification. The Optimyth Approach
When we think about Application Lifecycle Management and many other IT processes that complement it, independently of the various possible methodological approaches at hand, the following schema proposes two axes to observe the portfolio of your software assets (APM), and the projects required for their development and evolution in time (PPM).
Read MoreDon’t let the numbers fool you
Eduardo Aguado’s latest article about technical debt, earlier this week, has created some controversy inside and outside Optimyth. I would like to give my point view, and I think a comment in Eduardo’s article is not enough. Technical debt is something that is worth measuring, it provides valuable information, as Eduardo said, but it is true that you have to look beyond the cold numbers. And bear in mind that what we are trying to do here is to quantify a metaphor!
So how do you look beyond? What is that valuable information it provides? and, are the numbers really useless?
Read More
button in the bottom right corner