Project Management & BA
- ·Requirements written down, scoped and sequenced before code gets written.
- ·Agile delivery in sprints with the state of the work visible at all times.
- ·Receipts: all Kredit Hero sprint milestones delivered 15% ahead of schedule.
| Delivered by | product-manager · · |
| Skills used | spec-it |
Receipts
What this involves
Business analysis is the discipline of making sure the thing being built is the thing that was needed, and it is cheap compared to discovering the gap after delivery. The work is concrete: map the workflow as it actually runs, write requirements precise enough to be disagreed with, and get acceptance criteria agreed before a sprint starts rather than during review.
The receipt is a delivery record rather than a methodology. On Kredit Hero: AI Credit App, every sprint milestone was delivered 15% ahead of schedule, on a product that reached 1,000+ users in its first 30 days.
The academic version of the same work carries its own mark: a full-stack capstone taken from requirements gathering through deployment was placed Top 3 Best Capstone Project at UST CICS, out of a BS Information Technology cohort in which he ranked first.
The delivery style is lightweight Agile adapted to small teams: short sprints, progress visible without asking for it, and decisions surfaced when they are needed rather than batched into a status meeting.
On Kredit Hero, every sprint milestone was delivered 15% ahead of schedule.
How the work runs
1. Discovery
We agree what the project has to achieve, what it must not break, and how we will both know it worked, before any code is written.
2. Build
The work is built with an AI agent as the working partner and a human reviewing every change before it lands. You get commits you can read rather than a status update.
3. Review
You review running software at each milestone, not a screenshot of it, and the next milestone absorbs what you send back.
4. Launch
We deploy to production with checks in the pipeline and alerting that reaches a human, and you hold the repository and the infrastructure accounts.
Questions people actually ask
What does a business analysis engagement produce?
A requirements document, a user story backlog, process flow diagrams, a data model and an acceptance criteria framework. The test of whether they were worth commissioning is whether a developer who was not in the room can build from them without a second discovery call.
Do I need this if I already have a project manager?
Not if your project manager can read a schema and argue with an engineer about a trade-off. The gap this fills is technical literacy rather than coordination, and it shows up as requirements that are agreed by everyone and buildable by nobody.
Can the same person manage the project and build it?
Yes, and it removes the translation layer between planning and execution, which is where most requirement drift happens. The cost is the loss of an independent check on the plan, so on anything large enough to matter the acceptance criteria should be signed off by the client rather than by the builder.
What does 'ahead of schedule' mean on the Kredit Hero record?
It means the sprint milestones on that engagement were delivered 15% ahead of schedule against the dates committed at sprint planning, over the period from July to December 2025. It is a delivery-pace figure from one engagement, and it is stated as that rather than as a rate anyone should expect by default.