3 ms·
> But once a key portion of the requirements lives outside the team, this is no longer effective because then you're building without that feedback. But how do
by colonwqbang 3y ago
> But once a key portion of the requirements lives outside the team, this is no longer effective because then you're building without that feedback.
But how does Scrum help out here?
- irjustin 3y agoScrum has prescriptive method of who is supposed to gather requirements, the meeting for requirements gathering, estimation for "understanding of requirements", and demo... well for demo'ing the feature back to "the powers that be". Kanban doesn't prescribe any stakeholder methodology. It's not that it's not important, it's just up to the organization. This is definitely a point of contention in Scrum because "oh this is so slow", "there are too many stakeholders", "why do we have to do it this way". I'm at the belief - some way is better than no way. If you don't like Scrum, cool! Go build your own, but if you don't mind it, Scrum is good-enough^tm.