4 ms·

Thanks for making this. Maintaining parity between Google Sheets Gantt charts and JIRA tickets is a real problem I have and one that is underserved by existing

Thanks for making this. Maintaining parity between Google Sheets Gantt charts and JIRA tickets is a real problem I have and one that is underserved by existing tools. On the other hand this is a cursed development methodology. There's an infinite mine of No True Scotsmans about Agile, but really, when you find yourself putting your Agile stories in a Gantt chart and projecting sprints several months out, you are unambiguously rejecting substantive principle and content of Agile as a methodology. At this point it would be much more productive to admit that you're doing waterfall and put some effort into doing it well, instead of farting around with backlog grooming, sprint planning, etc. where the outcomes are all committed before the meeting in a master schedule.

flarg 5y ago
This is the reality of most mid and large sized organisations, fake Agile with Scrum, which is really better for waterfall anyway
electric_muse 5y ago
Hey, that means a lot. Thanks. It does seem there are a lot of methodologies being used with the product. And agilefall does seem to be making a comeback. But a fair number just use it as a faster way to plan the sprints and run standup. (Vs in Jira) The thing about “spreadsheets” is that they seem to be flexible enough to fit all the idiosyncrasies of how different teams work, regardless of methodology. I hope the product can save you time, frustration, and copy/paste drama.