Thursday, January 8, 2026

Firewall Challenge Week 3 – DEV Community

Keep Your Ubuntu-based VPN Server Up to Date

Enterprise-Grade Security for Small Businesses with Linux and Open Source

Ethics for Ephemeral Signals – A Manifesto

When Regex Falls Short – Auditing Discord Bots with AI Reasoning Models

Cisco Live 2025: Bridging the Gap in the Digital Workplace to Achieve ‘Distance Zero’

Agentforce London: Salesforce Reports 78% of UK Companies Embrace Agentic AI

WhatsApp Aims to Collaborate with Apple on Legal Challenge Against Home Office Encryption Directives

AI and the Creative Industries: A Misguided Decision by the UK Government

Agile projects fail due to lack of upfront specifications.

New research on IT project management has revealed that nearly two-thirds of projects utilizing the Agile Manifesto end up failing. The study, carried out for the book “Impact engineering,” showed that 65% of software projects that implement Agile engineering practices are unable to meet deadlines, stay within budget, and maintain high-quality standards.

Despite Agile’s focus on valuing individuals and interactions over processes and tools, a survey of 600 software engineers from the UK and US found that projects following Agile Manifesto practices have a 268% higher failure rate compared to those that do not. The research highlighted that projects with clearly defined specifications before development were more likely to succeed, emphasizing the importance of having a robust requirements engineering process.

Junade Ali, the author of “Impact engineering,” emphasized the need to question Agile’s popularity in light of the high failure rates. He stressed the importance of creating a work environment that fosters open communication, problem-solving, and prevents developer burnout. The study also explored why transformation initiatives often fail, revealing that a significant number of digital and Agile transformations do not meet their objectives.

The research suggested that incorporating impact engineering practices could significantly reduce the failure rate of transformation projects. In the UK, this could potentially lead to annual savings of £7 billion, while in the US, it could result in $115 billion less being wasted on failed R&D projects. Despite these findings, the study also highlighted that software engineers in the UK are less likely to feel empowered to address problems compared to their US counterparts.

Ali urged for a shift in perspective, likening IT systems to socio-technical systems where both human and technical factors are crucial for success. He emphasized the need for a collaborative approach, similar to the teamwork in an operating theatre or the quick thinking of pilots in an aircraft cockpit, to ensure the success and safety of IT projects.