It's not all happiness and rainbows when working on new code. We want to be working on the right task for our customer but sometimes building the RIGHT thing takes a lot more discussion than just coding up a storm. How do you think of assessing risk in your projects? What are activities that make development less risky?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (2)
I'd love to hear what folks at bigger orgs do. Most our risk involves "what if we waste a lot of time on something people don't like", but it can be informal because we're a small team.
I do like that a lot. Oftentimes the anti pattern that has come up as a hold over in some ways of "waterfall" or a potential human flaw is thinking one knows what their customer wants. This type of rule and seeking feedback often can prevent a lot of waste. When I'm working on a bigger feature what's typically running through my head is if this does fail how big of a deal is it and is it worth worrying about.