I’ve used sprintly in the past and overall quite liked it, but there were bugs and feature requests in their tracker, untouched for years, with comments like “yes, soon”. Besides the odd few reporting features, it just felt to me that development stopped and stagnated. This is a large reason why I didn’t go back to using it.
Overall, I liked sprintly and am sad to see it shut down, but I’m surprised it survived this long given how it started to feel a bit abandoned. (Sure you could argue if it’s not broken don’t fix it and sprintly mostly worked great, despite some issues being untouched so long, so I don’t think that’s what happened here. I do think it was perhaps a marketing problem not a feature/product problem, but it just gave a very abandoned impression)
I found out about it on recommendation by one of their advisers. I would never have heard about it otherwise so definitely think that it could have been better marketed. Although, with that said, it’s teue that sprintly was opinionated and that most teams have their own opinions that may not match up. For example, I wanted a way of having a pool of tasks that people could choose from rather than strict ordering (eg maybe a priority system where any equal-priority task at the top can be taken, not just the top task) but sprintly didn’t have any way of marking priorities or groups and they didn’t want to add the feature because it went against their strict top task next workflow. I’m not at all saying they should have supported that feature, of course, just how even small differences in opinion on workflow can make the tool less of a fit.
JIRA is the opposite in that it lets you customise it to fit whatever workflow you like, but in the process becomes a complex beast that I dislike using. I at least enjoyed using sprintly even if it didn’t always fit perfectly.
Overall, I liked sprintly and am sad to see it shut down, but I’m surprised it survived this long given how it started to feel a bit abandoned. (Sure you could argue if it’s not broken don’t fix it and sprintly mostly worked great, despite some issues being untouched so long, so I don’t think that’s what happened here. I do think it was perhaps a marketing problem not a feature/product problem, but it just gave a very abandoned impression)
I found out about it on recommendation by one of their advisers. I would never have heard about it otherwise so definitely think that it could have been better marketed. Although, with that said, it’s teue that sprintly was opinionated and that most teams have their own opinions that may not match up. For example, I wanted a way of having a pool of tasks that people could choose from rather than strict ordering (eg maybe a priority system where any equal-priority task at the top can be taken, not just the top task) but sprintly didn’t have any way of marking priorities or groups and they didn’t want to add the feature because it went against their strict top task next workflow. I’m not at all saying they should have supported that feature, of course, just how even small differences in opinion on workflow can make the tool less of a fit.
JIRA is the opposite in that it lets you customise it to fit whatever workflow you like, but in the process becomes a complex beast that I dislike using. I at least enjoyed using sprintly even if it didn’t always fit perfectly.
In any case, good luck on future ventures!