4 ms·
You can get away with some push back and influence business process changes, but even with that, and even with solid change management, the OP seems roughly rig
by davidivadavid 5y ago
You can get away with some push back and influence business process changes, but even with that, and even with solid change management, the OP seems roughly right IME.
- andy_ppp 5y agoI am not convinced that the description of business processes into code is doomed to always be completely intractable. It is possible to understand the business well enough to solve its problems in a clear way it’s just often extremely difficult. I have to say though, for an industry that claims to love science we have a dearth of tools that can help us learn how to do the more qualitative sides of coding better.
- wheelinsupial 5y ago> we have a dearth of tools that can help us learn how to do the more qualitative sides of coding better Does dearth mean something different than “lack” here? I come from a manufacturing and mechanical design background. We learned a design process including tools to deal with the qualitative aspect of requirements elicitation in each project. A book I found helpful while transitioning to a business analyst position involved with software projects is [1]. There is also the social sciences and maybe the humanities that use qualitative research methods. An example is enthographic research. I think there is plenty out there to use as a starting point. [1]https://www.microsoftpressstore.com/store/software-requirements-9780735679665 https://www.microsoftpressstore.com/store/software-requireme...