<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
  <title>Rufouss Insights</title>
  <link>https://rufouss.com/insights.html</link>
  <atom:link href="https://rufouss.com/insights-rss.xml" rel="self" type="application/rss+xml"/>
  <description>SAP Quality Engineering, written from experience. Practical thinking on SAP testing, S/4HANA transformation, automation and assurance.</description>
  <language>en-gb</language>
  <lastBuildDate>Sun, 16 Aug 2026 09:00:00 GMT</lastBuildDate>
  <item>
    <title>Five questions worth answering before SAP go-live</title>
    <link>https://rufouss.com/five-questions-before-sap-go-live</link>
    <guid isPermaLink="true">https://rufouss.com/five-questions-before-sap-go-live</guid>
    <pubDate>Sun, 16 Aug 2026 09:00:00 GMT</pubDate>
    <category>Executive Assurance</category>
    <description>Traceability, real business coverage, production-like data, a rehearsed cutover and the evidence behind the decision — five questions that tell you more than a pass rate.</description>
  </item>
  <item>
    <title>What should we re-test after an SAP upgrade?</title>
    <link>https://rufouss.com/what-to-retest-after-an-sap-upgrade</link>
    <guid isPermaLink="true">https://rufouss.com/what-to-retest-after-an-sap-upgrade</guid>
    <pubDate>Sat, 15 Aug 2026 09:00:00 GMT</pubDate>
    <category>S/4HANA</category>
    <description>Nine areas worth validating after an SAP upgrade, what SAP’s own tools do and do not tell you about each, and how change impact should decide the depth of regression.</description>
  </item>
  <item>
    <title>Before you approve an SAP go-live, what evidence should be on the table?</title>
    <link>https://rufouss.com/evidence-before-sap-go-live</link>
    <guid isPermaLink="true">https://rufouss.com/evidence-before-sap-go-live</guid>
    <pubDate>Tue, 04 Aug 2026 09:00:00 GMT</pubDate>
    <category>Executive Assurance</category>
    <description>Leadership needs visibility into business-process coverage, material defects, unresolved dependencies and the evidence behind readiness — not another status colour.</description>
  </item>
  <item>
    <title>An S/4HANA upgrade is a business-process test, not just a technical upgrade</title>
    <link>https://rufouss.com/s4hana-upgrade-is-a-business-process-test</link>
    <guid isPermaLink="true">https://rufouss.com/s4hana-upgrade-is-a-business-process-test</guid>
    <pubDate>Tue, 28 Jul 2026 09:00:00 GMT</pubDate>
    <category>S/4HANA</category>
    <description>Custom code, business data, interfaces and process behaviour all need attention when the underlying ERP changes beneath them.</description>
  </item>
  <item>
    <title>From requirement to business process: a better way to define SAP test coverage</title>
    <link>https://rufouss.com/requirement-to-business-process-coverage</link>
    <guid isPermaLink="true">https://rufouss.com/requirement-to-business-process-coverage</guid>
    <pubDate>Tue, 21 Jul 2026 09:00:00 GMT</pubDate>
    <category>SAP Testing</category>
    <description>Meaningful coverage traces what the business expects through processes, variants, scenarios and evidence — not through a total.</description>
  </item>
  <item>
    <title>What should you automate first in SAP?</title>
    <link>https://rufouss.com/what-to-automate-first-in-sap</link>
    <guid isPermaLink="true">https://rufouss.com/what-to-automate-first-in-sap</guid>
    <pubDate>Tue, 14 Jul 2026 09:00:00 GMT</pubDate>
    <category>Automation</category>
    <description>Sustainable automation starts with stable, repeatable and business-critical processes rather than automation-volume targets.</description>
  </item>
  <item>
    <title>Five quality signals every SAP steering committee should see</title>
    <link>https://rufouss.com/five-quality-signals-steering-committee</link>
    <guid isPermaLink="true">https://rufouss.com/five-quality-signals-steering-committee</guid>
    <pubDate>Tue, 07 Jul 2026 09:00:00 GMT</pubDate>
    <category>Executive Assurance</category>
    <description>Five signals that tell a steering committee something a completion percentage cannot.</description>
  </item>
  <item>
    <title>Building regression into the S/4HANA release rhythm</title>
    <link>https://rufouss.com/regression-in-the-s4hana-release-rhythm</link>
    <guid isPermaLink="true">https://rufouss.com/regression-in-the-s4hana-release-rhythm</guid>
    <pubDate>Tue, 30 Jun 2026 09:00:00 GMT</pubDate>
    <category>S/4HANA</category>
    <description>SAP ships on its own schedule. A regression suite that is rebuilt for each release will always be behind it.</description>
  </item>
  <item>
    <title>What should testing protect during an ECC-to-S/4HANA conversion?</title>
    <link>https://rufouss.com/what-testing-protects-in-ecc-conversion</link>
    <guid isPermaLink="true">https://rufouss.com/what-testing-protects-in-ecc-conversion</guid>
    <pubDate>Tue, 23 Jun 2026 09:00:00 GMT</pubDate>
    <category>S/4HANA</category>
    <description>Six things change underneath the business during a conversion. A test strategy is a set of decisions about which of them to protect first.</description>
  </item>
  <item>
    <title>How a maintained SAP regression suite changes the economics of releases</title>
    <link>https://rufouss.com/economics-of-a-maintained-regression-suite</link>
    <guid isPermaLink="true">https://rufouss.com/economics-of-a-maintained-regression-suite</guid>
    <pubDate>Tue, 16 Jun 2026 09:00:00 GMT</pubDate>
    <category>Automation</category>
    <description>Automation does not pay back on the day it is built. It pays back on the fourth, fifth and tenth time it runs.</description>
  </item>
  <item>
    <title>One business process. Six places quality can disappear.</title>
    <link>https://rufouss.com/one-process-six-places-quality-disappears</link>
    <guid isPermaLink="true">https://rufouss.com/one-process-six-places-quality-disappears</guid>
    <pubDate>Tue, 09 Jun 2026 09:00:00 GMT</pubDate>
    <category>Field Notes</category>
    <description>Source-to-pay, followed all the way through, and the six points at which coverage quietly goes missing.</description>
  </item>
  <item>
    <title>Where AI can genuinely help SAP test design</title>
    <link>https://rufouss.com/where-ai-helps-sap-test-design</link>
    <guid isPermaLink="true">https://rufouss.com/where-ai-helps-sap-test-design</guid>
    <pubDate>Tue, 02 Jun 2026 09:00:00 GMT</pubDate>
    <category>Automation</category>
    <description>Four places AI earns its keep in SAP test design, and the judgement it does not replace.</description>
  </item>
  <item>
    <title>Testing the hand-offs: where SAP processes become enterprise processes</title>
    <link>https://rufouss.com/testing-the-handoffs</link>
    <guid isPermaLink="true">https://rufouss.com/testing-the-handoffs</guid>
    <pubDate>Tue, 26 May 2026 09:00:00 GMT</pubDate>
    <category>Field Notes</category>
    <description>Every boundary a process crosses is owned by somebody, and the gaps sit between the owners rather than inside them.</description>
  </item>
  <item>
    <title>What does “ready” actually mean in an SAP programme?</title>
    <link>https://rufouss.com/what-ready-means-in-sap</link>
    <guid isPermaLink="true">https://rufouss.com/what-ready-means-in-sap</guid>
    <pubDate>Tue, 19 May 2026 09:00:00 GMT</pubDate>
    <category>Executive Assurance</category>
    <description>Readiness is a judgement about business capability, made by named people, on evidence. It is not a number that arrives from a tool.</description>
  </item>
</channel>
</rss>
