Mixing
My agile team was enhancing an existing feature and found serious bugs in the original code. Is it our responsibility to fix them?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
We estimated the effort to accomplish our software enhancement on the basis of the original feature working as designed. When testing we found it had significant defects and did not work as designed.
We found the source of the defects but are not allowed to remove it. Instead we have had to absorb fixing all the affected features (well beyond the original scope of our story) and now are being asked to test all the old features.
The scope of the testing is enormous. How do get the other teams to help test their original work again. They all claim its nothing to do with them despite us proving the functionality didnt work in the released version of the code.
professionalism agile
asked 17 mins ago
0ldg33zer
62
New contributor
0ldg33zer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
1
down vote
favorite
We estimated the effort to accomplish our software enhancement on the basis of the original feature working as designed. When testing we found it had significant defects and did not work as designed.
We found the source of the defects but are not allowed to remove it. Instead we have had to absorb fixing all the affected features (well beyond the original scope of our story) and now are being asked to test all the old features.
The scope of the testing is enormous. How do get the other teams to help test their original work again. They all claim its nothing to do with them despite us proving the functionality didnt work in the released version of the code.
professionalism agile
asked 17 mins ago
0ldg33zer
62
New contributor
0ldg33zer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
A supervisor is going to need to step in. Take this to your boss.
– paparazzo
8 mins ago
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
We estimated the effort to accomplish our software enhancement on the basis of the original feature working as designed. When testing we found it had significant defects and did not work as designed.
We found the source of the defects but are not allowed to remove it. Instead we have had to absorb fixing all the affected features (well beyond the original scope of our story) and now are being asked to test all the old features.
The scope of the testing is enormous. How do get the other teams to help test their original work again. They all claim its nothing to do with them despite us proving the functionality didnt work in the released version of the code.
professionalism agile
asked 17 mins ago
0ldg33zer
62
New contributor
0ldg33zer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
We estimated the effort to accomplish our software enhancement on the basis of the original feature working as designed. When testing we found it had significant defects and did not work as designed.
We found the source of the defects but are not allowed to remove it. Instead we have had to absorb fixing all the affected features (well beyond the original scope of our story) and now are being asked to test all the old features.
The scope of the testing is enormous. How do get the other teams to help test their original work again. They all claim its nothing to do with them despite us proving the functionality didnt work in the released version of the code.
professionalism agile
professionalism agile
asked 17 mins ago
0ldg33zer
62
New contributor
0ldg33zer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 17 mins ago
0ldg33zer
62
New contributor
0ldg33zer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 17 mins ago
0ldg33zer
62
New contributor
0ldg33zer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 17 mins ago
0ldg33zer
62
asked 17 mins ago
0ldg33zer
62
62
New contributor
0ldg33zer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
0ldg33zer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
0ldg33zer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
A supervisor is going to need to step in. Take this to your boss.
– paparazzo
8 mins ago
add a comment |Â
1
A supervisor is going to need to step in. Take this to your boss.
– paparazzo
8 mins ago
1
1
A supervisor is going to need to step in. Take this to your boss.
– paparazzo
8 mins ago
A supervisor is going to need to step in. Take this to your boss.
– paparazzo
8 mins ago
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
We found the source of the defects but are not allowed to remove it.
Instead we have had to absorb fixing all the affected features (well
beyond the original scope of our story)
This is a classic case of not enough analysis done to determine the overall impact of the change. If the analysis had been done properly, your team would have realized this was a potential issue, and it would have been in one of the stories.
and now are being asked to test all the old features.
That makes perfect sense. Last time you were not asked to test the old stuff, bugs were introduced. Now you being asked to regression test everything.
How do get the other teams to help test their original work again.
Usually, they get the testing commitment before they start development.
They all claim its nothing to do with them despite us proving the
functionality didnt work in the released version of the code.
It has nothing to do with them, your bugs, your testing.
All you can do here is learn from this. Your team should have done more analysis and now you are paying for it.
answered 5 mins ago
SaggingRufus
7,28852545
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
We found the source of the defects but are not allowed to remove it.
Instead we have had to absorb fixing all the affected features (well
beyond the original scope of our story)
This is a classic case of not enough analysis done to determine the overall impact of the change. If the analysis had been done properly, your team would have realized this was a potential issue, and it would have been in one of the stories.
and now are being asked to test all the old features.
That makes perfect sense. Last time you were not asked to test the old stuff, bugs were introduced. Now you being asked to regression test everything.
How do get the other teams to help test their original work again.
Usually, they get the testing commitment before they start development.
They all claim its nothing to do with them despite us proving the
functionality didnt work in the released version of the code.
It has nothing to do with them, your bugs, your testing.
All you can do here is learn from this. Your team should have done more analysis and now you are paying for it.
answered 5 mins ago
SaggingRufus
7,28852545
add a comment |Â
up vote
0
down vote
We found the source of the defects but are not allowed to remove it.
Instead we have had to absorb fixing all the affected features (well
beyond the original scope of our story)
This is a classic case of not enough analysis done to determine the overall impact of the change. If the analysis had been done properly, your team would have realized this was a potential issue, and it would have been in one of the stories.
and now are being asked to test all the old features.
That makes perfect sense. Last time you were not asked to test the old stuff, bugs were introduced. Now you being asked to regression test everything.
How do get the other teams to help test their original work again.
Usually, they get the testing commitment before they start development.
They all claim its nothing to do with them despite us proving the
functionality didnt work in the released version of the code.
It has nothing to do with them, your bugs, your testing.
All you can do here is learn from this. Your team should have done more analysis and now you are paying for it.
answered 5 mins ago
SaggingRufus
7,28852545
add a comment |Â
up vote
0
down vote
up vote
0
down vote
We found the source of the defects but are not allowed to remove it.
Instead we have had to absorb fixing all the affected features (well
beyond the original scope of our story)
This is a classic case of not enough analysis done to determine the overall impact of the change. If the analysis had been done properly, your team would have realized this was a potential issue, and it would have been in one of the stories.
and now are being asked to test all the old features.
That makes perfect sense. Last time you were not asked to test the old stuff, bugs were introduced. Now you being asked to regression test everything.
How do get the other teams to help test their original work again.
Usually, they get the testing commitment before they start development.
They all claim its nothing to do with them despite us proving the
functionality didnt work in the released version of the code.
It has nothing to do with them, your bugs, your testing.
All you can do here is learn from this. Your team should have done more analysis and now you are paying for it.
answered 5 mins ago
SaggingRufus
7,28852545
We found the source of the defects but are not allowed to remove it.
Instead we have had to absorb fixing all the affected features (well
beyond the original scope of our story)
This is a classic case of not enough analysis done to determine the overall impact of the change. If the analysis had been done properly, your team would have realized this was a potential issue, and it would have been in one of the stories.
and now are being asked to test all the old features.
That makes perfect sense. Last time you were not asked to test the old stuff, bugs were introduced. Now you being asked to regression test everything.
How do get the other teams to help test their original work again.
Usually, they get the testing commitment before they start development.
They all claim its nothing to do with them despite us proving the
functionality didnt work in the released version of the code.
It has nothing to do with them, your bugs, your testing.
All you can do here is learn from this. Your team should have done more analysis and now you are paying for it.
answered 5 mins ago
SaggingRufus
7,28852545
answered 5 mins ago
SaggingRufus
7,28852545
answered 5 mins ago
SaggingRufus
7,28852545
answered 5 mins ago
SaggingRufus
7,28852545
7,28852545
add a comment |Â
add a comment |Â
0ldg33zer is a new contributor. Be nice, and check out our Code of Conduct.
0ldg33zer is a new contributor. Be nice, and check out our Code of Conduct.
0ldg33zer is a new contributor. Be nice, and check out our Code of Conduct.
0ldg33zer is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f121131%2fmy-agile-team-was-enhancing-an-existing-feature-and-found-serious-bugs-in-the-or%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
A supervisor is going to need to step in. Take this to your boss.
– paparazzo
8 mins ago