More Notes On Process

The following graphic depicts a general approach for solution delivery. The diagram depicts the activities which occur during the major phases of development. This methodology is a hybrid of SDLC (PMBOK) activities and the Scrum development collaboration framework. We find that this combination of tasks works best for BI/DW programs. The activities which occur in each major phase (shown in the top half of the model) are described below. Please note that the tools, techniques, and processes which we would recommend are not described. There are a few reasons for this, although the most important is that clients often have a number of these in place, and we integrate our development style into their pre-existing environment.

Strategic Planning

The theme of this iteration is to select the project and define scope. Activities:

  • Active Stakeholder participation
  • Identify potential projects
  • Prioritize potential projects
  • Consider Project Feasibility
  • Identify Risks

Iteration 0

The theme of this iteration is to initiate the project. Activities:

  • Select Project and initiate program
  • Identify and engage Stakeholders
  • Obtain funding and support
  • Start building the team
  • Establish Communication Plan
  • Initial requirements envisioning
  • Initial architecture envisioning
  • Setup environment

Development Iterations (1..N)

The theme of this iteration (which repeats until the solution is completely developed) is to deliver a working system which meets the changing needs of stakeholders. Activities:

  • Active stakeholder participation
  • Collaborative Development (this is where the majority of Scrum activities takes place)
  • Refine data models
  • Initiate Test Driven Design practice
  • Confirmatory Testing
  • Update Documentation for each incremental release of working product
  • Promote incremental release into evolving product-base (integrate with previous releases)

Release of Iteration "N"

The theme of this iteration is the "Major Release." Depending on the size of the project's scope, the idea is that there will be "N" iterations (1..N) required to deliver the first major release of the project. Once delivered, if the project has a second Major Release planned, the development team will move forward in the Development Iteration (N+1) while the product released at the end of Iteration N will move forward into Production (managed by Operations). Activities:

  • Active stakeholder participation
  • Final system testing
  • Final acceptance testing
  • Finalize documentation
  • Pilot test the release (typically in a staging, pre-production environment)
  • Train end users
  • Train production (operations) staff
  • Deploy system into production

Production Support

  • The theme of this iteration is the support and use of the solution delivered in Iteration N. Activities:
  • Operate the system
  • Support the system
  • Identify defects and enhancements (which get prioritized in the Product Backlog)

Solution Retirement

  • The theme of this iteration is to remove the system completely from production. Activities:
  • Remove the final version of the system
  • Convert existing data to new platform
  • Migrate users
  • Update process models