4 ms·
> they also tend to know the full problem domain a little better than most of the business people they deal with This is too often overlooked. It is developme
by pasbesoin 17y ago
> they also tend to know the full problem domain a little better than most of the business people they deal with
This is too often overlooked.
It is development's job to "re-engineer" this domain in some fashion. Don't neglect the expertise they bring to the table and/or acquire in doing so.
And... if you are dealing with a corresponding "business type" at the client/customer, realize that this applies on the other side, too. When working with/through such contacts, you may not being gaining a full picture of what their end users really need.
Better model: Put the users and developers in closer contact with each other. Use your expertise to mediate this especially from a financial and legal perspective. Scheduling fits somewhere in between, and should have the active participation of both parties -- business and technical on your side, and ideally both business and technical on their side as well.
It can be like a light bulb going off, when e.g.your tech lead finally gets to communicate directly with theirs. An hour -- sometimes 15 minutes -- of direct communication can obviate weeks of "memos" and such. Especially if they are freed to communicate in a forthright manner on an ongoing basis.
Your job is to define the boundaries of communication and to adequately defend property rights and profitability. Don't insert yourself too heavily into nor try to micromanage the rest. Assuming you have good staff.
This is based upon my ad hoc observation of situations that have worked and situations that haven't. I'm not formally an "expert" in this.