Kailyn Ashley
Olujimi Babatunde
Paulette Baxter
Kristen Young
INSS 640
Assignment 3
Executive Summary
Sam, Lisa, Lee, the “A” Team
Green_Delivery_rus.com
Baltimore, Maryland
Dear Sam, Lisa and Lee:
Thank you for giving us a chance to assist you with the planning and designing of
Green_Delivery_rus.com’s green technology system. Please view our attached analysis below.
Objective:
To develop a sustainable, user-friendly system that provides online service to people who are
either too busy or not capable of performing tasks on their own. The new system will be
equipped to implement three distinctly different services:
1. Will take food orders for delivery (not necessarily deliver them)
2. Make emergency doctor’s appointments
3. Provide and make appoints for rides
Plan & Design
The system will be 100% environmentally friendly so the company can maintain its business
operations in line with a core value which is to meet the needs of the present without
compromising the ability of future generations to do the same. The system we implement will
not use any complex features so quick and easy use can be implemented by the client.
The system will have the ability to keep track of the number of its and resulting sales on the
website. Information about customers will be collected for data mining purposes.
We will ensure that end users have input in the design process. All project business goals and
objectives will be accomplished within the defined budget and time frame.
1
We recommend following course of action:
A well-designed risk management plan to reduce problems encountered during a project by up
to 90%.
The domain name of Green_delivery_rus.com is not yet taken but we would recommend an
easier and simpler domain name like Greendelivery.com, which is available and easier to
communicate to prospective customers.
We also recommend a system development methodology using Prototyping with RAD tools
because of the nature of the business.
For optimal business profit in the near future, the team should consider becoming contracted
outsourcing agent for delivering foods for restaurants. It will be more profitable than only food
order process.
We recommend that the team stay motivated by being an active participant throughout the project and
plan milestones to ensure that we are making progress.
Finally, we recommend effective communication throughout team and the use of Fault Tree
Analysis as a sure way to mitigate risk in the project.
We are very eager to work with you in designing your system and are looking forward to the
formation of a long and health relationship.
Sincerely,
The H Team, Systems Consultants
2
1. Define the scope of the project
The scope of a project “defines what work is or is not included in a project” (524).
Green_Delivery_rus.com will be an online delivery system that facilitates locating relevant
businesses via web access for a fee. The fee is yet to be determined. Initially, the business will
NOT deliver or provide services. Green_Delivery_rus.com is an environmentally friendly and
green conscious company that will serve the local market in Baltimore, with plans to start
delivery in Virginia and Delaware in 2012. The purpose of this e-business will be to provide
services to people who are either too busy or not capable of performing these tasks on their
own.
The new system will be equipped to implement three distinctly different services. It will take
food orders for delivery (not necessarily deliver them); make emergency doctor’s
appointments; and provide and make appointments for rides to locations such as the airport, a
friend’s home, and regular appointments.
To be more specific
Service 1: Take Food Orders. Green_Delivery_rus.com will provide links to menus of several
local restaurants on their website. A customer will select items from the menu. A referral
service fee will be charged by Green_delivery_rus.com, and will NOT provide any actual
deliveries at this time.
Service 2: Make Emergency Appointments. A person may need to make emergency
appointments at any time. Green_Delivery will assist in facilitating this service by providing
links to hospitals on their web site. An appointment reference fee will be charged for the use of
the service.
Service 3: Providing Rides. A person may want to go to different locations (airport, visit friends
etc.) Green_Delivery_rus.com will provide the links to taxis and other types of transportation
services that can provide rides. A reference fee will be charged for this service.
Since Green_Delivery_rus.com is very proud of the word “green” in their name and firmly
believes in “sustainability” – defined as “…meeting the needs of the present without
compromising the ability of future generations to meet their own needs…” (www.epa.gov),
“Green” system hardware and software will be used. The system will not use any complex
features to ensure that it can be implemented quickly and easily used by the clientele.
The system will have the ability to keep track of the number of hits and resulting sales on the
web site (Green_Delivery_rus.com), and would like to collect information on their customers
for data mining purposes ONLY. In order to complete this project both successfully and on
3
time, “the scope of [the project will] not expand beyond what [it] was originally intended” to be
(524).
2. Base line Plan
A. Introduction
Project Overview
Group H, Inc. has been given the task of planning and designing a new environmental green online system for Green_deliver_rus.com. Green_deliver_rus.com wants
to take their
organization to the next level and to stay competitive. The team’s goal is to create an easy to
use system that intentionally lacks any complex features and is quick to implement.
Green_deliver_rus.com requires that the new system entail:
-Take food orders for delivery (not necessarily deliver them).
-Green_deliver_rus.com will charge a referral service fee but will not provide any actual
deliveries at this time
-Make emergency doctor’s appointments.
-Provide and make appointments for Rides to locations such as the airport, friend’s home,
regular appointment etc.
Green_Delivery_rus.com plans to cater to mostly local market in Baltimore and surrounding
area but also have plans to start delivery in Virginia and the Delaware area starting 2012. They
are “environment” and “Green” conscious and want to build a system with “green” technology.
Start date of project July 1, 2010 and end date of project is October 30, 2010.
Four individuals will be assigned to work on the project and it will take four months for the
team to complete the project.
Green_Delivery_rus.com project have a budget of $500,000, and would be willing to consider
putting in more cash, if needed and if we justify the reasoning.
Project Goals and Objectives:
-Ensure that end users have input into the design process.
-Accomplish project business goals and objectives within defined budget and time parameters.
-Minimize impact to standard business operations within the affected unit.
4
-Craft a favorable and secure agreement between Green_Delivery_rus.com and us.
Project Budget
Green Run Delivery _ Rus.com Project Budget
Project Expenses:
-Employees’ Compensation……………………………………………………………………$100,000
-Equipment/Supplies……………………………………………………………………………..$300,000
-Overhead or Indirect Costs……………………………………………………………………$100,000
Total Project Expense………………………………………………………………………………………………..$500,000
Risk Assessment
The risk assessments associated with the project will continuously be monitored and updated
throughout the life of the project, with monthly assessments included in the status report and
we are open to making amendments if needed.
Project Assumptions
-We ensure that all project team members will be available as needed to complete project tasks
and objectives.
- Failure to identify changes to draft deliverables within the time specified in the project
timeline will result in project delays.
- Project team members will adhere to the communications plan.
- All project participants will abide by the guidelines identified within this plan.
-
The project plan may change as new information and issues are revealed.
Project Timeline
July 1st – Awarded the Green Run Delivery _ Rus.com project.
July 6th - Start Date of Project. Date on which work first begins on project.
August 31st -Project manager and team meets with Green Run Delivery _ Rus.com managers to
provide an update on the status of the project, and discuss any concerns.
5
August 1st, September 1st and October 1st, Semi-Final InspectionFirst is inspection of the entire project. Upon completion of the project, the team will perform
an inspection. If all construction contemplated by the contract has been completed to the
team’s satisfaction, that inspection will constitute the final inspection. If corrections are
needed, then this will be a semi-final inspection with final inspection to be done after
corrections are completed. If all work is completed and received a passing grade from the team
and Green Run Delivery _ Rus.com, we will move to the next stage. The team will conduct
multiple semi-final inspections on this project.
Sep. 26, Substantial Work Complete Date - Date that corrections noted on the last semi-final
inspection have been completed.
Oct. 30th, Final Inspection and Physical Work Complete Date - This is the date that all work has
been completed on the project.
3. List of critical success factors
“The strategic analysis, or success factors, approach argues that an organization’s information
requirements are determined by a small number of critical success factors (CSFs) of
managers.”(pg. 528)
The team defined with Green-deliver-rus.com top managers the CSFs that will make the project
a success. We wanted to ensure with management that we would make the CSFs measureable
in providing a return by the end of the first year of implementation of the new system. The
team plans to use these CSFs to measure the project and the team’s success.
-The team must have a plan for the project.
-Clear document project milestones and deliverables.
-A valid and realistic time-scale.
- Accurate cost estimates to be produced.
-Keep the project team
Green_Delivery_rus.com.
focused
and
aware
of
project
progress,
as
well
as
-It is important that the team stay motivated by being an active participant throughout the
project and plan milestones to ensure that we are making progress.
-It is imperative that the project be in line with Green_Delivery_rus.com organizational strategy.
6
4. Resource requirement, allocation and analysis (cost/benefit)
(note: these include material and personnel costs like hardware, software, web designer,
programmer, network engineer etc.)
To begin, resource requirement, allocation and analysis (cost/benefit) has to do with
strategically determining what resources are required, the allocation of said resources,
specifically “the determination of how costs, time, and personnel are assigned to different
phases of a systems development project,” and last but not least the cost/benefit analysis of
those required resources and allocated times (G 11).
This was developed using the Total Cost of Ownership of Technology Assets (196). The Total
Cost of Ownership (TCO) “model can be used to analyze these direct and indirect costs to help
firms determine the actual cost of specific technology implementations” (196).
Starting a new business, no matter what size and how innovative the idea can seem easily both
expensive and daunting. The projected resource requirement, allocation and analysis
(cost/benefit) has been projected below. The equipment is guaranteed to be environmentally
friendly and the perfect fit for a small beginning, and soon to be growing, small business.
Hardware acquisition
Computers
1,018.00 each – 7 for purchase: $7,126.00
Optiplex960SFF



Long system lifecycles, advanced manageability tools for IT
Comprehensive Enterprise Class security protects critical data
Green designs and smart energy choices help reduce environmental impact
Printer
1,300.00 each – 2 for purchase: $2,600.00
HP Color LaserJet CP3525X
Scanner
499.99
HP Scanjet N6310 Document Flatbed Scanner
Fax Machine
129.00
HP 3180
Software acquisition
MS Office Professional
499.00
7
McAfee
Other
30.00 each – 7 for purchase: $210.00
300.00 per month – $3,600
Phone, Internet through AT&T
Miscellaneous supplies
2,950.00
Paper, ink, power strips etc.
Supply Total: $17,613.00
Employees (all salaries are listed as per year; general corporate ranges for people with 5 yrs
exp).
Web Designer
60,000.00
Programmer
80,000.00
Network Engineer
75,000.00
Human Resources
63,000.00
Sam (each will need computers, hardware, software etc. – incl. above)
Lisa
Lee
Employee Total:$ 275,000.00
Grand Total: $ 292,613.00
Listed above are the costs (Hardware, software, telecommunications, personnel etc.) This
projected model also includes the following:
Tangible Benefits (Cost Savings)
Increased productivity
Lower operational costs
Lower computer expenses
Intangible Benefits
Improved resource control
8
Increased organizational flexibility
More timely information
More information
Increased organizational learning
Enhanced employee goodwill
Increased job satisfaction
Improved decision making
Improved operations
Higher client satisfaction
Better corporate image
5. Work Breakdown Structure (WBS)
Level 1
– Green_Delivery_rus.com Software System
Level 2
1.1 Project Management
Planning
Cost & Schedule Management
Scope management
Task Management
Project communications
Human Resource Management
Risk Management
Quality Management
9
1.2 Systems engineering
-Technical Planning
-Business Requirements Definitions
-System Requirements Definition
1.3 Software
-Software Design
-Software Requirement Specification
-Software unit detailed design
-Software Build
-Software Unit coding
-Software Unit Debugging
-Unit Testing
-Unit Test planning
-Unit test records
1.4 Hardware
-Hardware requirements planning
-Hardware System Definition
-Hardware component selection
-Hardware unit/component testing
1.5 System Test
-Module & Subsystem Testing
-System integration testing
10
-Defect classification, tracking, & metrics
1.6 Installation
-Installation Planning
-User support documentation
-User communications & training
-Installation testing and verification
-Installation performance monitoring
6.Critical Path method, project schedule and the Gantt chart generated
through Microsoft PROJECT
Start
Finish
Plan
7/6/10
7/15/10
Determine project scope
7/6/10
7/6/10
Management
Define preliminary resources
7/6/10
7/10/10
Project Manager
Secure core resources
7/10/10
7/15/10
Project Manager
Scope complete
7/15/10
7/15/10
7/15/10
8/6/10
7/15/10
7/22/10
Analyst
Draft preliminary software/hardware specifications 7/22/10
7/25/10
Analyst
Develop preliminary budget
7/25/10
7/30/10
Project Manager
Review software/hardware specifications
7/30/10
7/30/10
Project Manager
Incorporate feedback on software/hardware
7/30/10
7/31/10
Analyst
Develop delivery timeline
7/31/10
8/2/10
Project Manager
Obtain approvals to proceed
8/3/10
8/3/10
Management, PM
Secure required resources
8/3/10
8/6/10
Project Manager
Analysis complete
8/6/10
8/6/10
8/7/10
8/24/10
8/7/10
8/9/10
Analysis
Conduct needs analysis
Design
Resource Names
Review preliminary software/hardware
Specifications
11
Analyst
Develop software/hardware requirement
specifications
8/9/10
8/13/10
Analyst
Develop software unit detailed design
8/14/10
8/20/10
Analyst
Review software requirement specifications
8/20/10
8/21/10
Management
8/22/10
8/22/10
Analyst
Obtain approval to proceed
8/23/10
8/24/10
Management, PM
Design Complete
8/24/10
8/24/10
8/24/10
9/18/10
8/24/10
8/24/10
Analyst
9/4/10
Engineer, Developer
9/4/10
9/11/10
Software Engineer
9/11/10
9/16/10
Software Engineer
9/17/10
Management, PM
9/17/10
9/17/10
Analyst
Obtain approval to proceed
9/18/10
9/18/10
Management, PM
Development Complete
9/18/10
9/18/10
9/18/10
10/1/10
Review software/hardware specifications
9/18/10
9/20/10
Analyst
Module and Subsystem Testing
9/20/10
9/23/10
Software Engineer
System integration Testing
9/23/10
9/26/10
Software Engineer
Defect classification, tracking & metrics
9/26/10
9/27/10
Software Engineer
Review testing results
9/27/10
9/29/10
PM, Analyst
Get feedback on results
9/29/10
10/1/10
Management
Testing Complete
10/1/10
10/1/10
Project Complete
10/1/10
10/1/10
Incorporate feedback into software/hardware
requirement specifications
Develop
Review software/hardware specifications
Install hardware to meet hardware specifications 8/25/10
Complete software unit coding to meet software
Specifications
Complete software unit debugging to meet
software specifications
Review the actual software/hardware
development and see if specifications were met 9/16/10
Get feedback on actual software/hardware
Development
Test & Monitor
12
7. Risk associated with the project and how to control / mitigate these risks.
Risk is the uncertainty in a future event which may or may not occur. The goal of any company
is to reduce risk in order to avoid the corresponding potential for loss. Sam, Lisa and Lee are
eager to capitalize and be a part of the growing e-commerce business. Green_Delivery_rus.com
brings a lot of promise since the demand for delivery service is there. People are busy and
willing to spend money on services that will help them out. Focus on sustainability and
environmentally conscious efforts are also extremely important to people these days. By
providing a green system (both hardware and software) Green_Deliver_rus.com is likely to
appeal to many people. Combining this aspect into their business is very unique.
The attractive part of e-commerce business is that they require little capital investment.
Innovative ideas are essential and Sam, Lisa and Lee have already nailed that. Their largest
capital expense is going to be their software and hardware system. They will probably be
paying a premium on this since they are looking for a “green” system. Identifying and
managing the risk of a software project is critical for its success or failure. There are many risk
management tools that can help identify, reduce and prevent risk completely. The risks that are
associated with a software project include schedule / time-related / delivery related planning
risks, budget / financial risks, operational /procedural risks, technical / functional / performance
risks and other risks that are just unavoidable.
It is proven that a well-designed risk management plan can reduce problems encountered
during a project by up to 90%. The plan should be constructed during early stages of project
planning since everything builds off on planning. It is common knowledge that having a risk
management plan is a value added function of the project.
There are seven steps that can be followed to ensure a successful risk management plan. The
first step is actually writing the plan and organizing the team. In the case of
Green_Delivery_rus.com, the team formation is going to be easy since there are only three
people in the company as of now. Each of them should make a list of each ten risk items even if
items seem obvious. The next step is to combine everyone’s lists / get rid of duplicate entries
and form a master list. Step three is to assess each characteristic for every risk on the list.
Terms such as low, medium or high can be used. The fourth step would be to divide the team
(this may not be necessary since again, the team is only three people) into subgroups and then
to assign different parts of the master list to each group. The task of each group is to identify
red flags for each risk – normally three per risk. Step five is for the subgroups to identify
/document actions that could prevent these threats and especially ways to capitalize on the
opportunities. The next step is to make an action plan for the majority of the risks. The risks
that should be included are those that score above a particular cut-off point in order to keep
the process manageable. A plan that is incredibly time consuming will be ineffective. Finally, an
owner should be assigned to each risk on the master list. This person will keep watch for the
red flags identified and then act in the appropriate manner.
13
One very useful tool that is used in preventing or mitigating risk is the Fault Tree Analysis. This
takes undesirable events and represents them in a structure resembling a tree. Simple logic and
graphical design are used to do this. This allows managers to know what the root or lower level
causes of the fault are. Appropriate actions to avoid these events can then be taken.
Another huge way to mitigate risk is to ensure effective communication throughout the team.
This is very important for people-intensive projects and software projects are a perfect
example. A strong communication structure needs to be established from the start as well as a
conflict resolution process. Priorities also must be set from the start. It is also vital for
employees to be trained on how to use these different processes for them to be successful.
http://www.brighthub.com/office/project-management/articles/47932.aspx
http://www.brighthub.com/office/project-management/articles/2875.aspx
http://www.brighthub.com/office/project-management/articles/47932.aspx
14
8. What would be an appropriate system development methodology and why?
For the Green_delivery_rus.com, the appropriate system development methodology would be
Prototyping using RAD tools. Prototyping consist of building an experimental system rapidly and
inexpensively, and Rapid Application Development (RAD) is a software development
methodology that involves iterative development and the construction of prototypes. These
methodologies are most appropriate for Green delivery because time is very important in this
business. The Green Delivery team has projected expanding to Virginia and Delaware in 2012,
therefore they need is a system that could be a work-in progress while meeting the needs of
customers.
Prototyping is also very appropriate because Green delivery has not reached its final business
destination yet, and is considering expanding their services like providing food deliveries in the
future. So, a system that can be adjusted, updated to meet their growing needs, refined, tried,
and promote system design changes until a stable system is obtained is what Green delivery
requires. Prototyping will also help design information system that has end- user interface.
Such interface will enable Green Delivery analyze users’ information and exploit the users’
interaction with the website to their own advantage.
The essence of using RAD methodology is very evident because RAD works with iterative
process of prototyping, and is able to create rapid workable system in short period of time
(p507). Since Green delivery requires a system that will be able to add, change, and retire
technology capabilities rapidly and to respond to new opportunities in their business, digital
tools like RAD is very necessary.
Using RAD will also help reduce cost, provide visual tools for their Food segment, and graphical
user interfaces, which will be useful for the analysis of sales especially for their emergency
appointment and rides operation. Green Delivery is a data driven business which makes RAD
methodology very appropriate for them. Since RAD uses prototyping to accelerate software
system, it is able to define users requirements and design the final system.
More so, RAD promotes strong collaborative atmosphere and dynamic gathering of
requirements, therefore, involving the Green Delivery team in the prototyping, unit testing, and
ultimate success of the system.
Reference:
Laudon K.C , Laudon J. P. Management of Information Systems. Prentice Hall. 2010
http://en.wikipedia.org/wiki/Rapid_Application_Development
15
Appendix A: Grading Criteria
Requirements
Maximum Points
Executive Report with
recommendations
10
Parts 1-4
10
Part 5
5
Part 6
5
Part 7
5
Part 8
5
Part 9
5
TOTAL
45
16
YOUR Points