Online Stud Farm Management System

The assignment requires a comprehensive analysis of the online stud farm management system for Globex. It involves understanding key aspects such as project management, effective communication, and collaboration tools. The student is expected to provide detailed information about these elements in their submission.

PROJECT MANAGEMENT: ONLINE STUD FARM MANAGEMENT SYSTEM FOR GLOBEX
Student Details
Project Management:
Online Stud Farm management System for Globex

Abstract
This is a report on the project management and project execution approaches for the
development of the Online Stud Farm management System for Globex. The team chose an
agile SCRUM project management methodology. The project execution followed iterative
developments with daily meetings conducted online and using an online project management
and collaboration software (Wrike). Stakeholders are identified as Globex being the executive
sponsor, Virtucon CEO being a business sponsor, and the project team. The team held
meetings to allocate roles, capture user requirements, define work packages, review progress,
and test product. The project has taught me new leadership and team skills relevant to ICT
project management: one needs both technical and soft skills and for project success

Part One:
1. Project Name / Team / Description – (Team work)
Team Name:
Team Members Role Contact No EMail
Product Owner
Scrum master
Team Member
Team Member
Team Member

2. PROJECT OVERVIEW – (Individual Work)
This case study project aims at developing an OSFMS (Online Stud Farm
management System) for Globex that will replace the existing manual system. The OSFMS
will enable online booking for breeding services, maintain a record of breeds, and ensure the
breeding objectives based on Australian and International standards are maintained. To
achieve this, the team will use project management methodologies, based on the agile
framework, t develop the system: this framework covers the project team charter, a
stakeholder management plan (communication), and a reflection of team meetings and
lessons learned
3. PROJECT DESCRIPTION & OBJECTIVES – Individual work
The objectives of the project is to develop an OSFMS system that will enable farmers
and breeders in NSW to make online bookings for breeding services, make payments,
automate a breeding schedule, and store all records related to breeding in NSW. The system
will store the details of breeders, the details of their studs, while also retaining a platform
where breeders can directly contact the stud master through telephone if there is need. The
system will have a database of all these records and information, and be able to generate
customized reports, such as the number of breeders, studs, and breeding activities. The
envisaged system will therefore be a database driven, online based/ cloud application for
managing breeding services for NSW breeders and farmers, with financial and payment
processing features that can be accessed online from any location.
4. TEAM CHARTER – Team Work
The team roles have been developed based on the Agile project management
methodology which is suited to IT projects (Alexander, 2018)
Team Members Role Skills and Knowledge Inventory
Product Owner Represents stakeholder
requirements and is responsible
for prioritizing work packages,
Must have immense and detailed
knowledge abut the product to be
developed and its features, given

making timely decisions,
providing information to
stakeholders, and ensuring the
product meets the client
requirements. Responsible for
developing the product backlog
(priority work items list)
that this is the clients’
‘representative’. Excellent
communication skills to be able to
effective tell the ‘product story’.
Be an agile individual, able to take
on several roles. Have impeccable
organizational and planning skills,
including reporting and have
people skills to manage teams
(Morris, Pinto & Söderlund, 2013)
Scrum Master Is the team’s lead, responsible
for facilitating smooth operation
of the team, solving problems
such as disagreements,
organizing meetings, securing
the necessary resources for the
team, and removing any
obstacles the team may face
Excellent problem solving skills to
resolve inevitable conflicts in the
team. Excellent planning and
organizational skills. Excellent
communication skills and be very
good at interpersonal relationships
Budgeting and financial
management skills
Reporting skills (Carroll & Morris,
2015)
Team member-
Database
programming
Develop and program the system
database
Technical skills in database
development, programming, and
integration
Team member-
Web
development
Development of the web
interfaces (user interface)
Ability to capture user
requirements, web development
technical skills, including Java,
PHP, Perl, Python
Team member-
System
Developer and
Analyst
Develop and integrate disparate
parts of the system (the front
end, back end, database,
financial system)
Programming skills
System analysis and integration
technical skills
testing skills to test system and

recommend improvements
(Morris, Pinto & Söderlund, 2013)
Role Roles and Responsibilities
Product Owner According to Crookshanks (2015), the product owner plays a crucial
role, including creating the detailed work items list and features for the
system (product backlog); creating the user requirements list and
product features. Testing products to ensure it meets user requirements
and make recommendations for changes if necessary. Provide
leadership on the technical and functional aspects of the product/
system
Scrum master Secure the necessary resources for the team
provide leadership and resolve any problems / disagreements to ensure
work packages remain on course
Arrange meetings and take minutes of meetings
Implement the soft project management skills to ensure goals are met
within schedule and scope, as well as time constraints based on
(Viscardi, 2013)
Database
developer and
programming
Responsible for the design, programming, implementation, and
securing the system database
Web developer Developing the user interfaces and the scripts for the system at both
the front and back end
System Analyst
and Integrator
Analyze, test, and integrate the systems; ensure cloud functionality
and redundancy and functionality of the entire system

a. Team Communications :
Communication in project teams must be systematic to improve chances of project success
(Dunne & Dunne, 2011): Online collaboration and project management tools can enhance
team communications (Stewart, 2008)
Communication
Type
Frequency / Time Location eMails and Document
Storage location
Face to face
initial meeting to
assemble project
team and define
roles
Once before
commencing project
Company project
office
Minutes of the meetings
stored in electronic form
and shared with members
through intranet
Face to face
initial meeting
with client
Twice Client premises
Meeting minutes, in
paper and electronic form
shared through e-mail
with all team members
Face to face
team meeting to
plan project
schedule and
work packages
Three meetings Project Office
Meeting minutes shared
electronically through e-
mail and updated on
online collaboration and
project management
software (Wrike
https://www.wrike.com/)
Daily scrums
done online via
the project
management
software
(Wrike) and
Every day Online (one meeting
per week to be face
to face)
Project management and
collaboration software
(Wrike), E-mail

through Google
Hangouts / Chat
Face to face
product testing
meetings
Every Friday Project office
Project management and
collaboration software
(Wrike), E-mail, notes
taken during testing and
updated on Wrike, e-
mails
Face to face
testing meeting
with client
Every Fortnight Client premises
Wrike, notes
b. Team Rules & Expectations
Individual Work
o I was the Scrum master; this team project gave me new insights and skills,
especially in ensuring team dynamics and conflicts are effectively handled and
the project proceeds as scheduled. This was a new role for me, as I had
previously worked with teams just as a team member. This new role gave me
positive experiences in leadership, conflict management, problem solving, and
how to maintain focus in a project. I have realized that despite the best
planning, conflicts in projects are inevitable, and some people are just a
problem to deal with. Updating all progress on a daily basis and summarizing
all team member contributions on a daily basis proved a huge challenge
Team Work
Team Values –
 Team commitment to the cause

 Cooperation and collaboration
 Effective communication
 Service leadership and motivation
 Respect
Code of Ethics –
o Integrity and originality
o Not taking shortcuts
o Honesty (Marchewka, 2014)
Rules and Expectations –
o All members to ensure physical attendance for face to face meetings at least
90% of the time
o Daily online meetings attendance to be at least 85%
o Ensure contribution to the project, share experiences, work done, and
challenges faced on a regular (daily basis)
o Abide by team problem and conflict resolution mechanism (sharing conflicts
with scrum master)
o Everyone’s has a right to an opinion that the team must agree on
 Signatures –
______________________
________________

______________________
________________
______________________
________________
______________________
________________ Signature
Date
Part Two:
1. Learning Cycles
Meeting Date Organiser Scribe Meeting outcome
Scrum master Product owner Assigning roles
Product Owner Scrum master Understand user
requirements
Scrum master Database
developer
Project planning
System integrator System/ web
developer
Test product and
identify flaws to make
improvements

Product Owner Scrum master Test product with
client and identify
feature to add/
remove
Part Three:
Communication Plan – Team Work
Successful project execution requires effective communication done regularly, in an
inclusive, clear and transparent manner (Bruce, 2015). Team communication should
encourage participation and is effective when used together with online collaboration tools
(Ray, 2017)
Stakeholder
name
Information
to be shared
Frequency of
information
exchange
Location of
information
exchange
Purpose of
communication
Mechanism for
communication
Hardcopy, pdf,
ppt, word,
email, etc
Who What When Where Why How
Globex staff
(Executive
sponsor)
Product
design
Weekly Client
premises
Describe how
project is to be
executed,
product design,
features
Hard copy, e-
mails, memos,
pdf
Virtucon
CEO
Project
execution
plan
Weekly Project office
(Virtucon)
Update on
progress, get
approvals for
resources and
scope changes
E-mail, status
reports, pdf,
word
Product Work done Daily / Online/ Update on work Online project

owner
(project
manager)
Weekly Project
Office
done, challenges
faced
management
software, word,
e-mails
Part Four:
Reflection –
Prior, I understood leadership in an abstract way; that leadership styles require
specific skills in order for one to be an effective leader: I had imagined that a given style of
leadership was sufficient for running projects such as in IT. I also believed the leader must
always be the one ‘leading’; giving direction and telling others what to do. However,
undertaking the project taught me that leadership is very fluid: each situation requires a
different style. Further, this project has taught me that a leader should get ideas from team
members and then synthesize them to develop a common goal. I ave realized the important
role of communication and managing conflicts and disagreements as these are inevitable in
projects. A project manager in the ICT profession requires project management skills and
know the technical details of managing projects such as software development; for example
agile and waterfall methodologies. The project manager also needs effective soft skills such
as motivation, interpersonal, and communication skills as well as technical IT skills in one or
many areas; such as new technologies, systems, and system integration (Jamil, Maravilhas
Lopes, Silva & Ribeiro, 2015). Further, the ICT project manager needs excellent skills in
negotiation and b able to apply analytical skills. Excellent management and organizational
skills are indispensable as is the ability to work with teams and independently (Ohara &
Asada, 2009)

Part Five: Team and Individual Work
References
Alexander, M. (2018). Agile project management: A comprehensive guide. CIO. Retrieved 14
April 2018, from https://www.cio.com/article/3156998/agile-development/agile-
project-management-a-beginners-guide.html
Bruce, R. (2015). Effective Communication in Project Management | TeamGantt. TeamGantt.
Retrieved 14 April 2018, from https://www.teamgantt.com/blog/why-communication-
is-important-in-project-management/
Carroll, J., & Morris, D. (2015). Agile Project Management In Easy Steps, 2nd Edition (2nd
ed.). Warwickshire: In Easy Steps Limited.
Crookshanks, E. (2015). Practical Enterprise Software Development Techniques. Berkeley,
CA: Apress.
Dunne, E., & Dunne, K. (2011). Translation and Localization Project Management: The Art
of the Possible (American Translators Association Scholarly Monograph Series) (1st
ed., pp. 218-219). Amsterdam: John Benjamins Publishing Company.
Jamil, G., Maravilhas Lopes, S., Silva, A., & Ribeiro, F. (2015). Handbook of research on
effective project management through the integration of knowledge and innovation
(1st ed., p. 109). Hershey: IGI Global.
Marchewka, J. (2014). Information technology project management (5th ed., p. 19).
Hoboken, NJ: John Wiley and Sons.
Morris, P., Pinto, J., & Söderlund, J. (2013). The Oxford handbook of project management.
Oxford: Oxford University Press.
Ohara, S., & Asada, T. (2009). Japanese Project Management: KPM--innovation,
Development and Improvement (Monden Institute of Management, Japanese

management and international studies, v. 3) (pp. 107-108). New Jersey: World
Scientific.
Ray, S. (2017). What is a Project Management Communication Plan?. ProjectManager.com.
Retrieved 14 April 2018, from https://www.projectmanager.com/blog/project-
management-communication-plan
Stewart, J. (2008). Project management collaboration tools. Pmi.org. Retrieved 14 April
2018, from https://www.pmi.org/learning/library/project-management-collaboration-
tools-virtual-7040
Viscardi, S. (2013). The professional ScrumMaster's handbook. Birmingham, UK: Packt Pub.