IS 390 Group Project Milestone Two
Due: Oct. 29th
In this milestone, you are to deliver a document called BRD (Business Requirement Document). Although difference formats exist for BRD, the one you are required to present is popularly used in current IS practice. It serves as a “contract” between you and your client on the scope, schedule & expected outcome of your project. A BRD contains seven sections.
I. Version Control
Since a BRD might go through several rounds of revision (iterative process, remember?), this first section is simply used to keep track of the project history.
A. Revision history:
Simply a table with the following columns: Version# (0.1, 0.2…), Date of ...view middle of the document...
This is the person assigned to get it done (Could be more than one).
* An ‘A’ designation indicates that the person is accountable. This might be the person who manages the responsible person in some organizations. This person will be “called into account” if the task is not completed. In our project, this should be the project manager (you can take turn to serve as project manager during each stage). In other words, if I find a task not ideally completed, the person with an “A” in the cell will be the one I talk to.
* Others might be 'C' consulted about aspects of the task but are not directly accountable or responsible for that matter involved. For example, both your client and people outside of your group (including me) could be consulted regarding your project.
* An 'I' person (informed) is affected by the activity/decision and therefore need to be kept informed, but do not participate in the effort. (They are notified after the final decisions are made.)
Below is a sample RACI table:
RACI Table Example |
Activity | Deployment
Ownership | Project
Identification | Project
Selection | Project
Execution | Project
Results | Team
Support | Sustain
Executive Team | A | R | A | | | | |
Champion | R | A | R | | | R | |
P&L Managers | | I | | | A | R | R |
Process Owner | | C | | R | R | R | A |
Black Belt | | C | | R | R | A | |
Green Belt | | | | R | A | | |
II. Executive Summary
You need to write a concise summary using one to two pages. It must cover:
* Overview (1 – 2 sentences: this project is for a system that…)
* Background: domain knowledge! Should cover the industry and the company
* Objectives of the project --- what are the final deliverables?
* Requirements --- resources required for the project in terms of hardware, software, personnel, finance, etc. Don’t worry too much about it for your project.
* Proposed strategy --- in-house development? Package solution? Outsourcing? Don’t worry about it for this milestone
This is where you insert your PROJECT CHARTER AND SYSTEM SERVICE REQUEST (SSR) (please refer to day 5, page 10). Your SSR is basically a one-page summary that contains the information listed above.
What tasks are included in your scope? What are not included (for example, you know that implementation of the system is NOT)? What are the constraints (for example, time is certainly an issue here)? Be VERY specific. For example, do not say: “our project is on a very tight schedule”. Instead, say: “the final report of the project is due on ..., and the design is expected to be finalized by …”
IV. Risk Analysis
Risk is anything that could impact the completion of a project on time, in budget and according to specification. Try to estimate any potential risk involved in the project. There are five areas of risks: technological (the availability of a...