But as Web teams grow and their sites become more complex, signs of organizational and procedural stress begin to appear. There are several reasons for this. Rapidly-evolving tools and technologies keep businesses running as fast as they can to stay in place. The lower barriers to entry, compared to established markets, foster a highly innovative and competetive business environment. The Web largely lacks clear success metrics, resulting in business Web sites that continually evolve in hopes of landing on the right formula.
Web development requires a high level of integration and coordination among parallel tasks.
There is little experience to develop a foundation of mature and efficient work practices. Putting Methods into the Madness Because of the factors above, Web teams frequently spend more time being reactive than proactive. Projects under development are also subject to feature creep , where major changes in product definition add significant costs and delays. For example, let's say you were building a house. You wouldn't put up drywall without first installing the plumbing and wiring.