The build-or-buy question gets asked too early, and usually before anyone has written down what the software actually has to do. A platform chosen against a vague brief tends to get re-chosen within a couple of years, at a second round of cost.
This coverage sits mostly in the stretch between selection and go-live, where implementations quietly lose their schedule, and on the ownership question that follows delivery — what has to exist inside the business, in documentation and internal capability, before a vendor can reasonably step back.
The angles this subject is covered from, and what each one is for.
The build-or-buy question is usually asked too early, before anyone has written down what the software has to do. Our coverage starts with the specification, because a platform chosen against a vague brief will be re-chosen within two years.
Selection gets attention and go-live gets attention; the configuration and migration between them is where projects quietly lose their schedule. This subject stays with that middle stretch.
A delivered system that nobody inside the business can change is a dependency, not an asset. We write about handover, documentation and the internal capability that has to exist by the time a vendor steps back.
Reading about a subject is the first step. LGS can take it from understanding the opportunity to structuring and executing the next move.
