3 ms·
I am finding the same issue in many areas. But I am asking myself if it is just lack of knowledge and knowhow or is it also lack of time, processes and tools f
by gls2ro 8y ago
I am finding the same issue in many areas.
But I am asking myself if it is just lack of knowledge and knowhow or is it also lack of time, processes and tools for writing and maintaining requirements.
My observations are that along with not knowing how to gather and write requirements people at the project level also threat them as second hand objects for the success of project.
Eg: some people in agile talk about requirements being user stories with clarifications and decisions around them. Other people say that in agile requirements are conversation starters.
In a way these might be good points but also it creates the impression that we should not invest quality in requirements. As it will anyhow change.
- tmaly 8y agoWhat I find is that many people do not consider different edge cases or understand what the data really represents. They have some vague notion of what they want, and you only get that very high level limited case. They almost need some training on how to think like a program in some sense to understand just how much detail is needed to provide a good spec.