Hi, all:
I have several cases of objections, where I'm not very clear on which test questions will rule them out as valid or invalid:
1. Objections with resource allocation as arguments, such as not enough time, or not enough people. Which test question will rule them out as invalid ? And how ?
2. Objections because the proposal will not have the intended effect or does not change anything. Take for example a proposal to add accountability to a role to "Approve request for X". This proposal will not have the intended effect because none of the other roles have any obligation to ask for approval. When tested this objection may become invalid:
- This condition does not move anything backwards (even though it doesn't move anything forward too),
- Because nothing changes, with the proposal dropped we still have the same condition
- It is safe enough to try, although there will definitely be no change.
Because of these arguments, the proposal will become invalid, and the proposal will go through, even though it won't change anything. It seems like it should be a valid objection. Which of the condition above is wrong so that it will make the objection valid ? Is adding a useless accountability considered "moving us backwards" ?
3. Objection because the proposal is proposing something that is impossible, such as adding an accountability to "ensure sales target is met". Reaching sales target is a combination of different things including things that are beyond our control. Is this objection valid because it causes us to move backward, from a condition where we were not asking for the impossible to a condition where we are ?
Thanks,
Dien.