Harvest City's Intelligent Procurement

10/5/2022 System Analysis Report:

Student's Name: Darrell Scott

Institution: Southern New Hampshire University

REPORT
 Table of Content:

Overview 2
Analysis Report for Harvest City Project: 5
Summary: 5
Constraints and Opportunities: 5
Decision-Making Processes: 5
Scalability, Cost, and Time: 5
Documentation and Tracking 6
Recommendation 6
Recommendation for Decision-Making Process 6
Recommendation for Scalability, Cost, and Time 7
Importance of Documenting and Tracking Procedure 7

References 7

Overview:
1
Competency:

In this project, you will demonstrate your mastery of the following competencies:

 Analyze constraints and opportunities of an organization that impact systems decisions

 Analyze a current system to identify solutions to computing problems.

Scenario:

You are working for the IT department of Garnet Gardens Hotels, a small hotel chain in the mid-west
region of the United States. Because of a recent boom in business coming to the area, hotel
management is looking to become a competitive player in the region’s hospitality industry. Stakeholders
are hoping to target a professional clientele and the effort to increase revenue. However, the
actualization of such a plan would mean careful thought and consideration of guest amenities.

Your manager has approached you about a system upgrade that would focus on meeting the needs of
this increased traffic. The hotel’s targeted guest audience is business travelers who need high-speed
access, technological support, and flexible on-demand services, as well as a comfortable place to stay.

The chief information officer (CIO) of the company has asked your department to analyze the case study
for the intelligent procurement system project of Harvest City, linked in the Supporting Materials
section, as a comparative means to ensure due diligence for the stakeholders of this project. Your
analysis report will serve to benchmark and identify known unknowns that could potentially impact
project success. Stakeholders want to avoid the mistakes of the Harvest City convention complex. Your
analysis report will provide useful information to stakeholders regarding the pros of the system.

Directions:

You have been asked to analyze the case study, “Harvest City: The Intelligent Procurement System
Project,” and create an analysis report to present to the stakeholders. Using these directions, and based
on the results of your analysis, you will prepare a concise summary and recommendations.

Here are some points to consider as you analyze the case study:

2
  Factors (constraints and opportunities) that impacted the overall system development in the
case study. Consider:
o Strategy
o Communication
o Planning
o Governance
 Stakeholder needs that impacted the initial design of the system. Consider:
o Scalability
o Cost
o Time
 Potential risks of the project
 Formal decision-making of the organizational parameters of the project design
 Tracking and documentation. Consider:
o Procedures
o Changes
o Issues

Summary and Recommendations:

Using the information gathered through your analysis of the case study, you will create an analysis
report for your stakeholders. Within the summary section of the report, you must summarize the TRS
listed below about within the recommendations section of the report, you must make recommendations
and provide evidence to support them, using APA citations.

Summary:

 Explain how constraints and opportunities impacted system implementation.

 Describe the decision-making used by stakeholders in the case study and how those decisions
impacted system design, implementation, and governance.
 Explain how the needs of the stakeholders influenced the design and implementation of the
system in terms of scalability, cost, and time.
 Describe issues and events that occurred in the case study due to the lack of
effective documentation and tracking.

Recommendations:

 Describe the organizational strategy you would propose and how it would be used to avoid the
negative results of the Harvest City project.
 Recommend decision–making decision rulemaking old use to facilitate effective system
implementation. (Graphical representations are often useful supplements use in describing use
decision processes.)
 Recommend the measures you would take to meet the needs of the stakeholders, while still
considering the scalability, cost, and time requirements.
 Explain the importance of documenting and tracking procedures, changes, and issues that arise
during system implementation and how recording this information can reduce the impact of
known risks.

3
What to Submit:

To complete this project, you must submit the following:

Analysis Report:

You will create a 3- to 5-page analysis report about the intelligent procurement system project of
Harvest City, including a summary and recommendations to present to the stakeholders. It is beneficial
to get into the practice of creating reports that are high quality, organized, and ready to present to
project stakeholders so, while not required, you may want to copy and paste the content below and use
it as a table of contents for your analysis report .

Analysis Report:

1. Summary:
1.1 Constraints and Opportunities
1.2 Decision-Making Processes
1. 3 Scalability, Cost, and Time
1. 4 Documentation and Tracking
2. Recommendations:
2.1 Proposed Organizational Strategy
2.2 Recommendations for Decision Making Process
2.3 Recommendations for Scalability, Cost, and Time
2.4 Importance of Documenting and Tracking Procedures

4
 Analysis Report for Harvest City Project:

Summary:
Constraints and Opportunities:
Constraints are the limiting factors that affect the deliverability of a project, while opportunities are
actions that have a positive impact on the project. The Harvest town executives saw a chance to contour
all the intelligent systems within the advanced rather than having completely different systems for
various tenants, which can have created the customer’s expertise effortful to use numerous systems
across the advanced. However, Harvest town executives failed to think {about contemplate| and take into
account} what the tenants wanted; they failed to consult the tenants about their necessities (Applegate
& Montealegre, 2018), serving to Venso perceive the precise wants of specific tenants and the way
they'd implement the various wants of the assorted tenants. The constraints affected and slowed down
the implementation of the system, making the project last longer and cost more than it was projected to
cost.

Decision-Making Processes:
The stakeholders made decisions that they thought were the best for them without consulting all the
parties involved. The stakeholders did not ask the tenants if they needed an intelligent system or their
requirements and what they needed for their spaces (Applegate & Montealegre, 2018). The tenants
were not consulted on whether they preferred to install their smart system or were comfortable letting
the complex install the intelligent systems for the tenants. The stakeholders made decisions without
consulting other shareholders for their opinion. Not consulting tenants on their project requirements
caused the project scope and requirements to change from time to time. According to On Cloud, the
company that audited the intelligent system blamed the system’s complexity on the changing needs of
the various tenants (Applegate & Montealegre, 2018). The decisions made delayed the implementation
of the system design because of different tenants’ changing needs and requirements. The stakeholders
made decisions without consulting and informing the shareholders of any changes made.

Scalability, Cost, and Time:

The needs of the stakeholders kept changing and giving little time to Venso to implement the change
affecting the scalability, cost, and time of the project. Harvest City executives constantly changed the
requirements, and they did not listen to Venso’s complaints about the changing needs; they ignored
Venso and did nothing to make Venso’s work easier (Applegate & Montealegre, 2018). The stakeholders’
needs changed frequently, and Venso tried to keep up with the changes ensuring they completed the
project on time. The project was complex, and the changing needs did not make it easier for Venso to
implement the system. Midway through the project a tenant wanted the system to be changed,
increasing the cost and the time for the implementation. The stakeholders’ changing needs made the
system complex, not accommodating the needed scalability due to the changing customer needs.

5
Documentation and Tracking:
Lack of adequate documentation and tracking affected the result of the project affecting the launching
time for the whole Harvest City project. The stakeholders did not document and track the effects would
be when the vendors of the intelligent building management systems tapped into Venso’s sensor
system. The stakeholders did not document the change informing Venso of the shift, enabling Venso to
check if there would be any effect. This affected the conference that was planned weeks before the
launch, where Venso’s sensors misbehaved and sounded the alarm, opened the sprinklers, and signaled
the emergency services there was an emergency when there was no fire (Applegate & Montealegre,
2018). If the changes had been documented, Venso would have had the opportunity to assess the risks
of another vendor tapping into the sensory system and avoiding the damage that happened.

Recommendations:
Proposed Organizational Strategy An organization strategy is essential in a project to make it a success
to avoid going over the budget and using more time than required. An effective organizational strategy
will help align the team on the project’s requirements and help them understand their roles and the
mission and vision of the project (Kerzner, 2019). An effective corporate strategy will help avoid
changing the project scope and conditions, constantly delaying the project, and going beyond the
budget (Kerzner, 2019). Using project management software is essential to track the progress and know
who is responsible for the project. Project management software enables the team to track progress in
real time, and allows effective project collaboration and effective task allocation (Kerzner, 2019).
Creating a project plan and schedule will help the team understand the project’s specifics and the
budget and time frame of the project. Defining priorities is essential to ensure the team does not spend
time on less critical tasks that may affect the time and budget of the project. Effective communication
ensures that all the needs are understood and that the developers do what the client expects. This
would avoid making changes in the middle of the project, which is costly for both parties.

Recommendations for Decision-Making Process:

In the classical decision-making approach where the first step is identifying the problem that the project
has to solve. Here the project team identifies the problem and understands it well to facilitate a
successful process (Beach & Lipshitz, 2017). The next step is identifying the alternatives to solving the
identified problem. A wide range of other options should be determined to help choose the best option
for the problem. The next step is to evaluate all the alternatives identified and check if the choice is the
best for the project. The team would then decide the option that is best suited for the problem. A SWOT
analysis will help identify if the alternative is the best decision for the project (Beach & Lipshitz, 2017).
The last step is implementing the option according to the project plan, budget, scope, and constraints.
For this decision-making process to be effective, the team should include all the shareholders affected
by the solution to ensure that their needs are heard and considered in the project design and
implementation.

Recommendations for Scalability, Cost, and Time:

The measures that I would take to meet the needs of the stakeholders while still maintaining scalability,
costs, and time requirements include involving all the stakeholders involved at all stages of the designing
and implementation process. Constant communication with the stakeholders would help get feedback
about the designing and implementation process, reducing the chances of making changes that would

6
make the design and implementation of the project begin or stall (Alaidaros & Omar, 2017). Risk
assessment is essential for identifying any risk users may encounter when using a system, avoiding the
extra costs of solving a risk when the system is already in use.

Importance of Documenting and Tracking Procedures:

The important documentation and tracking procedures help to identify a risk solve the risk before the
system is used, and avoid unnecessary interruptions during the use of the system. Documentation is
essential in checking if all the system requirements are met and if they work exactly how the client
wanted the system to work (Behutiye et al. 2020). This would correct any errors to ensure the project
works as required. Documentation would help with accountability and identify opportunities for growth
for the project. Risk tracking and documentation will help identify and solve risks before the system
begins to be used. This would help in future referencing during the project to avoid experiencing and
encountering those risks during the project implementation (Behutiye et al. 2020).

References:

Alaidaros, H., & Omar, M. (2017). Software project management approaches for monitoring work-in-
progress: A review. Journal of Engineering and Applied Sciences, 12(15), 3851- 3857.

Applegate, L., & Montealegre, R. (2018, April 25). Harvest City: The Intelligent Procurement System
Project. Harvard Business School.

Beach, L. R., & Lipshitz, R. (2017). Why classical decision theory is an inappropriate standard for
evaluating and aiding most human decision-making. In Decision making in aviation (pp. 85-102).
Routledge.

Behutiye, W., Seppänen, P., Rodríguez, P., & Oivo, M. (2020). Documentation of quality requirements in
agile software development. In Proceedings of the Evaluation and Assessment in Software Engineering
(pp. 250-259).

Kerzner, H. (2019). Using the project management maturity model: strategic planning for project
management. John Wiley & Sons.