We have estimation; it's just not featured in the video. Whoops! The estimates are the bubbles next to the item cards. We use S, M, L, XL for all item types.
We use Python/Django and MySQL. Pretty boring to be honest, which I'm digging after spending nearly five years working on crazy ass big infrastructure.
That being said, I'm eyeing Redis, Node.js, Memcached (of course), and some AWS services for future upgrades, services, and features.
As for #3 in your list, we offer a feature where coder A can say, "Hey, coder B, you're item X is blocking my item Y!" When coder B finishes item X, coder A is alerted via email that coder B has unblocked them.
The original comment is correct though in that the video just talks about features, it doesn't tell a story or focus on how it would be used to build a product.
Even though I'm familiar with pivotal/ticketing systems, I still wanted to be sold on what it does not just on how it does it.
Chat hooks! I want hipchat (or campfire, w/e) to say "Joe commented on…" etc. Specially new items, comments and status changes.
Then I could configure github to notify sprintly and sprintly to notify the chat, instead of getting all the pushes in the chat, which is too noisy IMO.
All great feedback. The primary reason to limit signups right now is twofold: 1. There are only two of us and the holidays are upon us, so we wanted to keep support load as low as possible for now, 2. Our on-boarding process/funnel, as you've pointed out, is really lacking. Two nerds with full-time jobs don't make great copy editors unfortunately.
We're working on all of these things. I'll check out scrumy.com as well. Thanks for the tip.
Haha! We feel you. Your response was pretty much exactly what my developer friends said to me. "I'd like to use the product management app that doesn't exist." ... That's why we worked so hard on the GitHub integration. It's basically a CLI interface to sprint.ly for developers. We also have pretty deep email integration for managers.
