Lot of Added and Removed code

Regular development, new code being crafter is accompanied by a removal of old code (continuous refactoring).

Monitor technical debt to keep it on a controllable level. Ensure code review practice is in place.

Lot of Added code

Looks like an active feature development which generates lots of new code. As none gets removed - technical debt seems to grow over time which will likely require refactoring/cleanup on later stages.

Monitor the technical debt to understand when a stabilization/refactoring iteration should take place. Promote the Continuous Refactoring practice throughout the team.

Lot of Removed code

Something got refactored to take less code with no loss (hopefully) in functions. Example - a new library or framework was introduced on a project which allowed to delete a piece of in-house legacy code. Less code means less effort to maintain it.

Make sure technical debt got reduced.

Few-to-none Added or Removed code

No development activities in a team due to some reason. Maybe it's about some design or research or planning (i.e. when it's not about huge activity in code repository), maybe someone is lazy and needs a magic motivation to start working

Investigate the reasons of no coding activity.