Dr. Dobb's Journal - September 2008 - (Page 67)

d09ambler_p3as 7/16/08 8:02 AM Page 67 support the business. Many organizations, particularly mid-size ones, choose to combine these two disciplines because the people performing them work closely together and are often one and the same. Each strategy has its strengths and weakness, so choose the approach best suited to your organizational culture. Enterprise models are crucial for identifying potential systems, determining feasibility, and identifying viable implementation strategies because they provide context for these efforts. Unfortunately, many agilists are leery of enterprise modeling due to the many antipatterns exhibited by traditional enterprise modelers (see www.agilemodeling.com/ essays/enterpriseModelingAntiPatterns.htm). Many traditional enterprise modeling efforts run aground when the enterprise modelers focus just on modeling and not on executing the concepts captured in the models. If you choose, enterprise-level modeling can in fact be performed in an agile manner, and at www.agiledata .org/essays/enterpriseArchitecture.html, I describe a collection of techniques for doing exactly that. The main strategies are to keep the documentation light, to work iteratively and collaboratively, and to work actively with the development teams to implement the systems called out in the enterprise models. The length of Iteration –1 will vary by organization and by system. Sometimes a potential project is identified, fast-tracked, and initiated in a matter of weeks. Sometimes a project languishes in your stack of potential projects for months or even years before it receives funding to kick off Iteration 0. The portfolio management activities encapsulated in Iteration –1 are critical to the success of your IT organization, making Iteration –1 an important part of your overall system lifecycle. Thanks to Sally Elatta for the interesting conversation that we had around this topic. DDJ The Enterprise Unified Process expands upon the system development lifecycle (SDLC) to address the full IT lifecycle Scott is Practice Leader Agile Development for IBM Rational. September 2008 l www.ddj.com l Dr. Dobb’s Journal 67 http://www.agilemodeling.com/essays/enterpriseModelingAntiPatterns.htm http://www.agilemodeling.com/essays/enterpriseModelingAntiPatterns.htm http://www.agiledata.org/essays/enterpriseArchitecture.html http://www.agiledata.org/essays/enterpriseArchitecture.html http://www.rallydev.com http://www.rallydev.com http://www.ddj.com

Table of Contents Feed for the Digital Edition of Dr. Dobb's Journal - September 2008

Dr. Dobb's Journal - September 2008 Contents Friday Night Fish Fry Alia Vox Developer Diaries Developer’s Notebook A Conversation With Erik Demaine Application Lifecycle Management Meets Model-Driven Development Building a Robust Development Environment Real Users Really Matter Matching Wildcards: An Algorithm The Android Mobile Phone Platform Managing Application Thread Use Signalling Integer Overflows in Java .NET Development & the IBM WebSphere Portal Server The Agile Edge Effective Concurrency Swaine’s Flames

Dr. Dobb's Journal - September 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.