Comments on: Implementation by feature or vertical development http://www.nerdherding.net/2006/12/05/implementation-by-feature-or-vertical-development/ Working with nerds for fun and profit Wed, 23 Jul 2008 18:56:12 +0000 http://wordpress.org/?v=2.5 By: Lolma http://www.nerdherding.net/2006/12/05/implementation-by-feature-or-vertical-development/#comment-37588 Lolma Wed, 23 May 2007 14:00:56 +0000 http://www.nerdherding.net/2006/12/05/implementation-by-feature-or-vertical-development/#comment-37588 The vertical approach is pretty much dominant in all SE platform... The vertical approach is pretty much dominant in all SE platform…

]]> By: mv http://www.nerdherding.net/2006/12/05/implementation-by-feature-or-vertical-development/#comment-35195 mv Thu, 25 Jan 2007 01:27:07 +0000 http://www.nerdherding.net/2006/12/05/implementation-by-feature-or-vertical-development/#comment-35195 While the vertical slice approach can work in some situations, there can also be subtle pitfalls. A large, nontrivial application really does need an architecture, and some amount of system-wide thought and planning. There are interdependencies and concerns that cut across individual use cases, and developing with too narrow a vertical focus risks integration problems downstream. The appeal of the vertical slice is obvious for those stakeholders concerned with visibility, and the vertical slice certainly can aid with a tighter feedback loop. But these considerations must be balanced against life-cycle and system integrity concerns. While the vertical slice approach can work in some situations, there can also be subtle pitfalls.

A large, nontrivial application really does need an architecture, and some amount of system-wide thought and planning. There are interdependencies and concerns that cut across individual use cases, and developing with too narrow a vertical focus risks integration problems downstream.

The appeal of the vertical slice is obvious for those stakeholders concerned with visibility, and the vertical slice certainly can aid with a tighter feedback loop.

But these considerations must be balanced against life-cycle and system integrity concerns.

]]>