1305bdfa_g_the_Software_Engineering_sea__Water
[Rocks] Big user story hides: lack of integration: software is not integrated for weeks lack of unit and integration testing strategy poor confidence on work done in short period (2-3 days) fear of commitments lack of clear understanding of requirements [How to lower the water] Split big user stories in smaller user stories: small here means with lower complexity and therefore with lower size. Then each user story can be split in technical tasks short enough to guarantee confidence for commitments to the team Continuous integration [Water] 
USER STORY
T E A M
I T E R A T I O N
R E L E A S E
U S E R S T O R Y
M E E T I N G
B A C K L O G
W I P
I N T E G R A T I O N C Y C L E
edschepis.net | Surfing the Software Engineering sea
Water