Services
Custom software
Custom software is for the workflow a package will not carry. IncogX builds web, mobile, and enterprise systems as a single delivery: one backlog, one definition of done, and a sponsor who can see the increment.
In brief, then in detail
- Product, not a pile of tickets. The backlog is ordered by outcome. A sprint takes a slice that a user can recognise, not a layer that only an engineer can demo.
- Web, mobile, and enterprise. Portals, operational tools, APIs, and the systems of record around them. The same quality bar, whichever surface the user touches.
- Change, in the open. New scope is welcome when the learning is real. It is estimated, and something else moves, or the date and cost move with it.
- An increment you can reject. Every two weeks there is software. If it is wrong, that is discovered in the review, not at launch.
How it is run
Delivery is Scrum. A product owner, usually on the client side, orders the backlog. IncogX facilitates the events, removes impediments, and builds the increment. Planning sets the sprint goal. The daily scrum is for the team, not a status theatre for managers. The review is for the product. The retrospective is for the way of working. Code review and a passing pipeline sit inside the definition of done.
CadenceTwo-week sprints
DoneReviewed, tested, and deployable
OwnershipClient owns the product decisions
Engineering practice
- Product backlog
- Sprint goal
- Code review
- CI pipeline
- Definition of done
- Working increment
Terms, in plain language
- Product backlog. The ordered list of work. Order is a business decision. Size is a team decision.
- Sprint. A fixed period, here two weeks, that ends with a usable increment. The goal does not change mid-sprint without a conscious stop.
- Increment. The sum of done work. If it is not releasable, it is not done, even if the code exists.
- Definition of done. The shared checklist: review, tests, security notes, and anything else required before work can be called finished.