Exactly, it's all about finding the right balance. I'd be wary of just agreeing to avoid documentation, that could cause issues down the line. But I also don't think we need a huge, comprehensive design doc for every user story. Maybe a quick whiteboard sketch would be enough in this case.
Haha, 'Agile, no documentation?' That's a classic misconception. I'd go with option B - explain that documentation is not forbidden, it's just not the primary focus. As long as it's adding value and not slowing the team down, a little documentation can be useful.
I agree, it's a tough one. I think the ScrumMaster should try to find a middle ground. Maybe they could suggest starting with a lightweight design document, just to capture the key aspects, and then focus on the actual implementation.
This is a tricky question. I can see both sides of the argument. On one hand, Agile does emphasize interactions over documentation. But on the other hand, some level of documentation can be helpful, especially for complex systems.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Louann
12 months agoSerina
1 years agoMindy
1 years agoTish
11 months agoAhmed
11 months agoMiles
12 months agoGalen
12 months agoAllene
12 months agoMaia
1 years ago