Great work and fun article. You sort of already answered my question about how repeatable this is outside web development. I think having resources like StackOverflow solving most common issues and the field not having a lot of depth (barrier to entry) were critical. Might be a tad more difficult to do, say, secure systems software or hardware this way.
Determination, practice, and one-milestone-at-a-time are my main takeaways here. This benefits any field. Strange enough, it especially benefits high-assurance software because the stuff takes so much time and analysis companies might pull out financially or FOSS people loose focus/hope. INFOSEC guru Paul Karger promoted turning a big project into a series of intermediate, useful deliverables to maintain morale and provide short-term revenue from licensing/sales of intermediates. Seems same for learning, too.
JIRA is a great tool but it's hard to set up and for small teams it can be overkill. We built Zube to provide an Agile workflow right out of the box so you can get up an running right away.
Zube is also deeply integrated with GitHub and everything is synced both ways in real time. So even if some of your developers want to stay in GitHub, everything is still up to date.
To me, this two-way sync'ing is the killer feature of Zube (from my short usage so far), along with its Trello-like card metaphor for issues as a value-added layer.
Just having the real-time filtering on issues is a huge win. Change a filter, see your updated list. Excellent.
Determination, practice, and one-milestone-at-a-time are my main takeaways here. This benefits any field. Strange enough, it especially benefits high-assurance software because the stuff takes so much time and analysis companies might pull out financially or FOSS people loose focus/hope. INFOSEC guru Paul Karger promoted turning a big project into a series of intermediate, useful deliverables to maintain morale and provide short-term revenue from licensing/sales of intermediates. Seems same for learning, too.