Roadmapping for Language Engineering projects

At the beginning of each non-trivial project there is a lot of uncertainty, and typically language engineering projects are not-trivial at all.

How can you be confident this project will solve your problem?

Is a transpiler what you need in this case?

Should you go for a compiler or an interpreter?

Is there any runtime library you should consider?

Any particular dialect of your language you need to parse?

What factors will make the editor successful in your specific context?

Are you overlooking something that will bite you later, after you invested months and a significant amount of money in this?

Are the consultants working with you understanding what you really need?

By deciding to work with specialists you can avoid many pitfalls. Consultants like us, who work in a very specific niche, know the ins and outs of the involved technologies. However we do not know all the specifities of your context. Chances are, neither do you.

Is it a good business decision to get a quick “free estimate” and jump into the project?

Uncertainty is not good for business. We have to accept some of it but we should try to reduce as much as possible. To do that we suggest go through roadmapping.

Long story short:

roadmapping is a small engagement to figure out what you need, how you should get there, and examine the risks which could prevent you from getting there.

Is it like taking a look at the map and find the best path ahead before starting to run in the direction which seems more inspiring at the moment