5 entries tagged Methodology.
Our flagship rebuild is built, loaded, and in parallel testing — and still isn't in production. The shop runs on its old system, the new one runs alongside it, and go-live is targeted for November. Here's what parallel testing is for, what it has to prove, and the questions to ask before anyone switches your shop over sooner.
Every rung of this series ends with "and here's the number." This post is about the number — how a sprint's KPI gets picked in discovery, written on the quote, measured with the same instrument before and after, and what happens when it misses. Including what we do with an RFP.
Lights-out gets sold as a machine problem. Often the reason a shop can't run an unattended shift isn't the machine — it's that nothing can tell the machine what to do next without a person in the office. Here is the list of handoffs that have to happen without a human, and where that list stops at your wall.
Most bad custom-software stories start with a contract shape, not a bad programmer. How we work — three ways to scope the work, fixed prices, contingency stated instead of hidden — and why two-week fixed sprints are the shape where the buyer and the builder want the same thing.
No shame — it worked for twenty years. But the risks have changed, and there are three realistic ways out. Here's how to pick, including the two that don't involve hiring anyone like us.