Date post: | 04-Jan-2016 |
Category: |
Documents |
Upload: | philomena-allen |
View: | 218 times |
Download: | 0 times |
PROJECT PLAN
AJ Construction & Development Co
Portal & Customer Information and Billing System
INTRODUCTION Covers the implementation and
development of the Billing and Customer Information System of AJ Construction and Development Co
In implementing the system, the agents of the company will use it as a medium in every transaction
The web portal will be a stepping stone for the company to enter a more competitive stage
ALTERNATIVES
Stick to the manual system
Implement either the portal or the CBIS
GOALS AND OBJECTIVES
GOALS AND OBJECTIVES (BUSINESS) Increase the public penetration of the company through the World Wide Web
Advertisement Faster Report Generation. The faster the In – Out of Information through the Company
PROJECT GOALS AND OBJECTIVES Time Management (must achieve every
task defined in the Work plan) Must reflect the needs of the company Ensure that end users have input into
the design process. Accomplish project goals and objectives
within defined budget and time parameters.
Minimize impact to AJ’s standard operations within the affected units.
Craft a favorable and secure system that will make the company more profitable.
PROJECT GOALS AND OBJECTIVES Facilitates coordination and information sharing
both internal and external to the participating departments/divisions in the company.
Enhances the ability and effectiveness of staff to perform their jobs.
Provides high levels of data security. Provides an open, flexible, reliable technology
base for the future. Facilitates the electronic capture of data at its
source. Is easy to use. Eliminate redundant data entry throughout the
organization.
SCOPE
SCOPE DEFINITION
Web PortalCustomer Information System
Billing System
ITEMS BEYOND SCOPE
InventoryExpenses calculation during the construction of the house.
PROJECTED BUDGET PLAN
Task Name Actual Cost
Team Orientation PhP3,840.00
Company/Business Observation
PhP3,840.00
Planning PhP3,840.00
Development PhP50,600.00
RISK ASSESSMENT Step One: Identifying Project Steps
Step two: Identifying Potential Threats
Step Three - Estimate the Level of Risk
INITIAL PROJECT RISK ASSESSMENTRisks
Source / Cause
Effects Domain LevelMitigation Strategies
Integrity
Data corruption, Errors, Omissions
Data corruption User Interface 7Proper segregation of duties
AccessInappropriate security access set-up
Confidentiality violation, data lost or data corruption eiher by virus infection, worm, trojan attack programs etc
Business Process
3
How to separate incompatible duties within an organization and how to provide the correct level of empowerment to perform a function.
Availability
=> Natural disasters (Fire, Flood etc) causing hardware and software failure. => Power outage => Theft
Short term / Long term business disruptions to system
Critical IS system, applications and data.
3
Risks that can be avoided by monitoring performance proactively by addressing systems issues before a problem occurs
InfrastructureLack or weak organization planning
Disorganized and disfunctional IT decisions. Lack of proactive security policies and procedures or inconsistent one among IS and divisions.
IS department mission and organization
3
Define how I/T will impact the business and how I/T is articulated. It is important to have adequate executive level support and buy-in to this direction and an adequate organizational (people and process) planning to ensure that I/T efforts will be successful.
PROJECT ASSUMPTIONS Through observation the team
can capture the business process of the company
Management will ensure that project team members are available as needed to complete project tasks and objectives.
The project will be accomplished on time set by the team.
The resources needed by the project team will be provided by the budget given.
If a risk will arise, it will be handled by the team through the risk assessment management defined by the project.
The system that will be developed by the team would be very beneficial to the company.
AJ Dev & Const Inc employees are willing to change standard business operations to take advantage of the functionality offered by the new computerize system.
Management will ensure that project team members are available as needed to complete project tasks and objectives.
AJ’s employees (especially the Manager) will participate in the timely execution of the Project Plan (i.e., timely approval cycles and meeting when required).
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 project.
Every schedule, costs, e.g. may change as new information and issues are revealed.
CONSTRAINTS
Project ConstraintsPoor performanceWork accomplished vs. Scheduled
Resources
CRITICAL PROJECT BARRIERS
Removal of project funding.
Lack of Clarity Lack of Ongoing Client Support
Technology Gap
Roles Responsibilities
Project Manager The person responsible for
ensuring that the Project
Team completes the project;
secure acceptance and
approval of deliverables from
the Project Sponsor and
Stakeholders
Project Team Members Responsible for executing
tasks and producing
deliverables as outlined in the
Project Plan and directed by
the Project Manager
Programmer Responsible on the
functionality of the program,
it ensure that the develop
system has no errors and user
friendly
Database Administrator Responsible for the security of
stored data, organizing data and
retrieving stored data.
System Analyst Responsible for analyzing the problem,
the analyst must define and solve the
problem. Identify the requirements for
the problem to be resolved.
Users
Project Sponsors
- Commits department resources
- Approves major funding and
resource allocation strategies, and
significant changes to
funding/resource allocation
- Resolves conflicts and issues
- Provides direction to the Project
Manager
- Review project deliverables
ISSUE MANAGEMENT The data contained in the
document will probably change as the development goes on. With this, modifications would be allowed and be coordinated with the following processes:Step 1: As soon as changes which impact the major part of the project occur, the Project Management will document the issue.
Step 2: The Project Manager will review the changes and determine the linked impact to the project with added recommendation. Forward the issue to the Steering Committee for them to review and decide.
Step 3: The Steering Committee should make consent whether to approve, reject, or modify the request based on the Project Manager’s recommendation and their own judgment. And be forwarded to the Project Sponsor, with a written summation of the issue, for final resolution.
Step 4: The Project Sponsor shall review the issue(s) and render a final decision on the approval or denial of a change.
Step 5: Following an approval or denial (by the Steering Committee or Project Sponsor), the Project Manager will notify the original requestor of the action taken. There is no appeal process.
COMMUNICATION PLANKey Audiences: Company/Clients
UsersProject Sponsors
Project Manager Team Members
ProgrammerDatabase AdministratorSystem Analyst
AudienceIssues related to
this AudienceCommunications
ObjectivesActivities
Project Sponsors
Project funding and budget allocation
To ensure that the project can will provided enough funds
Financial finalization
User
Interface awareness
To ensure that the user can operate the system.
Acquire more clients
Process reports
Project manager
Estimated cost may not achieve.
Compatibility time to cost and scope
Scope VS time
To ensure that the all task are accomplished.
To ensure that time, cost and scope are monitored
Distribution of task
Team orientation
Work assessment
Programmer
System functionality
System maintenance
To ensure that the system is user friendly
To ensure that the system has no errors
To ensure that the system is being maintain
To ensure that the system provides the needs of the client.
Maintenance System testing Analysis System design Documentation
Database Administrator
Proper normalization
Design and planning
Naming Data Standards
To ensure that the data that will be store in the database are secured
To ensure the Fine flow of queries
Maintaining Database
Managing Data
Organizing Data
Storing Data Retrieving
Stored Data Securing
Data
System analyst
System requirements
Time lines Communicati
on between project manager and customer
To ensure that the system requirements are achieved
To ensure that the system is finish on time
Analysing problems
Identifying system requirements
Identifying time cost