Method · Sistema Órbita
Clear project management, with progress you can see.
Sistema Órbita is how I manage every project: the phased structure of PMI's PMBOK® Guide, the iterative delivery of Scrum and the quality discipline of ISO and Lean Six Sigma, scaled to the real size of your operation.
The commitment
«Every decision is put in writing and every result is measured with data, not impressions.»
Hybrid life cycle
Five phases, three gates, delivery in sprints
A hybrid approach as described by PMI: phases and gates bring order and control; inside the build, Scrum delivers working increments you review every few weeks.
Framing
We define the problem, goal, stakeholders and what stays out, in a project charter.
Discovery
I learn your current process, we measure the baseline and turn it into a prioritised backlog.
Design
We design the future process and agree acceptance criteria and a definition of done.
Build
I build in short sprints; at every review you test an increment that already works.
Adoption
Transition to operations, training and benefit measurement until your team owns it.
- C1 · Kick-off
- We approve the charter: scope, goals, owners and resources before investing.
- C2 · Design validation
- You review the design and the prioritised backlog; nothing is built without your approval.
- C3 · Close
- We confirm results against the baseline and hand the operation over to your team.
Throughout the cycle: monitoring and control of scope, risks and quality, plus continuous improvement with the PDCA cycle (plan, do, check, act).
Agile where it adds value
Scrum in the build: you see progress, not a report
Instead of waiting months for a final delivery, the system grows in small increments. You decide what matters most and see it working before we move on.
Sprint planning
We agree what goes into the next cycle, taken from the backlog you prioritise.
Visible tracking
A shared board shows what is in progress, what is done and what is blocked.
Sprint review
You test the working increment and your feedback adjusts the backlog.
Retrospective
We review how we work and improve the process in the next cycle.
Your role: Product Owner, who prioritises and approves. Mine: managing the project, facilitating the working rhythm and building the system.
Tailored to each case
The method fits your project, not the other way round
Digitising a form is not the same as building a new system. As PMI's guide recommends, we tailor the approach to the kind of challenge and only apply the rigour that adds value.
Digitise a process
Paper forms, Excel sheets or emails filled in by hand today: understood, redesigned and replaced.
Tailored system
A new solution for a need with no tool, with an agreed scope and clear acceptance criteria.
Data & KPIs
Scattered information becomes dashboards that let you decide with data.
Knowledge management
Your team's know-how, documented and connected, no longer depends on a single person.
Prototype & validation
Test an idea before investing in it: learning fast is a result too.
Documentation is scaled to the project —light, standard or full—: you pay for the rigour you need, not for bureaucracy.
Provenance
Built on frameworks your company already knows
Órbita doesn't invent a methodology: it applies recognised project-management and quality frameworks, taking from each what adds value to projects your size, without committees or red tape that doesn't apply.
PMBOK® Guide
Project Management Institute (PMI)
Phased life cycle with decision reviews, a hybrid predictive-agile approach, tailored rigour and management of scope, stakeholders and risk.
Scrum
The Scrum Guide · Schwaber & Sutherland
Short sprints with working increments, a backlog prioritised by the Product Owner, and a review and retrospective every cycle.
Agile
Agile Manifesto · Agile Practice Guide (PMI)
Deliver value early and often, collaborate with the client throughout the project and respond to change.
ISO 21502
Project management
Life-cycle gates, transition to operations and benefits measured after closure.
ISO 9001
Quality management
Process approach, evidence-based decisions and continuous improvement with the PDCA cycle.
Lean Six Sigma
DMAIC
Define and measure before improving: baseline, waste removal and control of the improved process.
Principles
Four non-negotiable rules
Process first, software second
Digitising a process you don't understand only automates the problem. First we organise it; then we bring it to technology.
ISO 9001 · Lean
Working progress, not promises
Every sprint ends in something you can test. If the course needs to change, we know in weeks, not at the end.
Scrum · Agile Manifesto
Built is not adopted
The project ends when your team uses it with ease, not when the system works.
PMI · ISO 21502 · ADKAR
Measured results, not assumed ones
We measure the starting point to prove the change. If something can't be measured, we say so clearly.
Lean Six Sigma · DMAIC
And also
- Every project has a Product Owner on your side who prioritises and approves.
- What stays out of scope is agreed in writing.
- Every key decision is recorded with the alternatives considered.
- Documentation is built during the project, not at the end.
- The system includes how to measure its own performance.
In practice
Leaders App
At Darnel Group (Ajover), process first meant mapping the Standard Work and updating procedures before writing the first screen: an AI agent on top of outdated documentation spreads the error instead of fixing it.
This site
Every case published here comes from the project's real documentation: I only show verified results.
Shall we apply the method to your operation?
We start with framing: what problem the system solves and what stays out.