Development of Online Management System for Stud Farm - Project Report

This project report details the development of an online management system for a stud farm, encompassing various project management aspects. The report begins with a measurable organizational value (MOV) analysis, assessing the project's impact across different areas like operations, customer relations, and finance. It outlines the project's value proposition, emphasizing cost savings, improved service delivery, and faster response times. The report then defines the project's scope, including software and hardware procurement, integration, and development of various features. It also specifies out-of-scope items, assumptions, constraints, and a scope management plan. A detailed resource plan is provided, listing personnel, technology, and facilities. The project's milestones, activities, and budget are presented, along with risk assessment and management strategies. The report concludes with a statement on project quality, a closure checklist, and a project evaluation, followed by an annotated bibliography and appendices. This project provides a comprehensive overview of the project management lifecycle, from initiation to closure.

Student Name
ID Development of Online
management system
for Stud Farm

1. Part One:
1.1 MOV - Measurable Organisational Value
Area of Impact Rank (1 to 5)
Operation 1
Customer 2
Financial 3
Social 4
Strategy 5
1.2 Value of the project
The project value is illustrated below:
Cheaper: The organization can save huge amount of money as they do not have to spend
money on managing information and data as it is done by the new system.
Better: The breeding services will be delivered online to the customers, which is quite better
than the manual service that is earlier provided.
Faster: The customers can get response from the organization quite faster if they have any
questions or queries as compared to previous situation.
1.3 Appropriate metric
Rank Impact Metrics Timeframe
1 Operation The new system helps
in increasing the
efficiency of the
operation by 15%.
2 months
2 Customer The organization
customers enhances
by 10% due to the
new facilities.
3 months
3 Financial The revenue grows by
17% due to the
utilization of the new
system.
4 months
4 Social The platform of social
media is utilized for
reaching the
customers.
1 month
5 Strategy Proper organizational
strategy is used for
attracting more
customers.
3 months

2. Part Two:
2.1 Scope
The following points are included within the scope:
 Developing the software procurement
 Developing the hardware procurement
 Integration of hardware with the existing system
 Initiating with proposed system
 Development of prototype
 Implementing breeding, financial and mobile features
 Integration with UI
 Evaluating the system function
 Development of online management system
 Documentation
2.2 Out of Scope
The following points are excluded from the project scope:
 The facility of training within the project
 Detailed illustration about the project suppliers involved
2.3 Assumptions
The points that are assumed before initiating the projects are listed below:
 The budget that will be required for developing the online management system will be
$93,352
 The timeframe that is required by the project for completion will be 75 days.
2.4 Constraints
The points that are considered as constraints for the project are listed below:
 The budget of developing the online management system must be finished within
$93,352
 The timeframe that is required for completion must be 75 days
 Scope of the project must be used during project progress otherwise it would be
quite difficult to finish the project on time.
2.5 Scope Management Plan
The project management plan includes steps that are as follows:
Understanding project requirements: The requirements as well as needs of the project must
be properly understood in order to avoid the occurrence of scope creep.
Determining project creep signs: The scope creep signs must be identified in this initial stage
so that the impact that it will generally create can be easily mitigated.

Accounting financial changes: The changes that are occurred within the budget due to
scope creep must be successfully managed with the help of the project managers.
2.6 Resource Plan
 People
Resource Name Std. Rate
Project Manager $50.00/hr.
Marketing and Commerce Manager $35.00/hr.
Technical Expert $40.00/hr.
Tester $40.00/hr.
Technical Integration Specialist $40.00/hr.
Developer $40.00/hr.
IT Manager $35.00/hr.
Data Management Officer $40.00/hr.
Project Supervisor $30.00/hr.
Human resource manager $30.00/hr.
Financial manager $30.00/hr.
Programmer $40.00/hr.
Quality analyst $35.00/hr.
Risk manager $30.00/hr.
Project planner $42.00/hr.
 Technology
Hardware RAM, desktop, hardware
Software Server, Java, Operating system
Network Application firewall
 Facilities
First-aid facility is present for both the team members as well as for other workers
who are involved with the project work.
 Other
Travel Requirements Additional travel expense is given to
the workers who work overtime.
Training Requirements Training facility is arranged for the
newly hired workers of the
organization.

Part three:
3.1 Project Milestones
Milestone Completion date
Milestone 1: Completion of project planning phase Sat 16-12-17
Milestone 2:Completion of initiation phase Mon 08-01-18
Milestone 3:Completion of development phase Mon 12-03-18
Milestone 4: Completion of testing phase Mon 19-03-18
Milestone 5:Completion of closure phase Fri 30-03-18
3.2 Project activities
Figure 1: Project activities

(Source: Created by Author)
3.3 Project resources
Figure 2: Project resources
(Source: Created by Author)

3.4 Time estimation
Figure 3: Time estimation
(Source: Created by Author)

3.5 Project budget
Figure 4: Project budget
(Source: Created by Author)

3.6 Time phase budget
Figure 5: Time-phase budget
(Source: Created by Author)

Part four:
4.1 Assumptions
The points that are assumed are listed below:
 The budget that will be required for developing the online management system will be
$93,352
 The timeframe that is required by the project for completion will be 75 days.
4.2 Project risks and management strategy
Risk
ID
Description Probability Impact Rate Assigned
To
Response
Strategy
Threat or
Opportunity
1 Inexperienced
quality
analyst
Up to 80% High High Human
resource
manager
Experienced
quality
analyst must
be hired so
that the
project
quality can
be properly
maintained.
Threat
2 Insufficient
budget
Up to 90% High High Financial
manager
Proper
budget
estimation is
done by
undertaking
proper
market
analysis so
that rates of
resources
can be
determined.
Threat
3 Inappropriate
management
Up to 74% Medium Mediu
m
Project
manager
Proper
management
strategies
required to
use for
avoiding the
issue.
Threat
4 Insufficient
training
facility
Up to 76% High Mediu
m
Project
planner
Effective
facility of
training
needs to be
arranged by
the project
managers.
Threat
5 Extending
project time
Up to 80% High Mediu
m
Project
manager
The
extension of
Opportunity

project time
is done for
incorporating
extra
features
within the
system
which
generally act
as a positive
risk though it
enhances
project
budget.
6 Insufficient
resources
Up to 69% Medium High Resource
manager
Proper
resource
facility must
be arranged
before
initiating
with the
project.
Threat
Part Five:
 Statement on project quality
It is quite essential to maintain the quality of the project by following the scope so that the
demands and requirements of the clients can be easily fulfilled. The organization uses proper tactics
for managing the quality of the project and some of the steps that are taken by Stud farm are listed:
 Weekly meetings are arranged for determining the project status
 Quality analyst is hired for checking the quality of the hardware as well as software
 Testing is performed before the system is deployed
 A set of verification activities
Verification Activity When?
Code review The code that is used is reviewed
after utilization.
Checking of project report The documents are reviewed in the
final project phase
Verification of testing outcome Testing outcome are checked after
the testing phase.
 A set of validation activities
Validation Activity When?
Validating users requirement Before initiating the project, the
requirements of the users are
validated.
Software checking validation Before utilizing the software in the
project it is checked.
Auto-script validation It is completed after the project
database is created.