We’re going through a bit of a reorganisation of our product, and given Tracker is going away we figured we might as well do it in our backlog’s “forever home”.
Are you able to give us any kind of indicative timeline as to when Storytime will be at least able to be trialled?
2 Likes
I used to get so mad when product managers would make time commitments to customers and prospects! And here I am straining not to. How the wheel turns, etc, etc.
We've had other contracts consuming our engineering capacity. We'll free up at the end of the month, and expect to be implementing the features we've gotten feedback are absolutely critical to be able to get more feedback - specifically (and unsurprisingly) organization-level privacy. We'll put develop those as rapidly as we can, and I'd be surprised if we don't have more public communication/news around our onboarding plans/capabilities by mid-February, in addition to whatever private onboarding/communication we're doing with particular prospects.
The current public alpha, which I'd be happy to onboard you to, is a free-for-all, permissions-wise. That is, anyone can create, read, and modify - and auditing/history isn't available. We're able to get a little bit of feedback like this, but unsurprisingly, not much based on actual use. We got validation value out of it anyway, though!
The interviews it's allowed us to conduct have us focused (at the moment) on the following problems:
- Organization-scoped access (still a free-for-all within a set of backlogs, but organizations have access to only their own)
- History (who modified stories and backlogs when, in detail)
- Crewing (who is (and was) on stories, in what combinations)
Getting 1 and 2 in particular we believe will let interested potential users and design partners put any kind of realistic use into the tool and unlock further feedback about the tool's actual characteristics.
3 Likes
I would love beta access yes please .
And also thank you; that’s definitely enough resolution to help with our decision making.
3 Likes