4 ms·
> there aren’t any explicit requirements but there are requirements, we just don’t know what they are and also they change every sprint so good luck What a sad
by delusional 7y ago
> there aren’t any explicit requirements but there are requirements, we just don’t know what they are and also they change every sprint so good luck
What a sad way to view your profession. The requirements aren't hidden from you, and they don't just randomly change. You can't get them up front because no one has any idea what we are looking for. Solving a small problem usually reveals more of the problem.
I don't think you believe in long requirement documents either, but I sometimes hear arguments very similar to yours.
- ThalesX 7y agoWhat a sad way to hammer someone’s view of his profession based on a comment. > You can’t get them up front because no one has any idea what we are looking for. Is this requirement implementation or R&D? While it’s understandable for R&D to be exist within the ‘no one has any idea what we are looking for’, to fit all software development into this paradigm is to have a pretty lax understanding of how most software operates... > Solving a small problem usually reveals more of the problem This is exactly what I think the parent post was arguing when shying away from estimates.
- lifeisstillgood 7y agoOur understanding of the problem evolves alongside the solutions - and when we look back we tends to say "how could we have been so dumb when we planned this" But we literally did not know
- jayd16 7y agoNew information is constantly becoming available, therefore more requirements are revealed. That's exactly the same as saying the set of requirements constantly changes.
- journalctl 7y agoIt is sad, isn’t it? I wish it didn’t happen so frequently, and I wish my concerns weren’t dismissed so flippantly. How fortunate I am to have met someone who knows more about my situation than I do.