###### tags: `RFC` # Collaboration between Solutions and Product ## The issues We are trying to improve our workflow for the following three "categories" of "things" that tend to happen - because these have been a bit of a thorn recently to all parties involved: - Urgent fix which usually must be made followed by a hotfix to the platform! - **GOAL:** Get the fix in the hands of customers ASAP. Always top priority. - Bug report (We find a bug internally or via a customer which we want filed and prioritized) - **GOAL:** We want to fix the product in the best way possible without compromising release schedules. - Bug fix (Either a workaround qualified for production or recommendation that might require evaluation still) - **GOAL:** Same as above. ## The solution proposal - Urgent fix: - Since it's top priority we form a cross-discipline squad to deal with the fix, QA and the release to follow. - Since the priority is higher than any feature release we can pull people out of existing squads for this without having to question without any doubt about the priority. - Bug report - Make sure the bug is confirmed and reproduced. - File it on shortcut in the PO inbox. - Fill out the bug template with as much information as possible. - Bug fixes - The plan here is still work in progress. Hopefully this also means that we in time level out the two development teams and we can fill in between each when needed so we make sure everything is running smoothly at all times.