On 3 Jan 2014, at 01:22, Charles Bradley - Professional Scrum Trainer and Coach <chuck-lists2@...
> Are you saying that knowing what Scrum is or is not is something that should be understood with a "very clear line" but that the "sharp division" of said line is not really important? That seems contradictory to me... Or maybe you’re just saying that the "spirit" of the canon is way more important than the fine detailed "letter" of the canon... but I'm speculating here.
Not Ron - but for what it’s worth this is my interpretation:
1) Knowing when you’re *not* doing Scrum (because you are dropping a fundamental practice) is important. But the main point is to start somewhere and improve even if you know that you’re not doing something useful.
2) Separating out Scrum-mandated practices and other necessary practices for the team in context is unimportant, and potentially harmful.
I suspect that you were intending (1) in the job spec, but it can easily be read as (2).
… and in the context of a job advert for a senior SM role it’s noise and should be removed. It’s the equivalent of asking something on the level of "must know the difference between object-oriented and functional development" on a senior-development job description. That knowledge is implicit in the other points on the job spec.