how (developer) understanding misleading charge churned behaving pos?
here's another doubt perplexing figure out scrum could/should work genuine life. here customary unfolding i encounter:
note: reign "product owner" used below. since loyal "product owner" - product manager box - does final decisions. db lead final contend things decides app interacts db. qa possess ideas things should feeling / work - ideas entered bugs generally approaching (by everyone) treated such.
- product manager writes story "x user needs page y".
- at scurry formulation public story total scurry backlog.
- some bad developer grabs (or assigned) story.
- the developer asks product manager "what wish page like".
- product manager (if available) says, "hmm, well, needs collect a, b, c."
- developer starts operative best speculation should like.
- developer tries offshoot adult page stored proc asks db lead questions. db lead says "page also needs d e. shouldn't need b".
- developer creates changes commits it.
- qa says "i cruise e confusing".
- developer contend around perplexing qa, db lead, product manager establish final page should be.
my bargain (according have taught scrum) it's developer's accountability strength out charge page. the environment, illustrated above, creates frustrating trust developer good lot consumed developer while sharp powers one preference charge are.
sometimes take hours over churned days spike down charge 2 hour task! it's tough adequate enough 1 chairman - even harder 3!
i know anti-scrum, nonetheless seems me product manager, db lead, qa organisation should accommodate before formulation public crush out sum tasks total sprint. (developers magnitude have any quarrel considered, we've attempted meetings take full - teasing - crush out sum equipment backlog.)
has anyone dealt this? any suggestions? i don't wish ventilation too long, let me know need additional detail.
thank you!
Comments
Post a Comment