Project Plan: Development of OSFMS for Globex (Team Name)

This project plan outlines the development of an Online Stud Farm Management System (OSFMS) for Globex, utilizing the agile scrum methodology. The project aims to replace Globex's manual breeding services with a web-based system, automating tasks like booking, registration, financial transactions, and reporting. The plan details team roles, responsibilities, communication strategies, and ethical guidelines. It includes a project charter, user stories, a product backlog, and outlines the system's features, such as a database for stallion and mare owners, a breed registry, and a mobile interface. The project emphasizes effective project management, team collaboration, and adherence to ethical standards, with the goal of delivering a comprehensive and efficient OSFMS solution.

PROJECT PLAN FOR THE
DEVELOPMENT OF THE
OSFMS
<<Your Student ID>> - <<Your Name>>
[Email address]
Abstract
This project details how the [] team will undertake to develop an OFSMS for Globex.
The team will use the agile scrum methodology to execute the project. Each team
member has a role suited to their skills. The project so far has given great insights on
practical project management, including team roles, team regulations, communication
with stakeholders, and application of leadership and project skills learned in class in a
practical setting

PROJECT PLAN FOR THE DEVELOPMENT OF THE OSFMS 1
Part One
1. Project Name / Team: (Team)
Team Name: Team Name ()
S. No Team Member Contact
Number
Email Role
1 Product Owner
(Project
Manager)/
System
Integrator
2 SCRUM Master
(Team lead)/
Developer
3 Database
Developer
4 Web
Applications
Developer
Based on ('Harvard Business Review', 2016)
2. Project Overview
Many stud farms offer breeding services to farmers in NSW; the service includes a database
of breeders and interested parties have to make a call or sending an e-mail to book for
services such as stud breeding. These details are then entered by an operator into a diary or
book by the stud farms, and keep a record of the enrollment of studs into breeding registers
services in accordance with local and international standards. Globex has been a long term
client of Virtucon, and so has contracted Virtucon to develop a suitable digital/ online based
system to replace and automate the breeding tasks currently being undertaken using a manual
system. The goal of stud farms is to ensure the true thoroughbreds percentage is maintained,

PROJECT PLAN FOR THE DEVELOPMENT OF THE OSFMS 2
while also offering breeding. The proposed system will replace the current manual systems
and to achieve the desired objective, Virtucon needs to use project management skills to
achieve the project objectives.
Project Description & Objectives
Globex offers stallion breeding and management services to a variety of users, including
those in rural areas in NSW using a manual system where people make calls, have bookings
made, and the details written in a journal/ register. The manual system has become
cumbersome and Globex is seeking to replace it with an Online Stud Farm Management
System (OSFMS). The new system will be a web based IT that enables users to access
services from a web interface where they can register, make a request, book for a service such
as DNA testing, obtain paternity certifications, obtain foal ID cards, book for micro chipping,
book for veterinary services, confirm payments, post queries, and have a mobile feature in
which data can be entered into the system in real time and updated to the database. The
OSFMS contains a database with stallion and mare owners, a breed registry, and will enable
financial transactions to be undertaken from the site, and have a mobile interface to enable
the system be used by people in the field.
The system should have a database of stallion and mare owners with their full booking
history to make possible targeted digital and print marketing initiatives and news releases.
The details of the breeder will also be stored in the database, including their company name,
name of person, and their contacts as well as their business type. Users can check further
details including breed color, insurance details for public liability. The system should have a
financial management system that includes a marketing and general ledger database and
produce stallion breeding contracts as well as allow location status of horses to be monitored
in real time. Farrier and vet charges should be entered into the system and allocated to horses,
enable expenses and costs to be tracked, and allow discounts to selected clients. This project
is about developing the OSFMS system with all the desired features and more, testing it,
deploying, and providing training and maintenance: to this end, the team is to develop a
project charter and a framework on how to manage and execute the project to achieve its
objectives.
3. Team Charter
Team
Members
Role Skills and Knowledge Inventory

PROJECT PLAN FOR THE DEVELOPMENT OF THE OSFMS 3
Product
owner and
project
manager,
also
perform
system
integration
roles during
developmen
t
Have technical knowledge of systems development and
integration to enhance understanding of how the system
should work.
Have effective soft skills that include effective leadership and
able to apply different leadership styles depending on the
situation, motivational skills, effective communication and
interaction skills, personal integrity, excellent organizational,
planning, and time management skills (Lindstrom, 2018)
Be an excellent story teller to be able to develop the product
backlog and itemize product and user requirements
The person must be an excellent representative, able to fully
represent the product owner and ensure goals are met
The person will have the requisite technical and practical
skills in project management using agile methodologies and
know how to manage the project scope, budget, and timelines
(Sverrisdottir, Ingason, & Jonasson, 2014, pp. 261-263)
The person must also have effective team skills to work
within a team as well as financial management and budgeting
skills to ensure the project meets its financial targets (Wick,
2016).
SCRUM
Master
Must have the soft skills necessary for ensuring team
harmony, including excellent communication and
interpersonal skills, team player, excellent organization and
time management skills
Conflict resolution skills must be effective and top notch
Technical IT skills in systems development to assist with the
technical work and be able to understand how the system
works ('Agile Trainings', 2018)
Database
developer
Soft skills in communication to be able to work within a team
Team skills and be a team player
Technical skills in database systems design, programming,
development, and database security
Knowledge of cloud computing and cloud based database

PROJECT PLAN FOR THE DEVELOPMENT OF THE OSFMS 4
architectures
System integration technical skills
Technical and working knowledge of various database
systems and approaches, including SQL, My SQL, Java, Java
Script, Python, and Perl, and fully understand the concept of
relational databases ('Programmer Blogspot', 2010)
Web
application
developer
Excellent communication, team, and interpersonal skills
Technical skills in web programming and development
languages, including C++, Java, PHP, HTML and HTML 5,
C, Ruby, Python, Perl, CSS, and Graphic systems
Excellent technical skills in system development and
integration
Application testing skills
Cloud computing knowledge and understanding of various
cloud architectures
System development technical skills
Knowledge of human computer interface design principles
and components (Heltzel, 2016
Role Roles and Responsibilities
Project
manager
The project manager is the product owner based on the Agile SCRUM
methodology proposed for this project.
Takes overall leadership of the team and this involves crating a unity of
purpose, getting the team to work together, and setting rules, regulations,
and ethical standards as well as the rules of engagement
The project manager will ensure that the project objectives are met within
the constraints of time, scope, and resources
Responsible for developing the user stories and generating the product
backlog as a user requirement file
Will identify the relevant stakeholders and evaluate their influence for the
purposes of developing an effective communication plan
Maintains a cordial working relationship with the project sponsors to

PROJECT PLAN FOR THE DEVELOPMENT OF THE OSFMS 5
ensure continued support and successful project delivery through an
effective communication plan
Help with technical work in developing the system, specifically mobile
system
Responsible for testing the system to ensure it meets the user requirements
and determines when improvements are to be made
Responsible for keeping the team members motivated and ensure each
person takes ownership of their roles
Seeks approvals for changes during scope change initiatives
Integration of the system and continuous product testing to ensure it works
flawlessly with other systems ('Bisk', 2018)
SCRUM
Master
Planning for and managing team meetings
Taking minutes for the meetings, documenting and synthesizing them, and
sharing it with team members
Will also be a technical person in systems development to help with
debugging of system during iterative development
Responsible for demonstrating leadership and control during team
meetings
Conflict resolution during project execution
Risk management; the SCRUM master will be in charge of managing the
project risks and the risk management plan
Managing all project documents accordingly
Removing all obstacles that may otherwise affect the project adversely,
and working with the product owner (project manager) to ensure the
product backlog is being expedited accordingly
Preparing the platform for managing the project and updating it, such as
using an online project management portal/system (Viscardi, 2013, p. 17)
Database
Developer
Design the database
Create cloud instance to ensure redundancy of the system
Develop security and access protocols for the database
Link database with other systems, including the financial management
system
Data migration to the new system ('Bisk', 2018)
Web Design the web based user interface

PROJECT PLAN FOR THE DEVELOPMENT OF THE OSFMS 6
application
developer Create necessary applets for interaction with the site
Develop front and back end for the system
Integrate system with all others (Kyrnin, 2009)
4. Team Communications
Communicatio
n Type
Frequency /
Time
Location eMails and Document Storage
location
In person, face
to face, audio
conference,
video
conference
Define how the team will
communicate with each other and
share information. Also specify how
meetings will be documented and
where subsequent resources will be
stored for ease of access.
Face to face
communication
when assigning
roles,
discussing
project
requirements
Weekly (once) Project office Meeting meetings paper, with
scanned copies into PDF
Stored in project physical file and in
the project management portal as well
as in e-mails
User
requirements
capture
Daily (3 days
total)
Globex (client
premises)
Project file
E-mail
Online project management portal
Reporting
progress to
stakeholder/
Fortnightly Executive
sponsor
Written memo and report stored in
project file

PROJECT PLAN FOR THE DEVELOPMENT OF THE OSFMS 7
seeking
changes
premise
E-mail
Online project management system
Daily Sprint
meetings
Daily Project office/
online project
management
portal
E-mal
Online project management portal
Meeting minutes stored in project file
Testing Weekly Project Office Project management file
E-mails
Online project management portal
5. Team Rules & Expectations
Individual Work
Past Experiences
I have participated in projects before and while those experiences were
educational and enriching, I am playing the role of project manager for the
first time. In the past, the rules and decisions were solely made by the project
manager; having learned about project leadership, this project has taught me a
lot about servant leadership and I have duly applied the leadership principles.
Compared to past projects, I find this very well organized, structured, and
formal, with a defined framework for achieving project goals. I will continue
to apply leadership skills learned in the past and in class in this project by
encouraging participation
Team Work
Team Values

PROJECT PLAN FOR THE DEVELOPMENT OF THE OSFMS 8
o People driven with every member deserving respect
o Cooperation and unity of purpose (team work)
o Integrity and honesty
o Constant learning and growth
o Client focused, with quality a major priority
o Visionary ad doing the best to achieve project objectives
o Commitment to the cause
o Working based on the big picture
Code of Ethics
o Absolute honesty and integrity
o Trustworthiness through honesty, integrity, reliability, and loyalty
o Responsibility through pursuit of excellence, accountability, and self-restraint
o Caring through showing concern for others and being mindful of how they are
affected by one’s actions
o Fairness through impartiality, procedural fairness, and equity
o Respect through individual dignity, courtesy, and tolerance, based on
recommendations by Schweriner (2007)
Rules and Expectations
o All team members must attend at least 85% of all the scheduled meetings,
including daily meetings
o All team members must contribute to the project effort to the best of their
ability
o All team members deserve a chance to give their views and ideas
o All team members must report any problems they are facing during daily
meetings and all team members propose solutions
o Each team member must give an individual daily and weekly progress report
o During testing, all team members must be present and contribute ideas
o Any identified issues with the system must be resolved before proceeding to
the next sprint
o All team members must give accurate and verifiable status reports

PROJECT PLAN FOR THE DEVELOPMENT OF THE OSFMS 9
o Each team member must update the dashboard through the online project
management portal
o Any conflicts must be reported to the scrum master if cannot be solved
amicably and resolutions reached must be followed
o All team members take collective responsibility for success or failure of the
project
Based on suggestions of Stuart (2014)
 Signatures – Insert the electronic signature of all the team members here. This will
indicate an understanding and agreement to the rules and expectations as specified in
the points above.
______________________
________________
______________________
________________
______________________
________________
______________________
________________ Signature
Date
Part Two:
1. Learning Cycles –

PROJECT PLAN FOR THE DEVELOPMENT OF THE OSFMS 10
Role Date/Time&
Attendees
Organiser
( NAME , Project
manager/ product owner
)
12 March
2018 week
Scribe
( NAME , SCRUM master
Outcome of the meeting:
Meeting to discuss and assign each team member roles and define what is expected of each
member. Roles were assigned as shown in section One. The team developed and agreed on
the team values and agreed to abide by them. The project charter was developed
Meeting 2
Role Date/Time&
Attendees
Organiser
(NAME, Project manager )
26 March 2018
week
Scribe
(NAME, Database Developer
)
Outcome of the meeting: The team discussed the user stories as documented by the product
owner and jointly developed the product backlog. The team also discussed and agreed on the
time framework for the project and also developed the project team rules and regulations as
well as ethical standards (rules of engagement). The team decided on the tools to use in
managing the project, including the online collaboration software, frequency of daily sprint
meetings, and how meetings will be conducted as well as conflict resolution mechanisms.
Team developed the sprint backlog, the project schedule, Gantt chart, and WBS
Meeting 3
Role Date/Time&

PROJECT PLAN FOR THE DEVELOPMENT OF THE OSFMS 11
Attendees
Organizer
(NAME, Scrum master )
02 April 2018 week
Eg. Wednesday, 4
April 2018Scribe
(NAME, Project manager )
Outcome of the meeting:
The team developed a mockup and diagrams of how the system will work (developed a joint
system architecture)
Team decided on the specific languages to use and the exact versions
Team decided on the project budget based on its architecture and refined the product backlog
Team determined the required documentation for the project and how the documents will be
managed as well as the person(s) responsible
2. Team Learning
What we know
(Facts)
What we think we know
(Assumptions)
What we don’t know
(Questions to be Answered)
The kind of system that
Globex needs
How the system will work
and integrate with other
systems
How the system will perform
under different loads
The need for an effective risk
management plan and
strategy
The risk management plan
will ensure the project
objectives are met within
time and budget
How effective the risk
management mitigation and
contingency plans will be
Each team member has a
specified role
Team members will deliver
their tasks as expected and
within time and scope
The exact performance of
each team member relative to
their individual roles and
overall project requirements
Budget developed and
stakeholders identified
The budget and stakeholder
management plan will ensure
successful project completion
If there will be forced scope
changes that affect budget
Continued support by
sponsors