+1(978)310-4246 credencewriters@gmail.com
  

Description

Felix
According to Case Study GG Freightways (GGFRT), University of
Maryland Global Campus (2021) shared that one of GGFRT’s strategic
objectives is to refine the loaded miles percentage in their fleet
through collaborating and communicating effectively with the delivery
and pick up department in the same position (University of Maryland
Global Campus, 2021).
Within an article named What is agile methodology? Modern software
development explained, Sacolick (2020) shared that the Agile Software
Development approach typically utilizes continuous collaboration and
planning to develop software (Sacolick, 2020). Likewise, according to
the article called named Agile Software Development, Brush (2019)
shared that the Agile model allows a group to swiftly work in teams to
complete a task by dividing it into parts (Brush, 2019). Also, the Agile
Software Development Model helps a team quickly monitor for issues
that get foreseen along the way. Overall, the Agile approach has a team
value interaction throughout the project (Sacolick, 2020).
Advantages & Disadvantages of using the Agile (ASD) model
Agile Software Development is a model that a group follows when they
value to improve by studying feedback (Sacolick, 2020). This means
that the ASD model encourages communication amongst a team with
the intention of “boosting productivity” as well (Sacolick, 2020). As a
result, an Agile methodology is the model that I think would greatly
suit GGFRT. For instance, the ASD model encourages collaboration in a
group and offers a healthy second opinion for workers (Brush, 2019). In
GGFRT’s case, the ASD model would allow the delivery and pickup
department to collaborate more and improve their communication as
well. Doing so will likely help GGFRT meet their objective of refining the
loaded miles percentage in their fleet through collaborating and
communicating effectively with the delivery and pick up department in
the same position (University of Maryland Global Campus, 2021).
Despite, the benefits of following the Agile Software Development
model there are a few potential obstacles that GGFRT may face along
the way. For instance, within an article called The Massive Downside of
Agile Software Development, Fridman (2016) shared that an Agile
Software Development model-inspired approach could prove as quite
time consuming due to an increase in collaboration (Fridman, 2016). As
a result, potentially one obstacle GGFRT faces is a possibility of failing
to finish on time. This means that under an Agile model, GGFRT could
face working overtime frequently (Fridman, 2016). Additionally, an ASD
model approach would require more training for staff members
(Fridman, 2016). With this in mind, GGFRT may struggle to find a
suitable/affordable training program for GGFRT team members in a
timely fashion (Fridman, 2016).
John haywood
I believe that the Development & Operations or “DevOps” model
would work best for GGFRT. According to Helical IT Solutions Pvt Lrd.,
“DevOps means a software development method which stresses on
communication, collaboration and cooperation between software
developers and other IT professionals.” (What Is DevOps in SDLC, 2019)
In other words, it is a flexible SDLC model that utilizes communication
throughout the process to deliver the best desired result, or product.
According to King, DevOps employs the best of other effective SDLC
models, such as Lean and Agile. (King, 2021) DevOps has many of the
strengths of other SDLC models without the typical problems they
face.
In the case of GGFRT’s strategic objectives, the third objective was
“provide warehousing services for customers who want to reduce
delivery time to their customers or company by having product
available locally for pickup in warehouses or quicker local delivery.”
(UMGC, 2021) Facilitating this capability will be new to GGFRT and will
require additional software features incorporated into the SaaS of their
choice. King again states that DevOps has been proven to provide
continuous software delivery, is less complex in fixing problems and
problems are resolved faster. There is also the added benefit on the
strictly business side with DevOps that include faster delivery of
features which greatly helps GGFRT provide this new service, has more
stable operating environments and allows more time to add value.
(King, 2021) GGFRT will need all of these features incorporating the
warehousing function for customers. For starters, continuous software
delivery allows GGFRT to improve iteratively based on customer
feedback. Problems being less complex to fix obviously means faster
resolution. Again, on the business side, customers will want and
appreciate faster delivery of features, especially if they’re based on
customer feedback. A more stable operating environment benefits
GGFRT and the customer by ready availability and optimal operating
conditions. All of this allows more time for GGFRT to utilize CPI,
(continuous process improvement.)
The challenges for incorporating DevOps into the GGFRT construct are
the same as any SDLC model and for that matter, any new business
plan. First, as the ITSP Lance created begins to go into effect one
problem is automatically user acceptance. Employees may not like any
of what’s going on or about to happen and may either quit or create
problems from within. Second, DevOps encourages cross-functional
organizations to share responsibilities across the SDLC phases
conducted in parallel. (Raza, 2020) So if departments or organizations
have limiting factors in this communication, or don’t have a good
relationship then it presents a challenge to the DevOps model’s
functional success. Now, the typical SDLC problems include 1- not
using key performance indicators to track cycles. 2- software processes
in development can have a few difference hands creating it so
standardization could be an issue. & 3- proper IT governance and CPI.
(King, 2021) Specifically for GGFRT this means employees might not
want it and customers might not either. Or, something new might just
be rejected. Hopefully if this happens its only a growing pain period
and is quickly overcome. In the case of providing warehousing there
needs to be on point scheduling with pickups, drop-offs and 24 hour
availability for the customers and even their customers. This will require
integration and automation within whatever system is adopted
(hopefully as a service, i.e. SaaS). Dispatchers, schedulers, developers
and software engineers and programmers will need to sit down and
create a comprehensive requirements list for this strategic objective to
be written into the system. It should include at a minumum;
•
•
•
•
•
•
The system must be available 24 hours a day
The system must be accessible by mobile platform/website
The system must be viewable from truck visual systems
dashboard (again, hopefully included in GGFRT’s tech upgrade
and yes, this means it has to comply with single touch access by
DOT)
The system must automatically deconflict requested times based
on terminal capability (number of available bays/ramps)
The system must be pre-programmed with the type of storage
required for drop-off (i.e. regular freight, flatbed or cargo,
refrigerated or regular)
The system must be pre-programmed with the type of
transportation required for pickup (i.e. regular freight, flatbed or
cargo, refrigerated or regular)
The way for GGFRT to overcome these challenges is for Lance to really
communicate well and drive the organization with confidence. He
needs to develop his leaders and managers to own their processes and
teach them. They in turn, need to do the same with their departments
and/or teams. Also, having a good SaaS to keep it all in-line with the
developers and operations techs to use, modify and
incorporate/integrate systems with immerging technologies as part of
CPI will keep GGFRT on the up and prepared for expansion quickly.
Its also worth mentioning that the COBIT 2019 platform has embedded
SDLC methodology within its framework that includes DevOps. (Raza,
2021)
Heather olson
The recommended SDLC model for GGFT would depend on the project.
Smaller projects could benefit from the Waterfall model which relies on
a specific sequence of steps that flows in one direction and does not
have the flexibility to reverse course and go back to previous stages
(“How To Create a Process For Your Development Team to Follow,”
2020). An Agile model would likely work best for larger projects
because it breaks the project down into smaller pieces and testing is
performed at each iteration (6 Basic SDLC Methodologies, 2021).
One of the projects GGFRT is likely to implement soon is the
development of the freight tracking feature of the Route Optimization /
Freight Tracking System. This project will have an impact on all three
current business strategies of GGFRT and an Agile method would be
the recommended model for the project. The suggestion would be to
break the project down into smaller cycles. As a high-level example:
1. Enable functionality to support tracking of the freight in the
warehouse.
2. Enable functionality to support tracking on the trucks
3. Utilize the functionality in cycle 2 to calculate utilization and
integration with the fleet management system.
Breaking the project down into smaller segments will allow GGFRT to
start supporting different strategic objectives. In the example, once the
first two cycles are complete, GGFRT would have the visibility into the
location of freight in the warehouse and on the trucks, and ultimately
being able to provide the accurate real-time information to their
customers. Using an Agile method, each cycle incrementally builds on
the last and is tested. Therefore, each subsequent phase of the Freight
Tracking development would provide additional functionality needed
to support the remaining strategic objectives. This would allow the
team to find any problems before they become larger issues (6 Basic
SDLC Methodologies, 2021). If the Waterfall method was used for the
project, testing would not occur until all development is complete; if
something were to then go wrong with testing, the project could be in
trouble. Use of an Agile method does pose its own challenges. One
challenge is that because the pace is quick and less rigid, it may be
difficult to accurately capture costs and determine the true cost the
project(“How To Create a Process For Your Development Team to
Follow,” 2020). Additionally, the GGFRT team may not have experience
with Agile methods, do not understand the process (Agile Problems,
Challenges, & Failures, n.d.) which could cause resistance to the
method’s processes. In this case, a hybrid agile approach, optimized
for the GGFRT team, could be developed.
Each project GGFRT undertakes should be evaluated to determine
which model makes the most sense. There are more models than just
Agile and Waterfall, and the answer may be any one of the models, or
even a hybrid of two models if needed. The ultimate answer will be
that the model will be one that works for both the project and for
GGFRT.
References:
Many of you have said that you have learned many new concepts
during this class. I would like for each of you to think back over the
class and then share with us one new concept which you feel was
important to you. It could be something that spurred your interest,
something you never heard of or did before, something you struggled
with, etc. The content of this course was modified effective this
semester, so your feedback is important to us.

Purchase answer to see full
attachment

  
error: Content is protected !!