Hybrid Software Development Methodology : Business Technology Consulting

2260 Words10 Pages
BUSINESS CASE HYBRID SOFTWARE DEVELOPMENT METHODOLOGY BUSINESS TECHNOLOGY CONSULTING JUNE 16, 2016 TABLE OF CONTENTS 1. EXECUTIVE SUMMARY 2 1.1. Issue 2 1.2. Anticipated Outcomes 2 1.3. Recommendation 3 1.4. Justification 3 2. PROBLEM DEFINITION 4 2.1. Problem Statement 4 2.2. Organizational Impact 5 2.3. Technology Migration 5 3. PROJECT OVERVIEW 6 3.1. Project Description 6 4. ALTERNATIVES ANALYSIS 7 5. TEMPLATE 8 1. EXECUTIVE SUMMARY Traditionally, this organization has utilized a waterfall methodology to develop software. The two main reasons for this are that is a well vetted methodology, and it provides a very well defined scope that we can use to manage projects and stay within a defined budget. As the business climate becomes increasingly volatile, the benefits of using this methodology have quickly become detractors. As requirements shift, the waterfall methodology locks clients in to a specific predetermined scope. While this is a good way to control budget, it does not provide the flexibility required to meet client needs. Several new software development methodologies have gained traction in the industry over the past few years. However, none of them provides both the flexibility needed by the end user and the rigidity and control needed to manage both the scope and budget of a project in order to set client expectations appropriately. This proposal recommends a hybrid approach that utilizes three of the more flexible software
Open Document