Deliverable $2-$ "Baseline Project Plan"

Overview

The Baseline Project Plan $($BPP$)$ describes the proposed project in detail. It directly addresses the question $-$ Is this project worth pursuing? As such, it forms the foundation, or baseline, for all remaining stages of the software development lifecycle.

Given your preliminary data collection, you should be as specific as possible in each of the required sections. $($You must have started your requirements$-$gathering activities to write this document, but you are not expected to have completed them.$)$

Your deliverable must be well organized, with clear headings delineating the sections in the same order as presented below. Remember this is describing the current system, except where noted.

Details

Deliverable $2$ should include the BPP $($outlined below$)$ with the following additional sections:

Baseline Project Plan $($BPP$)$

$1.)$ Introduction

A$.)$ Organizational overview: A description of the organizational environment for which this system is being developed. This is an expanded version of the organizational description from your project proposal, which includes the additional details needed to understand your project site.

B$.)$ Problem statement: A detailed documentation of the problem or opportunity which is motivating this project. This must describe the aspect of the current organizational situation that will be improved by your project. $($Spend time to make this as clear as you possibly can.$)$

C$.)$ Scope statement: A brief description of the people, business functions or processes, and locations that will be impacted by this undertaking. Describe how each of these is currently impacted by the problem$/$opportunity$,$ In describing these boundaries you may need to address related issues which are outside the scope of the project but are helpful for establishing the context.

D$.)$ Recommendation: A brief section presenting your group's recommendation to go ahead with this project or not, as justified by your feasibility assessments. If your team has changed the definition of the project in any way as a result of your initial analysis, please describe these changes here.

$2.)$ System Description

A$.)$ "Obvious" solution: A brief description of the "obvious" solution to the problem$/$opportunity outlined above $($i$.$e$.,$ the system that you believe, at this point, will probably be recommended after the analysis phase$).$ This description should only be as detailed as your current thinking about it$.$

B$.)$ Alternative$($s$)$: A brief description of at least one alternative solution that will also be investigated.

$3.)$ Feasibility analysis $($evaluating the current situation without regard to any particular solution$)$

A$.)$ Technical feasibility: Describe the technical issues that will be relevant to this project $($e$.$g$.,$ required system interfaces, platforms, protocols, user skill set$)$ and whether your team has the resources available to address these.

B$.)$ Economic feasibility: Identify all relevant costs and benefits of the existing system, indicating which are tangible $/$ intangible and one$-$time $/$ recurring. Quantify to the best of your current ability, Appropriately label sources and approximations.

C$.)$ Organizational feasibility: Describe organizational aspects of the project, including the following:

Stakeholders: Identify all relevant stakeholders and their relationship to the existing system.

Legal: What are the contractual constraints of the current system? If there are none, say so$.$

Schedule: Include a preliminary schedule for the entire project and your assessment of the probability that the schedule will be met. Graphical representations of time and dependency concerns are helpful, but not required at this stage.

$4.)$ Management issues

A$.)$ Team members: List all team members and their roles on the project. $($This is a relevant condensation of your bios from the project proposal.$)$

B$.)$ Risks and constraints: From your feasibility analysis, highlight important risks and constraints for the project. These may be schedule, budget, policy, or any others that your group can identify in your preliminary assessment of the organization. These should include anything that you think may become an obstacle to the successful completion of this project.

Data Collection: A brief description of your ongoing requirements$-$gathering activities. Specifically, this should identify the fact$-$finding approaches, data collection techniques, and information sources you that you used to generate this report.

Statement of Work $($SOW$)$: This is a one$-$page summary for your customer to ensure shared understanding $($give them a copy$).$ It states precisely what they should expect from you. This should be written in terms that the customer will understand. It should include a summary of your problem$/$scope statements and a simplified description of the "obvious" solution you have identified $($although you must also say that other alternatives will be investigated and the final solution may be different$).$ Also, outline what you expect will b