January 14, 2015 at 7:35 am
In my universe, the root of most UAT or production change requests isn't coding mistakes or oversights on the part of the developer, but rather that the functional requirements don't actually match how the end users conceptualize how the end result should look (which itself may even be a moving target that evolves once development begins and long after the first deployment).
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 9, 2015 at 6:44 am
I have found that there is no team or stakehold who hasn't been the cause of a defect. Developers (or any sort) are responsible for unit and, possibly, integration testing. When defects are raised then part of defect management is to analyse the root cause of the defect as well as the resolution. A fix applied to code may not have necessarily originated from code. But it might have done. Each team should take responsibility for resolving the issues for which the resolution is theirs to carry out, however, each team must also accept it when they cause a defect and consider how they can avoid it occurring again.
Work together. Hate the blamers. Not the players.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
February 9, 2015 at 9:39 am
Work together. Hate the blamers. Not the players.
Well put, Gaz, thank you.
December 14, 2021 at 6:44 am
This was removed by the editor as SPAM
Viewing 4 posts - 31 through 33 (of 33 total)
You must be logged in to reply to this topic. Login to reply