Agile In A Service-Oriented World

Goal

The overarching goal is a usable standalone service environment to foster new and innovative applications. To achieve this goal:

  1. a comprehensive and consistent service infrastructure should be produced
  2. application development must be performed on the service infrastructure as if it were supplied by an external provider
  3. any feature must be supported by the service environment before application development begins

Flow

Process

Feature Backlog

The feature backlog is owned and prioritized by the Product Manager (chartreuse). The Product Manager, with help from Core,  identifies impacted service(s). If any services are impacted, the feature is routed to the service backlog (purple).

When service support is operational, the feature is routed to one of the Application Delivery Teams (mauve, peach).

Service Backlog

The Service Backlog (purple) is an independent backlog. Core Services activities include:

  • mapping features to service contracts
  • specifying orchestration and other agreements to complete feature
  • working with external specification bodies (KS, OSIDs, etc).
  • providing light-weight mock services to unblock application development
  • evolving technical standards for data storage, authorization, system management
  • implementing services using these standards
  • performance testing
Once a functional (but not necessarily final) operating service is deployed into the development service environment, the Product Management may route the implementation of the feature to one of the ATDs.
Application Backlog

The Application Backlog (other random colors) is processed and one of the following may occur:  

  1. feature can be implemented as is
  2. feature is blocking on service support

It may be either the service support was not clearly understood earlier or new requirements were injected as part of the user story breakdown. In either case:

  1. Product Manager is consulted for prioritization feedback.
  2. Core Services is brought in to understand the work necessary.
  3. If the solution is to impact the service environment, the feature (or the relevant portion) is routed back to the service backlog and the remaining parts of the feature are implemented. 

 

  • No labels