8 deleted 88 characters in body
source | link

Most interesting Defect(IMHO) is Lack of team communication

As people already hashave given excellent answers about whether is it a good question or not so I will not go in tointo it but share one interesting experience around it.

Most interesting Defect(IMHO) is Lack of team communication.

enter image description here

I remember from a long time back during one waterfall project , I came upon a minor issue(which was hardly touching the real iceberg problem) but which sparked a lengthy discussion in team meeting which exposed an interesting revelation that a functionality was entirely functional and working fine as per the requirement but the actual usage scenarios were entirely different than what developers & testers envisioned.

Finally, it was found the screen business scenarios and user input were entirely different and the current implemented feature was fully functional and tested but entirely useless for the business.

The lesson I learned from that (from quality perspective) ,above any technical maturity in a team is "team communication".

A well communicating team can prevent lot of defects in the first place itself before implementing anything. *A well communicating team can prevent lot of defects in the first place itself before implementing anything.

As people already has given excellent answers about whether is it a good question or not so I will not go in to it but share one interesting experience around it.

Most interesting Defect(IMHO) is Lack of team communication.

enter image description here

I remember from long time back during one waterfall project , I came upon a minor issue(which was hardly touching the real iceberg problem) but which sparked a lengthy discussion in team meeting which exposed an interesting revelation that a functionality was entirely functional and working fine as per the requirement but the actual usage scenarios were entirely different than what developers & testers envisioned.

Finally, it was found the screen business scenarios and user input were entirely different and the current implemented feature was fully functional and tested but entirely useless for the business.

The lesson I learned from that (from quality perspective) ,above any technical maturity in a team is "team communication".

A well communicating team can prevent lot of defects in the first place itself before implementing anything.

Most interesting Defect(IMHO) is Lack of team communication

As people already have given excellent answers about whether is it a good question or not so I will not go into it but share one interesting experience around it.

I remember from a long time back during one waterfall project , I came upon a minor issue(which was hardly touching the real iceberg problem) but which sparked a lengthy discussion in team meeting which exposed an interesting revelation that a functionality was entirely functional and working fine as per the requirement but the actual usage scenarios were entirely different than what developers & testers envisioned.

Finally, it was found the screen business scenarios and user input were entirely different and the current implemented feature was fully functional and tested but entirely useless for the business.

The lesson I learned from that (from quality perspective) ,above any technical maturity in a team is "team communication".

*A well communicating team can prevent lot of defects in the first place itself before implementing anything.

7 added 39 characters in body; deleted 3 characters in body
source | link

As people already has given excellent answers about ,whether is it a good question or not so I will not go in to it but share my one interesting experience around it.

Most interesting Defect(IMHO)- Lack is Lack of team communication.

enter image description here

I remember from long time back during one waterfall project , I came upon a minor issue(which was hardly touching the real iceberg problem) but which sparked a lengthy discussion in team meeting which exposed an interesting revelation that a functionality was entirely functional and working fine as per the requirement but the actual usage scenarios were entirely different than what developers & testers envisioned.

Finally, it was found the screen business scenarios and user input were entirely different and the current implemented feature was fully functional and tested but entirely useless for the business.

The lesson I learned from that (from quality perspective) ,above any technical maturity in a team is "team communication".

A well communicating team can prevent lot of defects in the first place itself before implementing anything.

As people already has given excellent answers about , is it a good question but share my one interesting experience around it.

Most interesting Defect(IMHO)- Lack of team communication.

enter image description here

I remember from long time back during one waterfall project , I came upon a minor issue(which was hardly touching the real iceberg problem) but which sparked a lengthy discussion in team meeting which exposed an interesting revelation that a functionality was entirely functional and working fine as per the requirement but the actual usage scenarios were entirely different than what developers & testers envisioned.

Finally, it was found the screen business scenarios and user input were entirely different and the current implemented feature was fully functional and tested but entirely useless for the business.

The lesson I learned from that (from quality perspective) ,above any technical maturity in a team is "team communication".

A well communicating team can prevent lot of defects in the first place itself before implementing anything.

As people already has given excellent answers about whether is it a good question or not so I will not go in to it but share one interesting experience around it.

Most interesting Defect(IMHO) is Lack of team communication.

enter image description here

I remember from long time back during one waterfall project , I came upon a minor issue(which was hardly touching the real iceberg problem) but which sparked a lengthy discussion in team meeting which exposed an interesting revelation that a functionality was entirely functional and working fine as per the requirement but the actual usage scenarios were entirely different than what developers & testers envisioned.

Finally, it was found the screen business scenarios and user input were entirely different and the current implemented feature was fully functional and tested but entirely useless for the business.

The lesson I learned from that (from quality perspective) ,above any technical maturity in a team is "team communication".

A well communicating team can prevent lot of defects in the first place itself before implementing anything.

6 added 126 characters in body
source | link

As people already has given excellent answers about , is it a good question but share my one interesting experience around it.

Most interesting Defect(IMHO)- Lack of team communication.

enter image description here

I remember from long time back during one waterfall project , I came upon a minor issue(which was hardly touching the real iceberg problem) but which sparked a lengthy discussion in team meeting which exposed an interesting revelation that a functionality was entirely functional and working fine as per the requirement but the actual usage scenarios were entirely different than what developers & testers envisioned.

Finally, it was found the screen business scenarios and user input were entirely different and the current implemented feature was fully functional and tested but entirely useless for the business.

The lesson I learned from that (from quality perspective) ,above any technical maturity in a team is "team communication".

A well communicating team can prevent lot of defects in the first place itself before implementing anything.

Most interesting Defect(IMHO)- Lack of team communication.

enter image description here

I remember from long time back during one waterfall project , I came upon a minor issue(which was hardly touching the real iceberg problem) but which sparked a lengthy discussion in team meeting which exposed an interesting revelation that a functionality was entirely functional and working fine as per the requirement but the actual usage scenarios were entirely different than what developers & testers envisioned.

Finally, it was found the screen business scenarios and user input were entirely different and the current implemented feature was fully functional and tested but entirely useless for the business.

The lesson I learned from that (from quality perspective) ,above any technical maturity in a team is "team communication".

A well communicating team can prevent lot of defects in the first place itself before implementing anything.

As people already has given excellent answers about , is it a good question but share my one interesting experience around it.

Most interesting Defect(IMHO)- Lack of team communication.

enter image description here

I remember from long time back during one waterfall project , I came upon a minor issue(which was hardly touching the real iceberg problem) but which sparked a lengthy discussion in team meeting which exposed an interesting revelation that a functionality was entirely functional and working fine as per the requirement but the actual usage scenarios were entirely different than what developers & testers envisioned.

Finally, it was found the screen business scenarios and user input were entirely different and the current implemented feature was fully functional and tested but entirely useless for the business.

The lesson I learned from that (from quality perspective) ,above any technical maturity in a team is "team communication".

A well communicating team can prevent lot of defects in the first place itself before implementing anything.

5 deleted 2 characters in body
source | link
4 added 6 characters in body; deleted 2 characters in body
source | link
3 added 166 characters in body
source | link
2 added 4 characters in body; added 2 characters in body
source | link
1
source | link