LBi Development Methodology

LBi Development Methodology

LBi utilizes an agile software development methodology that focuses on the user and incorporates components from various standard methodologies. We have the flexibility to tailor the specific methodology to the project at hand.

The LBi methodology combines elements from Extreme Programming (XP), Agile Unified Process (AUP) and Rational Unified Process (RUP). We leverage the customer and stakeholder focus of XP, artifacts of AUP and the attention to detail of RUP. In addition we emphasize an in-depth understanding of the business of the client/user throughout the project, from inception to transition.

Our User-Centric Mindset

At the core of LBi�s approach to all projects (whether support, documentation, training or development) is our user-centric mindset. This mindset has two major rules - (1) Know the Business and (2) Keep the user involved throughout the project.

Our Methodology

Step 1 - Inception
	Our first step is to identify application scope and learn the business environment. We must also understand the motivation for developing the application, its expected growth, compliance issues, and any Service Level Agreements.
		a.	Learn the business � Sit with users, review existing documentation and learn the required tasks. This is the most important step as with this understanding of the client�s challenges the new application will be designed to improve their process.
b.			Identify initial scope of project.
c.			Set the project goals and objectives.

Step 2 - Elaboration
	Next we select appropriate architecture and prototype the interface. We also separate the project into small �bite-sized� functional units. Depending on the application/project this may be modules, sub modules, reports, and/or screens. Each unit must perform a function that can be delivered to the user.
		a.	Select appropriate architecture and application framework
b.			Prototype the interface
c.			Separate the project into small �bite-sized� function units. This decision may impact the architecture, so a. and b. may be repeated.

Step 3 - Construction
	We now perform the following steps for each functional unit (small �bite-sized� delivery), where each delivery has its own mini-lifecycle. Once again, feedback from the user is encouraged at all times. These are iterative steps that are repeated over the lifecycle of the project.
		a.	Requirements Gathering � user meetings, use cases
b.			Preliminary Design � workflow, sequence diagrams
c.			Prototyping
d.			Specification and Design � class diagrams and modeling
e.			Development and Testing
f.			Delivery to staging area
g.			QA

Step 4 - Transition
	This includes any final QA and delivery.
		a.	QA process � regression testing
b.			Delivery to production environment

Benefits of the LBi Approach

Download the LBi Development Methodology Handout

LBi's Development Methodology