Are Systems Engineers Complete Losers When it Comes to Communication?
by Chris Rupp
The systems development industry is frequently shaken by negative reports, such as the mishaps and delays that plagued the Toll Collect system in Germany or cars that break down due to software defects. Many people wonder what it is that ails modern systems development. Why is it so hard to build systems that realize user requirements when our technology allows us to do almost anything? Are systems engineers losers when it comes to communicating about the requirements? Can the problem be solved by an agile process and direct communication between system users and developers? If so, which fields of knowledge must be added to an agile process in order to ensure that knowledge transfer works?
| Attachment | Size |
|---|---|
| AreSystemsEngineersCompleteLosersWhenItComesToCommunciations.pdf | 336.79 KB |
The person on agile team who
The person on agile team who keeps their head free of solutions; anyone reason why you would not call this person a Business Analyst?
Talking is better than writing; do you mean that writing does not first involve talking?
How about talk, then write, then review with people who were talked with?
I just get tired of the implication that good requirements writing is too hard to do right, so why bother... it is not too hard if you know how to do it.