{"id":46,"date":"2026-09-04T16:00:03","date_gmt":"2026-09-04T16:00:03","guid":{"rendered":"https:\/\/qualityreforge.com\/?page_id=46"},"modified":"2026-09-13T12:20:33","modified_gmt":"2026-09-13T12:20:33","slug":"home","status":"publish","type":"page","link":"https:\/\/qualityreforge.com\/","title":{"rendered":"Home"},"content":{"rendered":"\n
\n

Notes from the anvil of software quality<\/p>\n\n\n\n

Quality is forged<\/mark>,
not inspected in.<\/h1>\n\n\n\n

Agile promised speed. What it quietly cost was craft<\/em> \u2014 and quality assurance paid the bill. This is a record of where the practice breaks, why it keeps breaking, and what re-forging it actually looks like.<\/p>\n\n\n\n

\n
Enter The Forge<\/a><\/div>\n\n\n\n
Read the manifesto<\/a><\/div>\n<\/div>\n<\/div>\n\n\n\n
\n

The Thesis<\/h2>\n\n\n\n
\n

 A blacksmith does not “test” a blade after it’s made. The craft is in the folding, the tempering, the thousand small decisions before the edge ever meets a target. Quality assurance was meant to work the same way<\/strong> \u2014 woven into the making, not bolted on at the end.<\/p>\n\n\n\n

Somewhere in the industry’s rush toward two-week sprints and velocity charts, QA got reduced to a checkbox at the bottom of a board. Testers became ticket-closers. Craft became compliance. And when quality quietly erodes, nobody notices until the blade snaps in someone’s hand.<\/p>\n\n\n\n

This blog exists to name the specific practices \u2014 inside agile teams, inside real sprints \u2014 that hollow out QA’s value, and to argue for treating it as the skilled trade it always was. These three paragraphs do NOT need an Additional CSS class \u2014 they inherit their styling automatically from being inside .qr-manifesto.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n
\n

From the Anvil<\/h2>\n<\/div>\n\n\n\n
\n

Recent Entries<\/p>\n\n\n\n

\n

No. 001<\/p>\n\n\n\n

\n

Why ‘just add it to the sprint’ is where QA goes to die<\/h3>\n\n\n\n

Squeezing testing into the same two weeks as development isn’t agility \u2014 it’s asking the smith to quench the blade before it’s finished forging.<\/p>\n<\/div>\n\n\n\n

Agile failure<\/p>\n<\/div>\n\n\n\n

\n

No. 002<\/p>\n\n\n\n

\n

The definition of done that no one defends<\/h3>\n\n\n\n

When ‘done’ quietly stops including ‘tested,’ QA becomes the department that argues with velocity \u2014 and loses.<\/p>\n<\/div>\n\n\n\n

Team Dynamics<\/p>\n<\/div>\n\n\n\n

\n

No. 003<\/p>\n\n\n\n

\n

Automation is a tool, not an apprenticeship<\/h3>\n\n\n\n

Chasing coverage numbers has replaced the slower work of actually understanding what could break, and why.<\/p>\n<\/div>\n\n\n\n

Craft<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Notes from the anvil of software quality Quality is forged,not inspected in. Agile promised speed. What it quietly cost was craft \u2014 and quality assurance paid the bill. This is a record of where the practice breaks, why it keeps breaking, and what re-forging it actually looks like. The Thesis  A blacksmith does not “test” a blade after […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_monsterinsights_skip_tracking":false,"footnotes":""},"class_list":["post-46","page","type-page","status-publish","hentry"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t