Scoping & Technical Audit Sprint
Teams with an idea or a struggling system who need a plan before spending on build.
You get
- Scope and priorities
- Architecture and risk review
- Costed delivery roadmap
Yaoundé, Cameroon. Available for TPM roles & select projects.
Driving TechnicalDelivery & BuildingHigh-Impact SoftwareSolutions.
Software Engineer & MBA in Project Management student specializing in agile delivery, system architecture, and operational web solutions for FinTech, Logistics, and growing businesses.
Agile / Scrum, MBA PM Student, Bilingual EN / FR.
4+
Years of engineering experience
End-to-end
Delivery ownership, scope to release
Audit-ready
Data systems and financial records
Proof, not promises.
Real projects, told the way I run them: the problem, how delivery was planned, what was built, and what changed for the business.
EdTech / Training
E-Learning Platforms for Training Providers
Training moved from scattered files and manual follow-up to platforms that track every learner and issue certificates automatically.
- 312
- Learners enrolled
- 48%
- Course completion rate
Non-profit / Events
Registration, Payment and Check-in Platform for a Charity Race
Registration, payment confirmation and race-day check-in ran through one system with a full audit trail.
- 1,350
- Participants registered
- 94%
- Payments confirmed automatically
SME operations
Operations & KPI Digitization for a Beauty Salon
The owner sees revenue and staff activity daily, and month-end reporting went from two days to under an hour.
- 2 days to 1 hour
- Month-end reporting
- Monthly to daily
- Revenue visibility
HealthTech / Product
MediQube: Clinic Management for West Africa
In a clinic pilot, no-shows fell from 31% to 14% with WhatsApp booking and automated reminders.
- 31% to 14%
- Missed appointments
- 68%
- Bookings via WhatsApp
A delivery system, not a hope.
Software projects slip when scope, risk and communication are left to chance. Every engagement runs on the same five steps, and each one leaves an artifact you can inspect.
1. Discover
Understand the operation, the stakeholders and the numbers that matter before any code is written.
Example artifact Stakeholder map
| Who | What they need | Involvement |
|---|---|---|
| Owner / sponsor | Decides scope and budget | Decides |
| Operations lead | A tool they can use daily | Daily |
| Finance | Audit-ready records | Reviews |
| Field staff | Fast, simple data entry | Daily |
Artifacts: Stakeholder map, Problem statement, Success KPIs.
2. Scope
Turn goals into a bounded plan: what is in, what is out, and what it costs in time.
Example artifact Scope document
In scope
- Sales and expense capture
- Role-based access
- Monthly report export
Not in this release
- Payroll
- Native mobile app
- Accounting software sync
Artifacts: Scope document, Roadmap, Architecture sketch.
3. Sprint
Short iterations with a visible board, working demos and early feedback.
Example artifact Sprint board
To do
- Expense categories
- Export to CSV
In progress
- Daily revenue dashboard
- Staff roles and permissions
Done
- Login and two-factor
- Sales entry form
Artifacts: Sprint board, Weekly demo, Decision log.
4. Ship
Release with tests, data checks and a handover your team can actually run.
Example artifact Release checklist
- Automated tests passing
- Data migrated and checked
- Runbook written
- Team trained
- Rollback plan ready
Artifacts: Release notes, Runbook, Training session.
5. Govern
Keep risk, quality and scope under control, then measure the result against the KPIs.
Example artifact Risk register
| Risk | Impact | Owner | Status |
|---|---|---|---|
| Payment confirmations arrive late | High | Backend | Mitigated |
| Scope grows during sprint 4 | Medium | Project lead | Watching |
| Key person unavailable | High | Team lead | Open |
Artifacts: Risk register, KPI dashboard, Retrospective.
Technical execution
Angular, Frontend architecture, Backend architecture, Database systems, API design.
Project delivery
Agile / Scrum, Scope control, Stakeholder alignment, Risk & governance.
Three ways to get a project delivered.
Clear scope, clear deliverables. Pick the starting point that fits where you are.
Fixed-scope Web App or Dashboard Build
SMEs that need an operational tool: KPIs, records, workflows, reporting.
You get
- Working, tested application
- KPI and audit-ready reporting
- Handover and documentation
Technical Delivery Lead (fractional TPM)
Teams with developers but no one owning cadence, risk and stakeholder communication.
You get
- Sprint planning and governance
- Stakeholder reporting
- Unblocking and risk control
- Target roles
- Technical Project Manager, IT Project Manager, Product Owner, Delivery Officer
- Background
- Software engineer, 4+ years
- Education
- MBA in Project Management (in progress); Bachelor of Technology in Project Management
- Strengths
- Agile delivery, scope control, risk & governance, API and system design
- Languages
- English, French
- Location / timezone
- Cameroon (WAT, UTC+1)
From building systems to delivering them.
I started as a software engineer: designing APIs, building web applications and working with data-heavy systems. Over time I found that the hardest problems were rarely technical. They were about scope, communication and keeping a team pointed at the outcome.
That is why I am completing an MBA in Project Management. I want to run delivery with the same rigour I bring to code: clear scope, visible progress, honest risk reporting, and results measured in business terms.
-
Engineer
Built web applications, APIs and database-backed systems.
-
Delivery
Took ownership of scope, sprints and stakeholder alignment.
-
MBA Now
Formalising project management and business leadership.
Straight answers.
How does an engagement work?
We start with a short call to understand the problem. If it is a fit, I propose a scoped plan with deliverables and a timeline. Work then runs in short sprints with a visible board and regular demos.
Do you work across time zones?
Yes. I am based in Cameroon (UTC+1), which overlaps well with Europe and the Americas, and I run async updates so progress never depends on a meeting.
Which languages can we work in?
English and French, for both delivery and documentation.
How is pricing structured?
Pricing depends on scope. After a first call I send a clear, itemised quote so you know what you are paying for before we start.
Are you open to full-time roles?
Yes, I am open to Technical Project Manager, IT Project Manager, Product Owner and Delivery Officer roles. Download the resume above or reach out directly.
What happens after launch?
Every build ends with a runbook, a handover session and a retrospective. Ongoing support is available if you want it, never forced.
Let's scope it.
Tell me what you are trying to achieve. I reply within two working days.