Comments on: “I know it’s late but please help me out guys!” – #EWT17 http://www.acatalin.ro/2010/05/08/i-know-it%e2%80%99s-late-but-please-help-me-out-guys-ewt17/ The Alchemy of Software Testing Fri, 19 Nov 2010 05:50:51 +0000 hourly 1 http://wordpress.org/?v=3.2 By: Catalin Anastasoaie http://www.acatalin.ro/2010/05/08/i-know-it%e2%80%99s-late-but-please-help-me-out-guys-ewt17/comment-page-1/#comment-7 Catalin Anastasoaie Sun, 13 Jun 2010 17:40:45 +0000 http://acatalin.ro/2010/05/08/i-know-it%e2%80%99s-late-but-please-help-me-out-guys-ewt17/#comment-7 Thanks for your comment Thomas, it was a really good assignment with lots of learnings (congrats). Hope to see you soon, too. Thanks for your comment Thomas, it was a really good assignment with lots of learnings (congrats).

Hope to see you soon, too.

]]> By: Thomas Ponnet http://www.acatalin.ro/2010/05/08/i-know-it%e2%80%99s-late-but-please-help-me-out-guys-ewt17/comment-page-1/#comment-6 Thomas Ponnet Sun, 13 Jun 2010 17:07:24 +0000 http://acatalin.ro/2010/05/08/i-know-it%e2%80%99s-late-but-please-help-me-out-guys-ewt17/#comment-6 Hi, I reallly like the thinking that the manager must have looked at the functionality before assigning it to the team. But has he? Looking at the wording he might just heard the name mentioned by someone saying ""That's a cool compressor, you should use it." So the idea is good, if that is then followed up with a quick question about if he actually tested the functionality you'd know that a very large part of the test effort might then be out of scope. Very good summary, I like the thinking behind it and that you wrote it down. Hope to see you again soon, Thomas Hi,
I reallly like the thinking that the manager must have looked at the functionality before assigning it to the team. But has he? Looking at the wording he might just heard the name mentioned by someone saying “”That’s a cool compressor, you should use it.”

So the idea is good, if that is then followed up with a quick question about if he actually tested the functionality you’d know that a very large part of the test effort might then be out of scope.

Very good summary, I like the thinking behind it and that you wrote it down.

Hope to see you again soon,

Thomas

]]> By: Catalin Anastasoaie http://www.acatalin.ro/2010/05/08/i-know-it%e2%80%99s-late-but-please-help-me-out-guys-ewt17/comment-page-1/#comment-5 Catalin Anastasoaie Sat, 12 Jun 2010 19:10:44 +0000 http://acatalin.ro/2010/05/08/i-know-it%e2%80%99s-late-but-please-help-me-out-guys-ewt17/#comment-5 Hi Markus, Thanks for your comment and for following up on my learning's. Really appreciated! Yes, indeed you are perfectly right about the missions and that we must always check back with our stakeholders to see if we got it right or if something has changed in the mean time. I really hope that we will have the chance to work together again. Thanks one more time for taking the time to comment on this. Hi Markus,

Thanks for your comment and for following up on my learning’s. Really appreciated!

Yes, indeed you are perfectly right about the missions and that we must always check back with our stakeholders to see if we got it right or if something has changed in the mean time.

I really hope that we will have the chance to work together again. Thanks one more time for taking the time to comment on this.

]]> By: Markus Gärtner http://www.acatalin.ro/2010/05/08/i-know-it%e2%80%99s-late-but-please-help-me-out-guys-ewt17/comment-page-1/#comment-4 Markus Gärtner Sat, 12 Jun 2010 18:04:29 +0000 http://acatalin.ro/2010/05/08/i-know-it%e2%80%99s-late-but-please-help-me-out-guys-ewt17/#comment-4 I see a flaw in the first point of your learnings. The problem is that we rarely get clear mission statements. So, we have to formulate them on our own and check back with our stakeholders whether they were correct or not. This has to be done regularly, and over time as projects unfold, these initial missions may also change due to problems being differently perceived, or initial problems being dealt with. Maybe something to continue thinking about :) Happy Testing. I see a flaw in the first point of your learnings. The problem is that we rarely get clear mission statements. So, we have to formulate them on our own and check back with our stakeholders whether they were correct or not. This has to be done regularly, and over time as projects unfold, these initial missions may also change due to problems being differently perceived, or initial problems being dealt with.

Maybe something to continue thinking about :)

Happy Testing.

]]>