No up front design

User stories are written but little to no up front design work is done.  A requirements document is usually not created, as well as any kind of architecture documentation, or low-level design documents.  The problem with not doing any kind of serious requirements analysis and design work up front is that the design of that code must be redone with each new feature and each new iteration.  In order to keep the code base sane, it must be constantly refactored.  Otherwise, it will bloat out of control and be much harder to maintain.  But, if the developers were tasked with writing a system based upon extensive analysis of a customer’s requirements, then the overhead of constant refactoring could for the most part be avoided.

Prev          Next          Back to problems with agile practices topic

Copyright 2011 by Robert G. Bryan


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s