Re: Parallel QA

Sagacious indeed! 

However, in my experience there is only a slim possibility that the audience (traditional QA manager) will recognise the depth of that comment. The traditional QA manager doesn't care too much about developing s/w. If (s)he were, then a deep dive into how/why programmers+analysts make so many mistakes/bugs would have long ago led them to the realisation that testing should be done, early and often.
In this case, I would even argue that it is actually not very difficult, in fact it is quite easy, to do testing in parallel;...people are a bit blind..., I think this is a case where we are trying to hack a tree, with a chain-saw.

cheers
SrinivasChillara Srinivas is a Scrum Coach, Scrum Trainer, XP, TDD, Test Driven Development, Scrum Training, consultant and trainer, Scrum implementation, Project Management Proficiency, PMP, Pune, India

  
|  
|   
|   
|   |    |

   |

  |
|  
|   |  
Chillara Srinivas is a Scrum Coach, Scrum Trainer, XP, TDD, Test Driven Dev...
 Chillara Srinivas Srinidhi is a Scrum Coach, Scrum Trainer for Scrum, XP, TDD (Test Driven Development), consult...  |   |

  |

  |

 


      From: "Alexander Kriegisch [email protected] [SCRUMDEVELOPMENT]" <[email protected]>
 To: [email protected] 
 Sent: Thursday, 31 August 2017 9:15 AM
 Subject: Re: [SCRUMDEVELOPMENT] Parallel QA
   
Miyamoto Musashi, a famous Japanese rōnin samurai and writer who lived 1584-1645, wrote in his famous "Book of the Five Rings" in a chapter about about learning how to fight with two swords at the same time (his signature technique):
    "It will seem difficult at first, but everything is difficult at first."   I have coached many teams during the last 12 or so years, and almost all them thought they could not do dev and QA within one sprint. But sooner or later they all proved themselves wrong. And by the way, small stories are not the problem but part of the solution.-- Alexander Kriegischhttps://scrum-master.de


Am 31.08.2017 um 03:19 schrieb Michael Wollin [email protected] [SCRUMDEVELOPMENT] <[email protected]>:


Got this from a colleague. Curious what you all think I might tell him:

Hi Michael,

I had a question come up from a potential client and was wondering what your response to this would be, since you've led sessions about what to say to a reluctant developer: What do you say to a QA manager that thinks QA work should be done outside (after) the sprint? This individual maintains that there is not enough time in a two-week sprint to do both the development and QA work, unless the stories are made so small there is little to test, and that they should be done sequentially (they obviously have a very waterfall-like process of dev completing their work and then handing a story off in its entirety to QA.) What would you tell this person to bring them on-board with the idea of the whole team completing their work within the time box of the sprint?

Thanks!



------------------------------------
Posted by: Michael Wollin <[email protected]>
------------------------------------

To Post a message, send it to:   [email protected]
To Unsubscribe, send a blank message to: [email protected]
------------------------------------

Yahoo Groups Links