Bifalgorithm post · Infotech governance policy ethics and law · Appendix C: Common scenarios

Client Requirements

Client Requirements (Infotech governance policy ethics and law · Appendix C: Common scenarios) — "Software development companies with an idea for a software pr…

Ideas in this flowchart

  • Client-financed software development creates obligations concerning reuse, requirements, and responsibility.
  • A developer may seek a client to finance a product that will later be sold to the client’s competitors.
  • The developer may offer a discount to secure the deal, although receiving full price would be preferable.
  • The client understands that their funding may also benefit competing companies.
  • The client may rely on a non-disclosure agreement, but that trust can prove misplaced.
  • During development, the client may request additional or specific software requirements.
  • The developer is likely to reject requests that do not fit the developer’s product strategy.
  • A developer has explicitly rejected a client request on the grounds that it conflicted with development strategy.
  • A client who pays for software is entitled to receive what they are paying for.
  • If the developer chooses a different direction, that work should be done at the developer’s own expense and on their own time.
Feed/

Client Requirements

Channel

Infotech governance policy ethics and law

1 page

"Software development companies with an idea for a software product will often look for a client who is willing to finance the production of the software which will then be sold to as many of the client’s competitors as possible. If the client can be persuaded to pay full price, then so much the better. To secure the deal, the developer may offer a discount. The client probably realises that they are funding a project that will not only benefit them, but also their competitors. Perhaps they trust a non-disclosure agreement with the developer to safeguard their interests. This trust may prove to be misplaced. As development proceeds, there are sure to be times when the client says to the developer, thinking about it, we now want the software to do this or that (specific requirements). Unless this fits with the developer’s own product strategy, the client is likely to be told, no that cannot be done. It would be a rash or arrogant developer who then says, it cannot be done because it does not fit with our development strategy, though I have personally heard these words spoken in a client-developer meeting. If the client is paying for it, they are entitled to get what they are paying for. If the developer wants to go in a different direction, they should do it at their own expense, on their time."

Flowchart preview
Series cover
👍
0
0 comments0 shares

Sign in to view and post comments.