Our Methodology - The Released Method
The pragmatic framework for building great software — fast, lean and without compromise.
What is the Released Method?
The Released Method is a battle-tested, real-world framework for delivering software that works — on time, on budget, and ready for the market.
It was created by Released Group founder Nick Beaugeard, drawing on over 25 years of product development experience across startups, enterprises, and government. It blends the best of Agile with real-world execution discipline — no fluff, no buzzwords, just results.
Whether you're building your first MVP or managing a scale-up platform, this is the method we use internally and with every client project to cut through the chaos and deliver reliable, maintainable, and commercially successful software
Why we built it?
Let’s be honest — most methodologies either give you too much ceremony or not enough structure. We’ve seen Agile teams flounder, Waterfall teams collapse, and lean startups spin in circles.
The Released Method is different. It delivers:
-
✔️ Predictable software delivery without bureaucracy
-
✔️ Startup-level speed with enterprise-level quality
-
✔️ Clear role accountability across business, tech, and design
-
✔️ A consistent, repeatable rhythm for any stage of growth
It’s principle-based, not dogmatic. It's built to work in the real world — not just in textbooks
The Six Core Pillars
The Released Method is built on six interdependent pillars. Ignore one, and the rest falter.
1. Management Reporting
Track what matters: burndown, test coverage, delivery velocity, open risks. Deliver insights — not noise — to stakeholders and teams.
2. Software Planning & Development
Move from idea to code with clear scope, defined sprints, ruthless prioritisation, and tight feedback loops.
3. Testing & Quality Assurance
Quality is baked in from day one. Unit tests, regression tests, automated pipelines — no guesswork, no finger-crossing.
4. Release Management
Automate deployment. Define environments. Control risk. Every release is a non-event — not a disaster.
5. Documentation
From code comments to SDKs and onboarding guides — documentation is part of the delivery process, not a post-it note on the backlog.
6. Selling (Customer Adoption)
Your software has to land. This includes internal enablement, external positioning, proposals, brochures, and demos that work.
📌 Selling isn't just sales — it's ensuring your product gets used, loved, and renewed.
Build and Release
Moving your project into staging and production is commonly a very painful manual process. We work hard to automate the build, test and release process, meaning you can release more often, with the full knowledge that every release works, passes all tests and is fit for purpose.