The project I am currently on was well underway when I arrived on the scene. Consequently, a lot of the framework and structure had already been decided, which is fine. It makes my job simpler... in theory.
The section that my team is working on involves allowing the user to enter notes on the "case" they are currently working on. The requirements ask that they be able to attach additional data to each of these notes regarding the source of the information in the note, the time spent in investigating, etc. Notes are entered thorughout the application but only in our particular section is this additional data needed. A forward-thinking data modeler actually allowed for the storage of these notes in the database so we are good to go there.
However, when we began presenting our design to a project lead, we hit a minor snag.
Lead: You need to use the "Notes Control" that we have already developed.
Us: Um... we can't because they want to save this additional data that is not part of the control.
Lead: No, you have to use the standard control.
Us: What about this additional data?
Lead: Tell them they cannot have it.
Us: But it is in the spec that has already been approved. The database even already has the fields to save this additional data. Can't we just copy the existing control and create a second control modified to include this additional data.
Lead: No. Tell them they have to change the spec to fit the control that has already been developed.