반응형
블로그 이미지
개발자로서 현장에서 일하면서 새로 접하는 기술들이나 알게된 정보 등을 정리하기 위한 블로그입니다. 운 좋게 미국에서 큰 회사들의 프로젝트에서 컬설턴트로 일하고 있어서 새로운 기술들을 접할 기회가 많이 있습니다. 미국의 IT 프로젝트에서 사용되는 툴들에 대해 많은 분들과 정보를 공유하고 싶습니다.
솔웅

최근에 받은 트랙백

글 보관함



A FEW EXAMPLES OF HOW TO CHANGE A NEGATIVE TO POSITIVE





WHEN A USER STORY IS REJECTED,
say, “I had to restart the story because ....” instead of, “I rejected the story because....”


WHEN MORE THAN TWO USER STORIES ARE REJECTED
say, “I accepted most of the stories except ..... because ......”


IF A USER STORY IS NOT CLEAR,
ask, “Can you provide test steps for this story?” instead of “I don’t know how to test this story.” 


WHEN ASKED FOR A PROJECT UPDATE
say, “I tested all the stories and added a few bugs that require immediate attention. I also added a few UI recommendations that can be discussed whenever you have some time.”


WHEN ALL THE STORIES IN AN ITERATION ARE ACCEPTED
say, “Good news! I accepted all the stories and there are no issues. Thanks for all the hard work.”


WHEN A BUG IS ADDED
say, “I added this bug because ......” instead of, “this app/feature is broken.”



FINDING BUGS
is a tester’s gig and not the developer’s. When you identify bugs never show your excitement to the developers.


WHEN THERE IS A CRASH
say, “I am able to reproduce a crash more than once. I added a bug for it along with test steps. Let me know if you are able to reproduce it,” instead of, “The app crashed numerous times and I am not able to test.”


WHEN YOU ARE OVERLOADED AND CANNOT TEST
say, “Currently I am working on another application but I can test yours later today or definitely by tomorrow. Let me know if you want any specific story to be tested on priority,” instead of, “I cannot test today, I am blocked. I will let you know when I can start testing.”


WHEN THE APPLICATION HAS TOO MANY FUNCTIONAL ISSUES
say, “The app is designed very well but I found some functional issues and have prioritized the ones that are most important. Can you take a look at it and let me know your thoughts?”


WHEN THE APPLICATION HAS TOO MANY UI ISSUES
say, “The app does what it is suppose to do and if we can make a few UI changes then it will be ready for a release. Example: ...”



IN SHORT
- ALWAYS MAKE POSITIVE STATEMENTS.
- PROVIDE A REASON.
- PROVIDE A TEST TIMELINE/DEADLINE.
- NEVER SAY “I DON’T KNOW”, “I CANNOT TEST”, OR “APP IS BROKEN”.
- THANK THE DEVELOPERS FOR THEIR HARD WORK.
- QUOTE EXAMPLES OF SIMILAR APPS ON THE
- MARKET WHEN MAKING UI RECOMMENDATIONS

반응형

Comment