Why focus on features isn't advisable?

Source: Allen Holub

Thinking in terms of features is a disaster. The main problem is that there is no direct connection between the feature and the user's actual work. Features describe your work, not your customer's. 

Many orgs chase one worthless feature after another, never delivering anything of value, and then go belly up. Even the MMF is a flawed notion. You need to release long before an MMF could be implemented to get necessary feedback.

Instead of features, implementing user stories does focus on the user's work, making it possible to do that work in a system that is far from feature complete. That provides real value, and it is often a salable product. Even if you can't sell it, you can get immediate feedback. 

IEEE Systems Engineering Body of Knowledge (SEBOK)

https://sebokwiki.org/wiki/Main_Page

Ringelmann effect and Social Loafing

Ringelmann Effect: As team size increases beyond certain point, individual productivity is seen to diminish. This leads to loss of motivation, and coordination problems.

Social Loafing: The reduction of individual effort exerted when people work in groups compared to when they work alone is called Social Loafing.

Student Syndrome and Parkinson's Law - Procrastinate and Delay the task, Expand work

Culture, habit and Agile Transformation

• 40% of decisions people make everyday are not decisions, but habits. (Dr. Wendy Woods).
• Key to changing habits is not willpower, rather it is changing environment.
• Change requires organizational re-learning -- unlearning and learning everything new