Planning Palooza

> end up in a labyrinth of documents, encumbered by stiff structures

Few lines down, a structure is proposed: single Jira board, Epics for decision, and duplicated task tickets (both in Jira and in Github).. Sounds like a pretty stiff structure.

I don't see the point of the article - author says there are too many alternatives (which I fully agree with), but their solution is two specific ones... How is this going to prevent fragmentation if team A goes with github while team B decides to use Atlassian instead?