Scrum team failing consistently?

We love firefighters! Don’t we? They are Heroes! But not in software development. In any Scrum software development, very few teams actually manage to find the time to refine and properly compose their stories (user requirements). Because of this, they’re constantly taking time to try and analyse the software requirements during the projects sprints.

This inevitably results in stories being rushed, ill defined, slapdash and careless. This delays the development of the software and  testing, which  should be a major activities, is compressed and squashed into just the last one or two days of the sprint.

And the result?

Firfighting !!!!

The result, is of course, defect in the code. The team then starts firefighting, to try and fix the problems that were born of their ill planning. However, because they’re so caught up in their self-imposed firefighting, they don’t have time to analyse and create competent stories for the next sprint, so they dive right back into the vicious cycle of firefighting.