Developing Online Farm Management System for Stud Farm

This project aims to develop an online farm management system for Stud Farm to improve data management and operations. The project overview, scope, assumptions, risk analysis, and evaluation criteria are discussed in detail. The measurable organizational value (MOV) is summarized in a clear and concise statement, and MOV metrics are provided. The resource plan, including the work breakdown structure (WBS), is also included.

Student Name
ID Developing Online Farm
Management System
for Stud Farm

Table of Contents
Introduction...........................................................................................................................................2
Project Overview...............................................................................................................................2
Project Background:..........................................................................................................................2
1. Part One: (15 Marks).........................................................................................................................2
1.1 MOV - Measurable Organisational Value (5 Marks).....................................................................2
1.2 SUMMARISE THE MOV IN A CLEAR CONCISE STATEMENT..........................................................2
1.3 MOV Metrics................................................................................................................................2
2. Part Two: (10 Marks) 2.1 Scope....................................................................................................3
2.2 Out of Scope....................................................................................................................................3
2.3 Assumptions....................................................................................................................................3
2.4 Constraints......................................................................................................................................3
2.5 Scope Management Plan.............................................................................................................4
2.6 Resource Plan (from MS-Project).................................................................................................4
3. Part Three..........................................................................................................................................6
4. Part Four............................................................................................................................................8
4.1 Assumptions................................................................................................................................8
4.2 Risk Analysis.................................................................................................................................8
5. Part Five.............................................................................................................................................8
5.1 Quality Statement........................................................................................................................8
5.2 Verification Activity......................................................................................................................8
5.3 Validation Activities.....................................................................................................................8
6. Part Six...............................................................................................................................................9
6.1 Annotated Bibliography...................................................................................................................9
6.2 Checklist.......................................................................................................................................9
6.3 Evaluation Criteria.......................................................................................................................9
Bibliography.........................................................................................................................................10
Appendix.............................................................................................................................................11

Introduction
Project Overview
The project of Developing Online Farm Management System for Stud Farm is a IT technology
development project developed for the implication of the effective implication of the improved data
management system. The implication of the project deliverable would be helpful for developing the
project and aligning it for the formation of the activities.
Project Background:
The online stud farm has developed their operations for the improvement of their business in
livestock breeding for horses and stallion. They provide services to the customers having stallion
barn and medical support too. The organization would be helpful for forming the development of
the activities. The alignment of the project activities would allow the supportive deployment of the
activities.
1. Part One: (15 Marks)
1.1 MOV - Measurable Organisational Value (5 Marks)
Area of Impact Rank (1 to 5)
Operational 1
Financial 2
Customer 3
Strategy 4
Social 5
1.2 SUMMARISE THE MOV IN A CLEAR CONCISE STATEMENT
The factor of operational holds the most critical value for the development of the successive
integration of the Stud Farm project.
Better – Developing Online Farm Management System for Stud Farm project would
result in forming the utilization of the activities forming the implication of the activities.
Faster – Improved faster and effective operations for the implication of the farm
activities
Cheaper – Overall cost of the operations of Stud Farm would be decreased for the
deployment
Do more – Cloud system development would be formed for the deployment of the
activities
1.3 MOV Metrics
Area of Time Frame Metrics

Impact (months)
Operational 6 Activities would be deployed for listing the operations of
Stud Farm
Financial 5 Financial audit and deployment would be aligned for the
management of activities
Customer 8 Alignment of the customers would be aligned for the
implication of the successive development of activities
Strategy 4 The strategy development would align for the implication
of the activities
Social 3 The interaction of the public would be socially intrigued for
the alignment of the activities
2. Part Two: (10 Marks)
2.1 Scope
 Accumulation of the required resources for the Stud Farm
 Stud farm would design and deploy the system for their benefit
 System development would imply the alignment of the testing and developing
 Documentation for the reports and test results are reported
 Maintenance plan would be supported by the system
2.2 Out of Scope
Documentation requirement for the project would exclude the development of project management
plan
2.3 Assumptions
 Project would require 91 days for completing the project
 Project would require a budget of $65,000.00 for completion
 Resources would be easily available
 Deployment plan would be sustainable
2.4 Constraints
 Project is limited to the technology innovation and development
 Skills of the human resources is another constraint for the project

Collect Requirements
Define Scope
Create WBS
Validate Scope
Control Scope
2.5 Scope Management Plan
Step 1: Collecting required materials for the project scope description
Step 2: Defining the immediate project scope and the implication of the activities
Step 3: Creating specific work packages for the project scope description
Step 4: Project scope would be validated in the project
Step 5: Changes in the project scope would be controlled
2.6 Resource Plan (from MS-Project)
People
ID Resource Name Work
1 Analyst 72 hrs
Idetification of the organization's requirments 40 hrs
Analysis of requirments phase 32 hrs
2 Project Manager 136 hrs
Development of requirement list 48 hrs
Accumulation of resources 56 hrs
Closing 32 hrs
3 Designer 64 hrs
Development of design 64 hrs
4 Database Admin 72 hrs
Formation of database 72 hrs
5 IT engineer 112 hrs
Integration of design and database 48 hrs
Development of complete system 64 hrs
6 Developer 176 hrs
Integration of system 72 hrs
Deployment of the system 56 hrs
Maintenance of system 48 hrs
7 Trainer 96 hrs
Completion of training of staff 96 hrs
Details
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
M S S F T W T M S S F T
Jun 17, '18 Jul 1, '18 Jul 15, '18 Jul 29, '18 Aug 12, '18 Aug 26, '18
32h 8h 16h 16h
32h 8h
16h 16h
32h 16h 16h 32h 8h
32h 16h
16h 32h 8h
24h 32h 8h
24h 32h 8h
32h 40h
32h 40h
32h 32h 32h
32h 16h
16h 32h

Technology
Hardwar
e
Design Tools, System, Database, Deployment tools, Maintenance tools
Software OS, Programming Software
Network Database Server
Facilities
No specific station would be required for the project and the execution of the project activities
would be eased by the development of the specific work package
Other
Travel Requirements NA
Training Requirements Training would be required for the staff
for using the new system

3. Part Three
ID Task
Mode
WBS Task Name Duration Start Finish Predecessors
0 0 Developing Online Farm
Management System for Stud
Farm
91 days Tue
6/26/18
Tue
10/30/18
1 1 Initiating 11 days Tue 6/26/18 Tue 7/10/18
2 1.1 Idetification of the
organization's requirments
5 days Tue 6/26/18 Mon 7/2/18
3 1.2 Development of requirement list6 days Tue 7/3/18 Tue 7/10/18 2
4 2 Analysing 11 days Wed 7/11/18Wed 7/25/18
5 2.1 Analysis of requirments phase4 days Wed 7/11/18Mon 7/16/18 3
6 2.2 Accumulation of resources 7 days Tue 7/17/18 Wed 7/25/185
7 3 Designing 17 days Thu 7/26/18 Fri 8/17/18
8 3.1 Development of design 8 days Thu 7/26/18 Mon 8/6/18 6
9 3.2 Formation of database 9 days Tue 8/7/18 Fri 8/17/18 8
10 4 Implementing 14 days Mon 8/20/18Thu 9/6/18
11 4.1 Integration of design and
database
6 days Mon 8/20/18Mon 8/27/18 9
12 4.2 Development of complete system8 days Tue 8/28/18 Thu 9/6/18 11
13 5 Accepting 21 days Fri 9/7/18 Fri 10/5/18
14 5.1 Integration of system 9 days Fri 9/7/18 Wed 9/19/1812
15 5.2 Completion of training of staff12 days Thu 9/20/18 Fri 10/5/18 14
16 6 Deploying and Maintaining 13 days Mon 10/8/18Wed 10/24/18
17 6.1 Deployment of the system 7 days Mon 10/8/18Tue 10/16/1815
18 6.2 Maintenance of system 6 days Wed 10/17/18Wed 10/24/1817
19 7 Closing 4 days Thu 10/25/18Tue 10/30/1818
Analyst
Project Manager
Analyst
Project Manager
Designer,Design tools[1]
Database Admin,Database[1]
IT engineer,System[1]
IT engineer
Developer
Trainer,Training Manuals[1]
Developer,Deployment tools[1]
Developer,Maintenance tools[1]
Project Manager
M S T T S F W M
Apr 22, '18 Jul 1, '18 Sep 9, '18 Nov 18, '18

June 2018 July 2018 August 2018 September 2018 October 2018
$0.00
$2,000.00
$4,000.00
$6,000.00
$8,000.00
$10,000.00
$12,000.00
$14,000.00
$16,000.00
$18,000.00
$20,000.00
$1,280.00
$15,010.00
$18,310.00
$13,288.33
$17,111.67
Cost
Analyst Project
Manager Designer Database
Admin IT engineer Developer Trainer
0 hrs
20 hrs
40 hrs
60 hrs
80 hrs
100 hrs
120 hrs
140 hrs
160 hrs
180 hrs
200 hrs
72 hrs
136 hrs
64 hrs 72 hrs
112 hrs
176 hrs
96 hrs

4. Part Four
4.1 Assumptions
 Project would require 91 days for completing the project
 Project would require a budget of $65,000.00 for completion
 Resources would be easily available
 Deployment plan would be sustainable
4.2 Risk Analysis
Risk
ID
Risk Probability Impact Rate Assigned
To
Response
Strategy
Threat or
Opportunity
1 Delayed Activities 90 2 180 Project
Manager
Exploit Opportunity
2 System Errors 60 5 300 IT Engineer Mitigate Threat
3 Cost Resource
Issues
70 3 210 Budgeter Avoid Threat
4 Limitation of
skills and
proficiency
50 2 100 HR
Manager
Transfer Threat
5 Design flaws 75 3 225 Designer Reduce Threat
5. Part Five
5.1 Quality Statement
Developing Online Farm Management System for Stud Farm project would result in forming the
utilization of the activities forming improvement for faster and effective operations, with decrease in
overall cost, and scope for Cloud system deployment
5.2 Verification Activity
Verification Activity When?
Prototyping Developing of system
Design Simulation Designing of system
Alpha Testing Deployment of system
5.3 Validation Activities
Validation Activity When?
External Audits Project Initiation
Final Documentation Project Closure
Evaluation of test results Project testing

6. Part Six
6.1 Annotated Bibliography
See in appendix
6.2 Checklist
Closure Checklist
All resources have been accumulated successfully 
Sustainable plan for project execution is made 
Development of feasible design for system 
Deployment of the system done on single platform 
Closure documents have been made probably 
6.3 Evaluation Criteria
 Implementation of project plan
 Proper documentation process
 Effective alignment of the activities
 Feasible system developed

Bibliography
Conforto, E. C., & Amaral, D. C. (2016). Agile project management and stage-gate model—A hybrid
framework for technology-based companies. Journal of Engineering and Technology
Management, 40, 1-14.
Cooper, R. G., & Sommer, A. F. (2018). Agile–Stage-Gate for Manufacturers: Changing the Way New
Products Are Developed Integrating Agile project management methods into a Stage-Gate
system offers both opportunities and challenges. Research-Technology Management, 61(2),
17-26.
Hansen, L. K., & Svejvig, P. (2018). Agile project portfolio management, new solutions and new
challenges: preliminary findings from a case study of an agile organization. In IRIS/SCIS
Conference 2018.
Hoda, R., & Murugesan, L. K. (2016). Multi-level agile project management challenges: A self-
organizing team perspective. Journal of Systems and Software, 117, 245-257.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Layton, M. C., & Ostermiller, S. J. (2017). Agile project management for dummies. John Wiley & Sons.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Špundak, M. (2014). Mixed agile/traditional project management methodology–reality or illusion?.
Procedia-Social and Behavioral Sciences, 119, 939-948.
White, K. R., & FELLOW, P. (2014). Agile project management. The AMA handbook of project
management, 441-450.

Appendix
1. Hoda, R., & Murugesan, L. K. (2016). Multi-level agile project management challenges: A self-
organizing team perspective. Journal of Systems and Software, 117, 245-257.
Agile project management is an iterative model for the development of the activities forming the
implication of the operations for forming the utilization of the activities. The technology based
organizations had provided the formation of the successive alignment activities. The utilization of
the infringement methods would allow the development for using the activities. The analysis would
also form the utilization would form the implication of the activities. The hybrid framework for the
project would be implied for developing the alignment of the operations.
2. Layton, M. C., & Ostermiller, S. J. (2017). Agile project management for dummies. John Wiley &
Sons.
Agile structure is very helpful for the formation of the activities listing the employment of the
operations favoring the alignment of the successive development models. The development of the
activities has also formed the utilization of the activities favoring the alignment of the improved
performance development. The implication of the activities would help in ceasing the activities for
the formation of the operations. The agile development would also help in ceasing the reality of the
activities and it would help in listing the project plan in a simplified method.
3. Špundak, M. (2014). Mixed agile/traditional project management methodology–reality or
illusion?. Procedia-Social and Behavioral Sciences, 119, 939-948.
Agile project management is an iterative model for the development of the activities forming the
implication of the operations for forming the utilization of the activities. The analysis would also
form the utilization would form the implication of the activities. The hybrid framework for the
project would be implied for developing the alignment of the operations. The implication of the
activities would help in ceasing the activities for the formation of the operations. The agile
development would also help in ceasing the reality of the activities and it would help in listing the
project plan in a simplified method.