One project with a version for each customer or a project for each customer.

Johannes Harestad

Let's say we have a project named "Bakery App". For each customer we created a version, let's say we have "Alice's Bakery" and "Tom's Bakery". They share the same core functionality, but got some custom stuff and each their design. We created a bunch of user stories and then marked each story with the right versions. But now we see that this might be a bad approach because you can only change the status from "in progress" to "resolved" for all versions, and not just one.

If we create a project for "Alice's Bakery" and "Tom's Bakery" there will be a lot of stories that we have to copy back and forth, a lot of duplicates.

What is the best approach to this in your opinion? Thank you for any answer, much appreciated!

Peter Van de Voorde

Hi Johannes,

I would simply create a project per Bakery (so one for Alice's Bakery, one for Tom's Bakery) and use these projects to contain all stories that are custom for this customer (design,...).

I would then create a global project which contains all you common stories (the core functionality).

You now have a clear project per customer and your core functionality doesn't have to be copied everywhere.

What do you think about that idea?

Best regards,

Peter