A Software Development Company Is Designing an Evaluation Plan for Its

Short Answer

A software development company is designing an evaluation plan for its software programmers. The company feels that changes are necessary because it lacks the facts it needs to distinguish outstanding software programmers from those that are only average, or worse. Previously, the company paid software programmers a flat salary and based evaluations on supervisors' opinions. Now, however, the company is considering the following measures for its software programmers:
Measurement Strategy Alpha: Software programmers will be evaluated based on the total number of lines of code that they produce.
Measurement Strategy Beta: Software programmers will be evaluated based on their ability to produce computer code that is free of errors.
Measurement Strategy Gamma: Software programmers will be evaluated based on the market success of the products they produce.
Management has decided to combine all three Measurement Strategies in order to give the software programmers incentives that match the company's goals. If the products meet their Gamma goals, software programmers who have met either their Alpha goals or their Beta goals will be rewarded, but if the products fail to meet their Gamma goals, software programmers will not be rewarded unless they have met both their Alpha goals and their Beta goals. Under this system, which of the following CANNOT be true?
A software programmer who has met his or her Alpha goals is not rewarded.
A software programmer who has not met his or her Beta goals is rewarded.
A software programmer who has met neither his or her Alpha goals nor his or her Beta goals is not rewarded.
The company meets its Gamma goals, and a software programmer who meets his or her Alpha goals is not rewarded.
The company does not meet its Gamma goals, and a software programmer who meets his or her Beta goals is not rewarded.