Methodology

This session describes methodology using by LST for the delivery of reliable and scalable software. Using the template project plan described here, you can define a realistic project plan for the delivery of software. Clearly, business drivers vary between projects, so the precise makeup of the project plan will be unique to a specific project; however, you should treat this project plan as a good starting point. All estimates in this plan are provided in person-days.

The tasks that we are going to describe in our project plan are

  • Business Case Analysis
  • Requirements Analysis
  • Technical Blueprint
  • Design and Build Software
  • Design and Build Database Structures
  • Design and Build Operational Infrastructure
  • Testing
  • Transition to Production


Business Case Analysis

Description
This task determines the business case for investing in the development of the software. It identifies the projected returns from this project over a 3-5 year period.

Steps

  • Identify and prioritize all the business needs for this software.
  • Calculate the projected returns
  • Calculate the capital expenditure and operational expenditure for developing and running this software. Consider other options
  • Document and present the business case.

Estimating

  • Effort varies depending on the complexity of the solution, and the clarity of the vision within the organization. In most cases, the effort is limited to approximately 30-person days' duration.

Risks
Minimal. Do not be surprised if the conclusions are that the software is inappropriate; it is far more important to make sure that you are building software for the right reasons.


Prerequisites
A documented business case that have identified a problem and suggested some solutions.

 

Deliverables
  • Feasibility analysis report.
  • A presentation to senior executives.