I have seen many Agile projects, particularly those focused on brand-new product lines, struggle with getting their infrastructure up and running.  Much of the reason is the time and effort that is needed to get infrastructure established far exceeds the time it takes to start development using an Agile method, effectively the first iteration.  Typically the approach used to establish infrastructure is ad hoc and often not always aligned with the needs of the project.  Therefore, a task must be identified to establish infrastructure.  The question then is, how to best approach the establishment of infrastructure for a project using Agile methods?  We do not want to build excessive infrastructure that may constrain us in the future yet we want to establish enough to keep us stable and productive.

Originally published at the Agile Journal. Read the rest of the article here.

Trackback(0)

TrackBack URI for this entry

Comments (0)

Subscribe to this comment's feed

Write comment