102

Client's logic (stolen from the Facebook page "I love programming")

Comments
  • 2
    That may be better than ever changing requirements! xD
  • 1
    @KuMa you need to write down the requirements, and get the ok from the client, that the requirements are fine.

    Then, if they later want to change them, say them that is not what you discussed, and changing them will require additional work and therefore additional time and budget
  • 3
    @heikomat hehe I wish it were that easy with internal teams.
    We often get project agreement on requirements, set priorities and all that but then often get hit with new requirements. Of course higher management doesn’t care who’s fault it is for the delays.
    We manage by going agile and adding in contingency, my comment was mainly a good old rant ;)
Add Comment