INFS703 - Global System Development Plan for Fonterra Project Mgmt

This report presents a global systems development plan for Fonterra, a global dairy nutrition company. It explores various system development approaches, including SDLC, RAD, and prototyping, to determine the most suitable approach for developing a global information system. The report compares Rapid Application Design (RAD) and System Development Life Cycle (SDLC) methodologies, recommending SDLC due to its structured framework and thorough testing capabilities. Furthermore, it analyzes project management methodologies like Soft System Methodology (SSM) and Agile Development Methodology, ultimately advocating for Agile due to its iterative nature and adaptability to changing requirements. The rationale for not selecting alternative methodologies, such as SARDIS, SSADM, UCD, JSD, and IEM, is also discussed, highlighting the advantages of Agile in addressing project challenges and ensuring successful system development for Fonterra's global operations.

Running head: PROJECT MANAGEMENT.
A Global Systems Development Plan for Fonterra
Name of the Student
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Part 1: Approaches for Global system development at Fonterra
1.1 Introduction
The paper mainly focuses on the organization "Fonterra" which is one of the global
dairy nutrition company (Verzuh, 2015). It is found that to expand its business and for
reaching to more number of customers, the organization requires a global information system.
It is identified that to develop the information system, the number of development approaches
like SDLC, RAD, as well as prototyping, are discussed so that appropriate development
approach can be selected for the development of the information system.
1.2 System development approaches
It is found that to develop the global system for the organization "Fonterra", it is very
much necessary to select proper system development methodology so that planning as well as
controlling the procedure of information system development can be done quite effectively
(Kerzner & Kerzner2017). For that reason, three different types of system development
approaches are discussed so that the best approach can be utilized during the development of
the information system for the organization .
1.3 Description of the approaches and comparison between them
The approaches to system development are generally discussed below:
Rapid application design (RAD): It is one of the development methodologies that
help in providing advanced development tools, prebuilt as well as the graphical user interface
as well as object-oriented related techniques (Joslin and Muller2015). The main key is to
target steps which can be overlapped and performed with the help of the multiple teams
(kerzner, 2018). It is very much useful system development approach as it assists in quickly
producing the number of applications. In addition to this, it is found that this approach is

2
PROJECT MANAGEMENT
mainly suitable within the projects in which the functionality of the system is clearly visible
where the project should be of medium-scale and of short duration (Jeston, 2014).
System development life cycle (SDLC): System development life cycle is one of the
domains of competency that it is mainly utilized for the development of information system
as well as software engineering for describing the procedure of planning, testing, creating as
well as deploying the entire information system successfully (Sanchez, 2015). It is found that
the SDLC approach basically has three paradigms including linear approach, iterative
approach as well as component-based software development approach.
The comparison between the RAD and SDLC approaches are generally elaborated
below:
Factors Rapid application design
(RAD)
System development life cycle
(SDLC)
Definition It is defined a one of the
development methodologies that
is mainly dependent on various
advanced development tools
including interfaces builder, code
generator as well as on various
types of object-oriented
techniques (Chih & Zwikael
2015).
It is one of the conceptual
models that is mainly used within
project management for
describing the various stages as
well as tasks that are mainly
involved in each task of the
project.
Advantages The advantages of RAD are
generally elaborated below:
 It assists in providing a
The advantages of SDLC
approach are listed below:
 SDLC approach is very much

3
PROJECT MANAGEMENT
constricted fit between the
requirements of the user
swell as the specification of
the user (Marchewka, 2014).
It mainly helps in providing the
proper ability to change the
system quite rapidly as per the
user's demand (Mathur, Jugdev,
& Shing Fung, 2014).
 This approach is considered
o be advantageous as it
generally helps in saving
time, cost as well as human
effort (Leach, 2014).
simple to use and understand.
 Testing is done after the
execution phase for checking
whether the development of
the project is done properly
or not.
 The progress of the entire
project is measurable (Papke-
Shieldsand, 2017).
 The project generally have
clear requirements as well as
project objectives
Disadvantages The disadvantages of RAD are
listed below:
 It generally delivers the poor
quality of the system due to
the enhanced speed during
the project development
phase.
 It generally can cause
inconsistent system design
 It generally can cause the
number of difficulties within
the module usability for the
The disadvantages that are
mainly related to SDLC approach
are listed below:
 This approach is very much
time consuming, and thus the
project will take much time.
 With the help of this
approach, it is very much
difficult to make changes
within the approach
 It generally has very much

4
PROJECT MANAGEMENT
system that are required to be
developed within the future
(Badewi, 2016).
little space for iteration
1.4 Reason of selection with the recommendation
It is found that the use of SDLC development approach for the development of an
information system within the organization "Fonterra" is considered to be advantageous. It is
identified that the use of SDLC approach assets in providing a common framework so that
the information system for the organization can be developed quite successfully. It generally
assists in identifying he requirement of the project in the initial phase and then finishes each
of the activities of the project so that the objectives that are associated with the project can be
achieved (Conforto et al., 2014). Moreover, it is found that testing is done after the execution
phase for checking whether the development of the project is done properly or not. Thus, due
to the advantages that the SDLC approach provides to the project, this approach is
recommended to be suitable for the development of the information system (Marcelino-
Sádaba et al., 2014).
1.5 Reason for not selecting other approaches
The reasons are elaborated below:
RAD: it is found that this approach is not selected for the project due to the reasons
which are generally listed below:
 It is appropriate for the projects that are generally smaller in size
 When this approach is used, the technical risks of the project is high and therefore
this approach is not used within this project (Sanchez, 2015).

5
PROJECT MANAGEMENT
 It generally reduces the scalability, and it is quite difficult to track problem when
this approach is applied within the project.
Prototyping: It is found that his approach is not used within the project due to the
reasons that are generally elaborated below:
 It generally creates confusion for the user, and thus, in this project, it is not used
 The developers of the information system can face difficulties in understanding the
objectives of the developer (Kumar and Ranjan2017).
 The time that is required for the development of the project is quite more, and thus
this approach is avoided being used (Braglia & Frosolini, 2014).
Part 2: Methodologies for Global system development at Fonterra
It is found that to develop the global information system for the organization
"Fonterra," the number of project management methodologies like SARDIS, SSADM,
UCD, , JSD, IEM as well as agile are analyzed to identify the best project management
methodology for the project (Nicholas & Steyn, 2017). Thus, to identify the best
methodology, the project management development methodologies are compared so that
most suitable methodology for the development of the global information system can be
identified.
2.1 Description of two project management methodology and comparison between them
The description of the project management methodologies are mainly elaborated
below:
Soft system methodology: It is found that it is one of the approaches for the
organizational process modeling that is mainly utilized to resolve the problems as well as
issues that are associated with the management of change. This methodology is used in the

6
PROJECT MANAGEMENT
seven-step process to develop the system (Fleming & Koppelman, 2016). It is found that it
assists in providing a structure when there is a complex situation while undertaking the
project.
Agile development methodology: It is found that agile development methodology is
mainly defined as one of the practices that generally assist in promoting continuous iteration
off testing as well as development throughout the software development lifecycle (Benzaken
et al., 2017). It is found that in agile project methodology, the entire procedure is broken into
the number of models so that the project developer or designer can complete the work quite
successfully .
It is found that comparison between the SSM as well as agile development
methodology is generally provided in the table that is generally provided below:
Factors Soft system methodology Agile methodology
Definition It is considered as one of the
significant tools that are mainly
utilized within the system
research.
Agile project methodology is
considered one of the practices of
continuous iteration for testing as
well as the development of the
information system within the
project lifecycle.
Advantages The advantages that are mainly
associated with this methodology
are mainly elaborated below:
 It generally assists in
providing proper structure for
the complex organizational
The advantages that agile project
methodology provides are
generally elaborated below:
 It generally provides proper
attention to the technical desi

7
PROJECT MANAGEMENT
issues so that the problems
and challenges can get
resolved quite effectively
(Joslin. & Muller2015).
 It generally allows the user to
deal with them in an
organized manner.
of the project (Leach, 2014).
 Even late change within the
project requirement can be
done when this development
methodology is used within
the project
 The customer can get
satisfied with the system that
is developed by this
methodology (Galvan, Mora,
Connor, Acosta, & Alvarez,
2015) .It is found that in agile
project methodology, the
entire procedure is broken
into some models so that the
project developer or designer
can complete the work quite
successfully
Disadvantages The disadvantages that are
associated with SSD
methodology are elaborated
below:
 The fourth stage of this
methodology, does not have
the proper modeling tool
 If the workers are not
experienced, the it is quite
The disadvantages that are
mainly associated with agile
development approach are
provided below:
 Lack of proper emphasis on
the documentation as well as
designing
 The project can get out of
track if the project

8
PROJECT MANAGEMENT
difficult to come up with a
proper solution
representatives do not have
clear project idea (Sánchez,
2015).
2.2 Selection of one project management methodology
It is found that the utility of agile development methodology is quite suitable for the
development of a global information system for the organization "Fonterra." (Todorović,
Petrović, Mihić, Obradović, & Bushuyev, 2015)
It is found that agile project management methodology is mainly used within the project as it
is one of the iterative as well as the incremental approach of software design that generally
broken the individual's models into the number of processes so that the work of the project
can be finished quite effectively (Kerzner & Kerzner 2017).In addition to this, the most
important reason for using agile development methodology is that the use of this
methodology assists in providing the opportunity to resolve the problems as well as errors
that are associated with the project within the middle of the project. It is found that due to the
advantages that an agile project development methodology provides it is recommended to be
best suitable for the development of the information system for the organization "Fonterra."
2.3 Explanation for not selecting the other methodologies
It is found that other project development methodologies are not used within the
projects d to the problems that they possess during the development of the project. It is found
that after analysis of all the project development methodology, it is analyzed that the
methodologies like SARDIS, SSADM, UCD, JSD, IEM are not useful for the development of
global information system within the organization Fonterra (Kerzner, 2017).

9
PROJECT MANAGEMENT
It can be concluded that agile project development methodology for the development
of the global information system for the organization "Fonterra" is suitable (Mir &
Pinnington, 2014). It is found that by using this methodology, the entire work is broken into
the number of models so that the project developer or designer can complete the work quite
successfully. It is identified that other methodologies like methodologies like SARDIS,
SSADM, UCD, JSD, and IEM are not useful for the development of the global information
system within the organization Fonterra (Heldman,2018). Thus, after analyzing all the
methodology, agile development methodology is considered to be quite suitable for the
development of the information system for the organization.
Part 3: Ethics-based risk assessment
The stakeholders of the project are categorized into primary stakeholders as well as
secondary stakeholders.
Primary stakeholders: The primary stakeholders who are involved with the project
directors are listed below:
 Project manager
 Project planner
 IT manager
 Human resource manager
 Financial manager
 IT analyst
 Database manager
Secondary stakeholders: the secondary stakeholders who are indirectly associated
with the project are listed below:

10
PROJECT MANAGEMENT
 Suppliers
 Investors
 Government
The ethics-based risk assessment is undertaken within the table that is provided
below:
Risk Description Impact Probability Responsible Mitigation
Cybersecurity
risks
It is found
that the
number of
cybersecurity-
related issues
and
challenges
occurs within
the project if
the
information
system project
that is
generally
undertaken is
not properly
used.
High High IT analyst It is found that
to resolve the
issues and
challenges; it
is quite
necessary to
use firewall so
that
unauthorized
access can be
avoided and
the problem of
cybersecurity
issues can be
reduced.
Use of
improper
It is found
that if the
materials that
are used
High High Quality It is very
much

11
PROJECT MANAGEMENT
materials within the
project are
inappropriate
in quality and
as a result, it
can cause of
quality related
issues and
challenges
within the
project
(hornstein,201
5)
analyst necessary to
use the proper
quality of
materials
within the
project to
avoid quality
related issues
and
challenges. I
addition to
this, it is very
much
necessary to
test the quality
of the
materials to
avoid such
types of
problems.
Improper
gathering of
information
If the
information
that is
gathered for
the project is
not
appropriate,
Medium High Project
planner
It is quite
necessary to
gather the
information as
well as
requirements
related to the

12
PROJECT MANAGEMENT
then it is quite
necessary to
finish the
entire project
within the
expected time
and budget.
project quite
appropriately
so that the
entire project
can be
completed
within the
expected time
and budget.

13
PROJECT MANAGEMENT
References
Braglia, M., & Frosolini, M. (2014). An integrated approach to implement project
management information systems within the extended enterprise. International
Journal of Project Management, 32(1), 18-29.
Fleming, Q. W., & Koppelman, J. M. (2016, December). Earned value project management.
Project Management Institute.
Galvan, S., Mora, M., O’Connor, R. V., Acosta, F., & Alvarez, F. (2015). A compliance
analysis of agile methodologies with the ISO/IEC 29110 project management
process. Procedia Computer Science, 64, 188-195.
Heldman, K. (2018). PMP: project management professional exam study guide. John Wiley
& Sons.
Hornstein, H. A. (2015). The integration of project management and organizational change
management is now a necessity. International Journal of Project Management, 33(2),
291-298.
Jeston, J. (2014). Business process management. Routledge.
Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring
and monitoring project performance. John Wiley & Sons.
Kerzner, H. (2018). Project management best practices: Achieving global excellence. John
Wiley & Sons.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.

14
PROJECT MANAGEMENT
Leach, L. P. (2014). Critical chain project management. Artech House.
Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A. M. E., & Villanueva, P. (2014).
Project risk management methodology for small firms. International journal of
project management, 32(2), 327-340.
Marchewka, J. T. (2014). Information technology project management. John Wiley & Sons.
Mathur, G., Jugdev, K., & Shing Fung, T. (2014). The relationship between project
management process characteristics and performance outcomes. Management
Research Review, 37(11), 9
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.
Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business and
technology. Routledge.
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.
Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.