¿Calidad en seguridad o seguridad en la calidad?

portada wqrEl último World Quality Report, publicado por Sogeti este mismo mes ha puesto de relieve varias circunstancias que merecen ser repasadas para comprender la situación de la calidad en el mundo y, sobre todo, dado que éste es un post de ciberseguridad, la seguridad como una parte importante de la misma. Read more

WORLD QUALITY REPORT 2015-2016

infografia wqr0Disrupciones tecnológicas como Internet of Things (IoT), Big Data y Movilidad están dando lugar a transformaciones de negocio más rápidas que nunca. Las empresas tienen que moverse rápidamente para mantenerse a la vanguardia, competir y adaptarse al nuevo estilo de negocio.

Read more

Principales conclusiones del VI Informe “World Quality Report”

wqr

Sogeti, Capgemini y HP publican el VI Informe World Quality Report, el más amplio estudio de Testing y Calidad de Software a nivel mundial y la fuente más completa de análisis de este mercado. Este informe anual está basado en 1.543 entrevistas a Directores de IT de 25 países, entre ellos 20 empresas españolas. A continuación recopilamos para ti las principales conclusiones del estudio. Read more

Reduce Tomorrow’s Rework by Addressing Knowledge Debt Today

alberttortoctubreSoftware maintenance effort usually represents between 50% and 90% of the total budget that companies invest in software engineering activities. Sogeti’s World Quality Report concludes, in alignment with existing studies and software professional experiences, that once a system is released, we usually need to come back to it (for corrective maintenance, evolution, quality assurance activities, etc.). At this point, if a crosswise knowledge management strategy has not been considered, rework may arise, and many times, it may be too late to address it without overcosts. There are several day-to-day examples that fall into this situation: testers that need to recover the requirements in order to know what to test effectively, maintenance people that need to rethink about current and expected system functions behavior, difficult evolution due to loss knowledge, etc. Addressing such situations is a key challenge in many organizations and requires investment strategies when planning software quality activities in a project. The impact of expected “tomorrow’s” rework needs to be adequately considered in advance when performing first-forward development “today”. Therefore, it is necessary to think about which artifacts will be needed “tomorrow” in the likely case that somebody needs to come back to work on the system again for maintenance, evolution or quality assurance activities. Read more

IS IT A GOOD IDEA SOLVING TEST ENVIRONMENT PROBLEMS “LATER”?

In recent years, many companies focus on improving their test process. The aim is that the improvements will lead to measurable improvements in quality, faster time-to-market, cost reduction and more efficient IT operational processes. Still, they think it is best to first establish a good test process and then consider if they need to improve their test environment. Read more

Agile (testing) – the final solution?

I am not sure about that! I think our clients – the business – will expect more of us in the near future. The World Quality Report 2013-14 found that 46% organizations don’t have a specific approach to testing in agile projects. They are adapting testing methodologies based on waterfall development models. And as many as 87% of businesses in the Nordics report that they are using agile, but larger companies are typically seen to implement only certain elements of agile and experience greater difficulties adapting their processes, methods and people to the agile ways. We have to dig in to these challenges and find solutions for the areas not adapted by the companies.

Read more