Development of Online Management System for Stud Farm - Project Management

This project management report outlines the development of an online management system for a stud farm, including scope, resources, budget, and risk management strategies.

Running head: PROJECT MANAGEMENT
Student Name
ID Development of Online
management system
for Stud Farm

1
PROJECT MANAGEMENT
Part One:
1.1 MOV - Measurable Organisational Value
Area of Impact Rank (1 to 5)
Operational 1
Customer 2
Financial 3
Strategic 4
Social 5
1.2 Value of the project
The significance that is delivered is illustrated below:
Faster: The service, which is mainly supplied to the customers, is faster as well as much
more appropriate and as a result, the clients have to opportunity of getting solution of their queries
in short period.
Better: The customers can be able to get breeding services and have the opportunity of
paying online for the services with the help of the online. The advancement within the services helps
in making the services of the company much better.
1.3 Appropriate metric
Rank Impact Metrics Timeframe
1 Operational Improvement occurs
within the business
functions and
operations due to
implementation of the
system.
3 months
2 Customer Positive impact is
created on the
customers due to the
services and as a
result, the customers
of the organization
increase.
2months
3 Financial The yearly revenue
that is collected is 0.3
times more than the
revenue that is
collected last year
because of business
expansion within the
new system.
3 months
4 Strategic For providing proper
customer experience,
2 months

2
PROJECT MANAGEMENT
numbers of strategies
are implemented.
5 Social For advertisement,
the companies use the
social media.
1 month
2. Part Two:
2.1 Scope
The scope is:
 Creating design for the interface
 Developing the database
 Breed registry facility
 Developing facility of recording
 Providing reviewing option
 Option for customized communication
 Developing database for marketing
 Contract management facility
 Location identification facility
 Tracking cost facility
2.2 Out of Scope
The out scope is:
 No future plan was included within the project
 Marketing strategies are also excluded from the project
2.3 Assumptions
The assumptions are:
 The hardware as well as software that are needed will be easily available
 Protect team will cooperate for finishing the project
 Budget $ 108,920 s considered for finishing the project.
2.4 Constraints
The constraints are:
 Handling of project quality within the lifecycle of the project
 Avoiding the chances of scope creep
 The project should be finished within the expected time as well as budget.
2.5 Scope Management Plan
The steps include:
 The authority of the organization is committed to create scope development plan
 Setting the boundary of the scope
 Identification of deliverables that is supported by MOV
 Providing confirmation that the scope is appropriately managed
 Making sure that the controls are appropriate to avoid changes in the scope

3
PROJECT MANAGEMENT
2.6 Resource Plan
 People
Resource Name Type Std. Rate
Project planner Work $ 35.00/hr.
Developer Work $ 30.00/hr.
Database administrator Work $ 30.00/hr.
Designer Work $ 35.00/hr.
Human resource manager Work $ 35.00/hr.
Financial manager Work $ 35.00/hr.
Quality analyst Work $ 30.00/hr.
risk manager Work $ 30.00/hr.
Project manager Work $ 50.00/hr.
Technical expert Work $ 35.00/hr.
Risk manager Work $ 30.00/hr.
System administrator Work $ 30.00/hr.
System administrator Work $ 35.00/hr.
Software engineer Work $ 30.00/hr.
Project sponsor Work $ 0.00/hr.
 Technology
Hardware RAM, hardware, desktop
Software Operating system, Java and more.
Network Server
 Facilities
High speed of internet connection is provided as a facility for the developing the
project.
Other
Travel Requirements No facility of traveling is given
Training Requirements The team members are given training if
they are facing any type of issues.
Part three:
3.1 Project Milestones
Milestone Completion date
Milestone 1: Initiation completion Mon 28-05-18
Milestone 2: Project planning completion Thu 07-06-18

4
PROJECT MANAGEMENT
Milestone 3: Design phase completion Thu 21-06-18
Milestone 4: Development completion Thu 30-08-18
Milestone 5: Testing phase completion Fri 14-09-18
Milestone 6: Completion of monitoring and control phase Wed 26-09-18
Milestone 7: Completion of closure phase Mon 01-10-18
3.2 Project activities
Task Name
Online management system development for Stud
Farm
Project initiation phase
Requirement identification
Development of project pan
Cost benefit analysis
Milestone 1: Initiation completion
Planning phase
Identifying needed resources
Scheduling project activities
Allocating work to the team members
Making communication plan
Assigning project resources
Milestone 2: Project planning completion
Design phase
Designing prototype
incorporating features
Determining functional and non-functional needs
Milestone 3: Design phase completion
Development phase
Developing features of breeding
Creating design for the interface
Developing the database
Breed registry facility
Developing mobile related features
Developing facility of recording
Providing reviewing option
Option for customized communication
Developing financial features
Developing database for marketing
Contract management facility
Location identification facility
Tracking cost facility
Milestone 4: Development completion
Testing phase
Black box testing

5
PROJECT MANAGEMENT
performance testing
User-acceptance testing
White box testing
User-acceptability testing
Milestone 5: Testing phase completion
Monitoring and control
Facility of request management
Facility of issue management
Facility of risk management
Team meetings
Undertaking earned value analysis
Milestone 6: Completion of monitoring and
control phase
Closing Phase
Post project review
Stakeholder sign off
Milestone 7: Completion of closure phase
3.3 Project resources
Resource table
Task Name Duration Resource Names
Online management system development for
Stud Farm 97 days
Project initiation phase 97 days
Requirement identification 2 days Project planner, Developer
Development of project pan 3 days Project planner
Cost benefit analysis 2 days Database administrator, Technical
expert
Milestone 1: Initiation completion 0 days
Planning phase 8 days
Identifying needed resources 2 days Developer
Scheduling project activities 1 day Database administrator, Technical
expert
Allocating work to the team members 2 days Developer, Database administrator,
Technical expert
Making communication plan 2 days Project planner, Technical expert
Assigning project resources 1 day Developer, Technical expert
Milestone 2: Project planning
completion 0 days
Design phase 10 days
Designing prototype 4 days risk manager, Financial manager,
Human resource manager
incorporating features 3 days
Software engineer, System
administrator, Human resource
manager

6
PROJECT MANAGEMENT
Determining functional and non-
functional needs 3 days risk manager, Technical expert,
System administrator
Milestone 3: Design phase completion 0 days
Development phase 50 days
Developing features of breeding 15 days
Creating design for the interface 4 days Designer, System administrator,
Software engineer
Developing the database 5 days Project manager, Human resource
manager
Breed registry facility 6 days
Hardware and software
requirements[1],System
administrator, Software engineer,
System administrator
Developing mobile related features 15 days
Developing facility of recording 6 days Software engineer, System
administrator
Providing reviewing option 5 days
Developer, Human resource
manager, Software engineer,
Quality analyst
Option for customized communication 4 days
Database administrator, Human
resource manager, System
administrator
Developing financial features 20 days
Developing database for marketing 5 days Project manager, Designer, System
administrator
Contract management facility 4 days Developer, Software engineer,
Human resource manager
Location identification facility 5 days Project manager, Software
engineer, Human resource manager
Tracking cost facility 6 days Designer, Software engineer,
System administrator
Milestone 4: Development completion 0 days
Testing phase 11 days
Black box testing 2 days Additional cost[1],Risk manager,
Quality analyst
performance testing 3 days Quality analyst
User-acceptance testing 3 days Risk manager, Quality analyst
White box testing 2 days Risk manager, Quality analyst
User-acceptability testing 1 day Risk manager, Quality analyst
Milestone 5: Testing phase completion 0 days Risk manager, Quality analyst
Monitoring and control 9 days
Facility of request management 2 days Project planner
Facility of issue management 3 days Risk manager
Facility of risk management 2 days Risk manager, Quality analyst
Team meetings 1 day Developer, Project planner
Undertaking earned value analysis 1 day Technical expert, Project planner
Milestone 6: Completion of monitoring 0 days

7
PROJECT MANAGEMENT
and control phase
Closing Phase 3 days
Post project review 1 day Project planner
Stakeholder sign off 2 days Financial manager, Project planner
Milestone 7: Completion of closure
phase 0 days
Resource overview
Project planner
Developer
Database administrator
Designer
Human resource manager
Finanacial manager
Qulaity analyst
ris manager
Project manageer
Technical expert
Risk manager
System admnistrator
System administrator
Software engineer
Project sponsor
0 hrs
100 hrs
200 hrs
300 hrs
Actual Work Remaining Work Baseline Work
Figure 1: Resource overview
(Source: Created by author)
Resource plan
Figure 2: Resource plan
(Source: Created by author)

8
PROJECT MANAGEMENT
3.4 Time estimation (Gantt chart)
Figure 3: Time estimation

9
PROJECT MANAGEMENT
(Source: Created by Author)

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

11
PROJECT MANAGEMENT
3.6 Time phase budget
May 2018 June 2018 July 2018 August
2018 September
2018 October
2018
$ 0.00
$ 5,000.00
$ 10,000.00
$ 15,000.00
$ 20,000.00
$ 25,000.00
$ 30,000.00
$ 35,000.00
$ 40,000.00
$ 45,000.00
Time-phase budget
Cost
Figure 5: Time-phase budget
(Source: Created by Author)
Part four:
4.1 Assumptions
 The system will be quite beneficial for the customers
 The team members will work effectively for finishing the project
 The time that is utilized will be around 97 days for finishing the work
4.2 Project risks and management strategy
Risk
ID
Description Probability Impact Rate Assigned
To
Response
Strategy
Threat or
Opportunity
R1 Need of new
requirements
due to
technology
advancement
50 4 200 Resource
manager
This risk can
accepted as
will be
helpful I
creating
advance
system
.Opportunity
R2 Low
understandin
g of project
requirements
80 3 240 Project
managers
The risk can
be
prevented
by
appointing
experienced
project
manager
Threat
R3 Inappropriate
testing
90 4 360 Tester The testing
must be
conducted
properly by
Threat

12
PROJECT MANAGEMENT
utilizing the
needed
time for
preventing
the risk.
R4 Inaccurate
design of the
prototype
90 4 360 Tester The design
of the
prototype
must be
checked
after it is
designed
for making
sure that all
demands of
the
customers
will be
fulfilled and
for
mitigating
the issue
Threat
R5 Low quality of
resources
80 4 360 Quality
analyst
Good
quality of
hardware
and
software
must be
used for
preventing
this issue
threat
Part Five:
 Statement on project quality
The main aim of the project team is to make sure that all the project needs must focuses on
time, cost as well as quality so that proper quality of project can be provided. Some of the
significant tasks that were undertaken by the team for marinating quality include:
 Utilization of testing software for checking resources quality
 Conducting monthly meeting for reflecting on the project quality
 Post project review for ensuring that the objectives of the project are met
 A set of verification activities
Verification Activity When?
Contract verification Project planning phase
Evaluation of source code Development phase
Analysis off interface Requirement phase
 A set of validation activities

13
PROJECT MANAGEMENT
Part Six:
a. Annotated bibliography
Refer to appendices
b. Develop a closure checklist
Activities Status
Does the project testing phase is completed? Yes
Does all the documents of the project are
approved and reviewed?
Yes
Does the requirement traceability matrix is
checked?
No
Does all the issues related with the project is
closed?
Yes
Is project handover finished? No
Is training completed Yes
c. Develop a project evaluation
Evaluation as per project MOV
Objective Checklist (Yes/No)
Does the project maintain quality effectively? Yes
Does scope creep occurs No
Is the project finished within the approved
budget?
Yes
Does the testing phase conducted
appropriately
Yes
Validation Activity When?
Executing source code Development phase
Execution of system test Testing phase
Software design evaluation Designing phase

14
PROJECT MANAGEMENT
Bibliography
Andersen, E. S. (2016). Do project managers have different perspectives on project
management?. International Journal of Project Management, 34(1), 58-65.
Cagliano, A. C., Grimaldi, S., & Rafele, C. (2015). Choosing project risk management techniques. A
theoretical framework. Journal of Risk Research, 18(2), 232-248.
Fernandes, G., Ward, S., & Araújo, M. (2015). Improving and embedding project management
practice in organisations—A qualitative study. International Journal of Project
Management, 33(5), 1052-1067.
Garton, C., & McCulloch, E. (2012). Fundamentals of Technology Project Management. MC Press,
LLC.
Goetsch, D. L., & Davis, S. B. (2014). Quality management for organizational excellence.pearson.
Hegazy, T. (2013). Computer-Based Construction Project Management: Pearson New International
Edition. Pearson Higher Ed.
Heldman, K. (2015). PMP project management professional exam deluxe study guide: updated for
the 2015 Exam. John Wiley & Sons.
Hubicki, M. (2014). Risk Management Plan.
Hwang, B. G., & Ng, W. J. (2013). Project management knowledge and skills for green construction:
Overcoming challenges. International Journal of Project Management, 31(2), 272-284.
Kami, N. (2015). U.S. Patent No. 9,116,916. Washington, DC: U.S. Patent and Trademark Office.
Kendrick, T. (2015). Identifying and managing project risk: essential tools for failure-proofing your
project. AMACOM Div American Mgmt Assn.
Kerzner, H. (2013). Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Larson, E. W., &Gray, C. (2013). Project Management: The Managerial Process with MS Project.
McGraw-Hill.
Mir, F. A., &Pinnington, A. H. (2014).Exploring the value of project management: linking project
management performance and project success. International journal of project
management, 32(2), 202-217.
Nanda, V. (2016). Quality management system handbook for product development companies.CRC
Press.
Pemsel, S., &Wiewiora, A. (2013).Project management office a knowledge broker in project-based
organisations. International Journal of Project Management, 31(1), 31-42.
Stark, J. (2015). Product lifecycle management.In Product Lifecycle Management (pp. 1-29).Springer
International Publishing.
Todorović, M. L., Petrović, D. Č., Mihić, M. M., Obradović, V. L., &Bushuyev, S. D. (2015). Project
success analysis framework: A knowledge-based approach in project
management. International Journal of Project Management, 33(4), 772-783.

15
PROJECT MANAGEMENT
Tornabene, C., Hussain, M. M., Crowe, T., Cohen, N., & Panzer, J. (2012).U.S. Patent No. 8,103,729.
Washington, DC: U.S. Patent and Trademark Office.
Verburg, R. M., Bosch-Sijtsema, P., &Vartiainen, M. (2013).Getting it done: Critical success factors for
project managers in virtual work settings.International Journal of Project
Management, 31(1), 68-79.

16
PROJECT MANAGEMENT
Appendices
Appendix 1: Annotated Bibliography
Article 1: Fernandes, G., Ward, S., & Araújo, M. (2015). Improving and embedding project
management practice in organisations—A qualitative study. International Journal of Project
Management, 33(5), 1052-1067.
The article elaborates the outcomes of a quantitative study that is conducted for developing
proper framework for helping organizations to embed appropriate project management
improvement initiatives which generally aims to identify the key PMIIs and factors that is dependent
on the circumstances for encountering different organizations (Fernandes, Ward & Araujo, 2015).
The research report on the innovation generally states the literature, which generally helps in
providing proper set of salient features. The initial stage of framework conceptualization is very
dependent on the literature that was mainly utilized for empirical research.
Article 2: Cagliano, A. C., Grimaldi, S., & Rafele, C. (2015). Choosing project risk management
techniques. A theoretical framework. Journal of Risk Research, 18(2), 232-248.
This article reflects on the selection of project management technique. According to
Cagliano, Grimaldi and Rafele (2015), the enhancing pressure of quality with minimizing time and
cost within the project are placing emphasis in handling the risks that are associated with the
project. The author illustrates that lots of techniques as well as models are developed which are
generally utilized for managing the risks of the project. However, the knowledge on risk
management is quite important for properly dealing with complex projects. Proper guidelines must
be provided in thee aspect of operational and managerial position so that the risks as well as
challenges associated with the project can be mitigated easily.
Article 3: Andersen, E. S. (2016). Do project managers have different perspectives on project
management?. International Journal of Project Management, 34(1), 58-65.
The paper argued on the question that whether all the project managers have similar
perspective in context to project management. Andersen (2016) stated that different project
managers have different perspectives in context to project management. The author elaborates that
project manager mainly reflects on delivering the project on time within the approved budget b not
compromising the quality. The organizational perspective states that the focus of the project
manager is to create proper value within the project. The survey that is conducted that different
perspectives are present within the project managers