How can I use versions effectively without compromising agile methodology?

[Jonny Davies]

As a team we are currently in the v0-v1 stage, we have a couple of users but not found our sweet spot in the market yet. This means that we are currently validating multiple features and follow a Foursquare style product roadmap (Now, Next, Future), this means our feature priorities are changing constantly. 

It would be good to use versions within Jira and our sprint process but will it restrict our ability to be truly flexible as it seems it would require us to commit to building features ahead of time and suits a time-based product roadmap better.

Is this feeling correct or can versions be incorporated into this kind of workflow effectively?

Thanks!

[Nour Durra Consultant]

@Jonny Davies hi,

you can use versions at anytime through the project, i.e. you can edit the ticket and add a version to it, not necessarily on creation.

Also you can add multiple versions to a ticket, for example a feature is being worked on V1 , V2, and V3 

I hope I got my question correctly :)