4 ms·
And given _unclear_ requirements, you should be able to ask the right questions to make them clear. This is probably a harder barrier to overcome.
by x3n0ph3n3 6y ago
And given _unclear_ requirements, you should be able to ask the right questions to make them clear. This is probably a harder barrier to overcome.
- xupybd 6y agoThis is very much a hard barrier. I find it even harder to produce clear requirements that don't precipitate such questions. I guess it depends on your org but if you're required to do BA work, I find that the most challenging.
- AdieuToLogic 6y agoI humbly proffer that in order to produce clear requirements, it necessitates asking clarifying questions in the context of understanding what engineering effort is being requested. And, perhaps, the most valued skill a senior developer acquires is enough business analysis (which I assume you reference as "BA work") ability such that the stakeholders feel comfortable in what they have conveyed is, in fact, what the development team will set out to deliver.
- xupybd 6y ago>And, perhaps, the most valued skill a senior developer acquires is enough business analysis (which I assume you reference as "BA work") ability such that the stakeholders feel comfortable in what they have conveyed is, in fact, what the development team will set out to deliver. I could not agree with you more. Learning how to clearly communicate to stakeholders is an invaluable skill. One I have yet to master but deeply long to.
- kulig 6y agoLiterally any junior can do this. Unless they are really dense.