Futures

As well as a massive amount of features that we have already built within AgileData.io, we also have a massive amount of features we still want to build.

In our agile way of working we only commit to building the next feature when we have got to done done on the current feature. We always pick the highest priority feature next, and of course our priorities often change based on feedback from our users. So you won’t get a guaranteed road map of what’s next from us.

But we think visibility of features we want to build might be useful to you. And at some stage we hope to build a feature where you can tell us what your highest priority feature is (but that’s not a high priority feature for us yet ;-)

So here we brain dump our “futures” so you can see them and we can find them.

We see little value in fleshing these futures out in detail until they are close to the top of the priority list, so to start off we stand on the shoulders of giants (in this case Ian McAllister and Amazon) and reuse their press release format to describe these futures.

There’s an example outline for the press release (thank you for so generously sharing Ian) :

  • Heading - Name the feature in a way the reader (i.e. your target customers) will understand.

  • Sub-Heading - Describe who the market for the feature is and what benefit they get. One sentence only underneath the title.

  • Summary - Give a summary of the feature and the benefit. Assume the reader will not read anything else so make this paragraph good.

  • Challenge - Describe the problem the feature solves.

  • Solution - Describe how the feature elegantly solves the problem.

  • Quote from ADI - A quote from ADI our virtual spokesperson.

  • How to Get Started - Describe how easy it is to get started.

  • Customer Quote - Provide a quote from a hypothetical customer that describes how they experienced the benefit.

  • Closing and Call to Action - Wrap it up and give pointers where the reader should go next.