Doing more… but not too much

Problem analysis, conversations, agreements, calls, code design, daily stand-ups, testing and implementation, pair programming, refactoring, meetings, code review, comments and defects and changes of the code, documentation and… much, much more. The bigger project, the more things have to be done, the more things are required to be done. But how much is too much? How to do enough instead of doing too much?