Polaris. 57 best practices for IT system development and transformation
Your North Star for predictable IT projects delivery
We’re sharing Polaris — the quality standard that’s been our internal compass across new builds, transformations, and legacy systems.
For tech leads who need predictable delivery, business stakeholders who expect transparency, and development teams who value autonomy.
It provides a fixed reference point for project decision-making — especially when scope shifts and pressure mounts. It’s the result of 10+ years of delivery experience and continuous refinement of how projects are delivered predictably, without cutting corners.
Contents of the ebook
From auditing projects to building quality culture — a practical guide built on 10+ years of delivery experience.
What Polaris is and when to apply it
You’ll understand Polaris as both a quality standard and a way of thinking about IT projects. You’ll learn when it makes the most sense to use it — when launching new initiatives, during product development, and when modernising systems that need to keep running alongside the changes.
The 57 practices that make up the standard
You’ll get a structured map of 57 practices across three areas: product and process, technology and development, documentation and testing. Each area addresses a different type of risk — business, technical and operational.
How to run a Polaris audit, step by step
You’ll learn how to use Polaris in practice to assess a project: how to prepare for an audit, how to run a workshop with the team, and how to gather insights that drive decisions — not just document the current state.
Polaris areas and their owners
You’ll see how to clarify responsibility in IT projects: who owns each quality area and how to avoid situations where decisions have no clear owner.
Case studies from Inwedo projects
You’ll see real examples of improvements we’ve implemented in our projects — with the context, the decisions behind them, and the impact they had on day-to-day team work and client collaboration.
The role of QA and testing standards
You’ll learn how QA and testing work in Polaris: as a way of building quality throughout the project lifecycle, not just as a final checkpoint.
Definition of Ready and Definition of Done in practice
You’ll see how to use DoR and DoD as tools that bring structure to collaboration — setting clear expectations, reducing misunderstandings, and stabilising team rhythm.
Benefits and common pitfalls when implementing standards
You’ll learn about the benefits we’ve observed from working with a quality standard, and the most common pitfalls that come up during implementation — with guidance on how to avoid them before they affect delivery pace and quality.
Results from working with Polaris
of sprints delivered on plan (vs. 60% before Polaris)
test coverage achieved in audited projects
lower maintenance costs through reduced technical debt
What you’ll gain from this book
A guiding framework for IT project decisions
In fast-moving IT projects, it’s easy to lose sight of direction and alignment. Polaris was created as a guiding framework that helps you make consistent decisions and maintain a shared approach to quality — even when scope and assumptions evolve during delivery.
This is for everyone who wants confidence that IT projects are delivered predictably, safely, and according to clear quality standards. For business and technology leaders, engineers, QA professionals and project managers who want to deliberately build a quality culture — not through bureaucracy, but through clear principles, accountability and transparency.
-
A structured way to assess IT project quality
Without diving into operational details or relying solely on gut feeling or team declarations.
-
A solid foundation for partnership with your IT provider
Clear quality criteria, responsibilities and expectations — from project kick-off through ongoing development.
-
Better decisions on development, risk and priorities
Based on a complete picture of the project, not isolated signals or the pressure of current problems.
-
Clear quality guardrails that support team autonomy
Teams retain freedom to act, but work against a shared, understood standard.
-
One standard that works across different project types
Whether you’re launching new initiatives, evolving products, or modernising legacy systems.
-
A shared language for quality conversations across the organization
Between technical teams, leadership and business stakeholders — without misunderstandings or assumptions going unchecked.
Why Polaris — and why we’re sharing it
For centuries, sailors navigated by the North Star — a constant point in the sky that kept them on course.
In IT projects, we need the same: a fixed reference point that guides decisions even when everything around you is changing. That’s why we created Polaris.
It emerged from over ten years of work on end-to-end IT projects and team extension engagements. In 2022, we formalised it as part of an internal project audit, combined with ISO 27001 and ISO 9001 certification. This turned Polaris into a coherent, practical tool that supports everyday project decisions — not just a collection of abstract principles.
We’re sharing Polaris because we believe in a culture of openness and in the exchange of knowledge and experience. Over the years, it has helped us structure our work, learn from mistakes, and develop shared quality standards.
Now we’re putting it out there — so other teams can learn from it, draw inspiration, or simply compare their own approach to quality and collaboration.
About the author
Engineer and humanist leader with over 20 years of experience in the IT industry.
CEO of Inwedo, where he works with teams and business stakeholders on quality, security, and decision-making in IT projects — from new products to legacy system modernisation.
Author of books, as well as a blog and podcast focused on leadership, cybersecurity, and emerging technologies. In this ebook, he presents the Polaris quality standard from the perspective of a practitioner and organisational leader, showing how it supports project decisions, predictability, and accountability in day-to-day delivery.
Get a clear reference point for IT project quality
Download Polaris: 57 best practices for predictable IT delivery —
from new projects to legacy modernization.
FAQ
Polaris is a quality standard that works WITH your existing framework.
Where Scrum tells you HOW to work (sprints, ceremonies, roles), Polaris defines WHAT “done right” actually means (test coverage, documentation standards, deployment practices).
Where DevOps gives you cultural principles, Polaris gives you 57 concrete checkpoints.
Think of it as your quality compass, not another process to follow. It complements what you already do by making quality expectations explicit and auditable.
No. Polaris scales to your context.
A 3-person startup MVP will use Polaris differently than a 30-person enterprise system — but both benefit from the same core principles: clear definitions of “done,” systematic testing, and transparent communication.
Small teams might keep documentation lightweight and ceremonies flexible. Large teams implement the full framework with formal acceptance testing and comprehensive documentation.
The standard adapts to your scale, not the other way around.
100% practical implementation. It’s a playbook built from 10+ years of actual project work.
You get:
- 57 specific practices with real project examples
- Step-by-step audit process (what to check, when, and how)
- Definition of Ready and Definition of Done templates you can use tomorrow
- Real case studies
- Common pitfalls and how to avoid them
Polaris is modular by design. You might:
- Start with Product & Process (DoD, DoR, backlog management) if your main pain is unclear requirements
- Start with Technology & Development (automated tests, CI/CD) if you’re drowning in bugs
- Start with Documentation & Testing if knowledge is siloed and onboarding takes forever
Scale and combine as your team matures. You don’t need to implement all 57 practices on day one.
We offer project audits and implementation support tailored to your needs.
Whether you want:
- A one-time audit to identify gaps
- Ongoing advisory as you roll out Polaris practices
- Full project partnership with Polaris built-in from day one
Book a consultation to discuss your specific situation, or reply to any email from us after downloading the ebook.