Scrum telling you how to align with the organization is not rewarding the engineer in any way. Orthogonal concerns.
How does Scrum reward the engineer, in a way that it does it better, and more profoundly, than other methodologies?
How does Scrum reward the engineer, in a way that it does it better, and more profoundly, than other methodologies?
As the author noted, Scrum solves this problem by making number of story points completed the primary tool for a team to measure its productivity. If the cool-sounding project isn't important enough to take other items out of the sprint, there's no way to offer a post-hoc justification for doing it anyway. It has no story points, so work on it is considered non-productive.