Identifying your Initial Technical Strategy
When a disciplined agile project or product team starts, one of the process goals which they will likely need to address is Identify Initial Technical Strategy. This is sometimes referred to as initial architecture envisioning or simply initial architecture modeling. This is an important process goal for several reasons. First, the team should think through, at least at a high level, their architecture so as to identify a viable strategy for moving forward into construction. A little bit of up-front thinking can increase your effectiveness as a team by getting you going in a good direction early in the lifecycle. Second, the team should strive to identify the existing organizational assets, such as web services, frameworks, or legacy data sources, that they can potentially leverage while producing the new solution desired by their stakeholders. By doing this you increase the chance of reuse, thereby avoiding adding technical debt into your organizational ecosystem, and more importantly you reduce the time and cost of delivering a new solution as the result of reuse. You will do this by working with your organization’s enterprise architects, if you have any. This is an aspect of DAD’s philosophy of working in an enterprise aware manner.
The process goal diagram for Identify Initial Technical Strategy is shown below. The rounded rectangle indicates the goal, the squared rectangles indicate issues or process factors that you may need to consider, and the lists in the right hand column represent potential strategies or practices that you may choose to adopt to address those issues. The lists with an arrow to the left are ordered, indicating that in general the options at the top of the list are more preferable from an agile point of view than the options towards the bottom. The highlighted options (bolded and italicized) indicate default starting points for teams looking for a good place to start but who don’t want to invest a lot of time in process tailoring right now. Each of these practices/strategies has advantages and disadvantages, and none are perfect in all situations, which is why it is important to understand the options you have available to you.
Let’s consider each process factor:
- Level of detail. How much effort should you put into capturing your architectural strategy, if any at all. A small co-located team may find that a high-level overview captured using whiteboard sketches is sufficient. A team that is geographically distributed across several locations will find that it needs to at least take digital snapshots of the sketches and share them (perhaps via a wiki) or even capture the diagrams using a drawing tool such as Visio or OmniGraffle. They may also find that they need to define the details of the interfaces to major components and services, a strategy often referred to as design by contract. A team in a life-critical regulatory environment may choose to capture more details, even to the point of doing big design up front (BDUF).
- View types. Solution/application architectures are typically explored via several views, and there are architectural modeling frameworks such as TOGAF, Zachman Framework (ZF), and Kruchten’s 4+1 approach that focus on defining potential views. The DAD framework calls out several common views, including Technical, user interface (UI), and Business and suggests that your team address the views that are applicable to the situation you find yourself in. Technical aspects of your architecture may be captured via free form, layered architecture diagrams, network diagrams, or UML deployment diagrams. You may explore the user interface architecture via a UI flow diagram or wireframe model. Business or domain aspects may be explored via conceptual domain models or high-level process models.
- Modeling strategy. How will your team go about formulating their architecture? Will they hold informal modeling sessions in an agile modeling space or formal modeling sessions Joint Application Design (JAD) strategy? Or both? Will they identify a single technical strategy or several options which they will hope to explore and eventually choose from (or combine ideas from)?
- Delivery strategy. Will the team be building a solution from scratch? Will they be evolving an existing solution? Will they be evolving a purchased, commercial off the shelf (COTS) package? Combinations thereof?
We want to share two important observations about this goal. First, this goal, along with Explore Initial Scope, Coordinate Activities, and Move Closer to a Deployable Release seem to take the brunt of your process tailoring efforts when working at scale. It really does seem to be one of those Pareto situations where 20% addresses 80% of the work, more on this in a future blog posting. As you saw in the discussion of the process issues, the process tailoring decisions that you make regarding this goal will vary greatly based on the various scaling factors. Second, as with all process goal diagrams, the one above doesn’t provide an exhaustive list of options although it does provide a pretty good start.
We’re firm believers that a team should tailor their strategy, including their team structure, their work environment, and their process, to reflect the situation that they find themselves in. When it comes to process tailoring, process goal diagrams not only help teams to identify the issues they need to consider they also summarize potential options available to them. Agile teams with a minimal bit of process guidance such as this are in a much better situation to tailor their approach that teams that are trying to figure it out on their own. The DAD process decision framework provides this guidance.