1
1 Comment

Feedback from Agile developers: retrospective tool

Hi everyone,

I run an online retrospective tool for Agile developers called Sprint Boards (https://sprintboards.io). I'm interested in receiving feedback from people that work in, or lead, Agile teams about what they think of Sprint Boards.

Many of the features it has today is the direct result of feedback I've received from users, so I'm always keen to get feedback from development teams that follow Agile methodology about what we can do better.

Thank you!

on March 15, 2020
  1. 1

    Hey Ben!

    I love a good retrospective, so it's nice to see there are more tools for this being built. I see a huge opportunity for them in non-development teams as well, so keep an eye on how you can expand into different verticals.

    Let's get into the feedback:

    1. In general, the website feels very cold. You use mostly dark greys throughout, which doesn't have the positive feeling you want a retrospective to evoke! I recommend adding some color and making it more fun, like the Mixpanel website (https://mixpanel.com/).

    2. I like that you have a screenshot, but it's pretty small and hard to discern. I would recommend making your header vertically stacked so the image can be larger. To do this, you'll want to cut down on your caption in the heading as well—it's unlikely someone will (or needs?) to read all that right away!

    By the way, I noticed the laptop is a graphic you licensed from some Mattias fellow. It's nice, but if you ever want more mockups, visit https://facebook.design/devices for more to use!

    1. In general, I think you have a bit too much text and not enough product demonstration. Most screenshots showing how I can use the product will be better than paragraphs describing it. For example, "Share on Slack" could come with a photo of what that looks like, whether it be a link you copy or an integrated dropdown menu, etc.

    2. This is a common thing, but something I've seen helps a lot for paid SaaS products: add an "About Us" page! People love knowing who is behind the tools they use, why they chose to build them, and what the vision of the product is. Even if you're a solo developer, people like that. (See https://lunchbag.ca/lunch-money-mistakes/ for more on that!)

    That's all I've got for now, but I'm really excited to see where this goes. Feel free to reach out if you have more questions! Let me know what went well and didn't go well in this reply! :)

    Best,
    Arix