I'm afraid it's not that easy with game dev, Serg and I don't really know how that would benefit you actually. Things you intend on fixing get worked on, if you add more plans for other fixes then they might (usually do) have a knock on to the previous stuff being fixed which could put those things at risk of change, which might alter the fix to those - you can't just go "FIXED! THAT'S IN!" and lock it off - everything touches everything, it's incredible.
Hi
@sallymorganmoore
perhaps it would be helpfull for many people here, if there would be more transparancy about the issues and backlog items that your colleagues from the Dev teams currently work on.
My guess: You guys work on
- Incidents and problems that you identify internally
- Incidents and problems are are marked as "Confirmed" in the Issue Tracker
- Incidents and problems that are listed in the Issue Tracker but did not reach the "official" number of contributors to be marked as "Confirmed"
- Some kind of feature updates and gameplay improvements.
I worked in a Big Blue company some years ago and for us it was quite normal, to open our CMVC system to clients, if things boiled up far too hot (i.e. if clients were upset due to a lack of product quality). Did this solve the problem? No! But our clients felt far better as they had direct information about our current work to help them out of their trouble.
Our goal was not the satisfied client! We wanted to have
VERY satisfied clients. Of course we were not always successfull but at least here in Germany we did a fairly good job.
The way you kept us informed last Thursday after Update #4 was really great.
Starting with this I'd put even more emphasis on transparancy:
- Perhaps share a Kanban board where we can see which problem/incident is in which state. This would also open the opportunity for us, to refer to those items in progress, if we face a bug and file a report in the Issue Tracker.
- Let there be a mark in each report of the Issue Tracker from which we can see, if someone from Dev had a look into and made a 1st qualification (e.g. qualified-known (worked on with ID # on the Kanban board), qualified-unknown (opened new item on Kanban board), qualified-requires-recreation and/or more (log)data (***), nonsense, invalid, by design)
***: Perhaps it makes sense to ask us for additional data/logs/recreation steps. You may give us some rewards (e.g. Arx, credits, ship paintings etc.) as a reward for this.
I think, that this could lead to a point where you have satisfied clients again. Then you should make them very satisfied clients by implementing at least some of the really good gameplay features that were written down in the forums throughout the last weeks and months.
Edit: fixed some typos. If you find more, you are allowed to keep them