How big should a story be?

###Intro Stories are the fundamental unit of work for an agile team. For a project to be successful, it is important that stories are well written, sliced properly and correctly sized. Story slicing and sizing are often difficult to get right, especially for those new to agile.

So how big should a story be?
Simply, as small as it can be, no bigger nor smaller.

###What does that mean?
It means that a story should cover exactly one piece of functionality that the customer would find useful. This piece of functionality should be independently implementable, testable and deployable. It should be something that, when deployed, will give the customer some value.

###Counterarguments

###Single Responsibility Principle

###Continuous feedback

###Pipelining the team