Scribd
Upload
196 views5 pages

Effective SWOT Analysis Guide

A SWOT analysis is a tool that organizes internal strengths and weaknesses as well as external opportunities and threats into a two-by-two grid. It helps achieve business goals by documenting these factors. Internal factors are within a business' control, like existing systems, while external factors like competitors, technology, and customer trends exist independently of the business. A systems project considers both internal and external environmental factors that can positively or negatively impact a business. A preliminary investigation identifies problems, defines the project scope, performs fact-finding through interviews and observations, evaluates feasibility, estimates costs and timelines, and presents recommendations to management in a report. Constraints are conditions that prevent an ideal solution from being fully delivered to customers.

Uploaded by

DUGONG BISAYA VLOG
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
196 views5 pages

Effective SWOT Analysis Guide

A SWOT analysis is a tool that organizes internal strengths and weaknesses as well as external opportunities and threats into a two-by-two grid. It helps achieve business goals by documenting these factors. Internal factors are within a business' control, like existing systems, while external factors like competitors, technology, and customer trends exist independently of the business. A systems project considers both internal and external environmental factors that can positively or negatively impact a business. A preliminary investigation identifies problems, defines the project scope, performs fact-finding through interviews and observations, evaluates feasibility, estimates costs and timelines, and presents recommendations to management in a report. Constraints are conditions that prevent an ideal solution from being fully delivered to customers.

Uploaded by

DUGONG BISAYA VLOG
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

PERFORM SWOT ANALYSIS

A SWOT analysis is a tool for documenting internal strengths (S) and weaknesses (W) in your
business, as well as external opportunities (O) and threats (T). You can use this information in
your business planning to help achieve your goals. To work out if something is an internal or
external factor, ask yourself if it would exist even if your business didn't. If it would, then it's an
external factor (e.g. new technology).
EXAMPLE: include competitors, prices of raw materials, and customer shopping trends.
A SWOT ANALYSIS organizes your top strengths, weaknesses, opportunities, and threats into
an organized list and is usually presented in a simple two-by-two grid.

INTERNAL AND EXTERNAL FACTORS


If there is anything that is steadfast and unchanging, it is change itself. Change is inevitable, and
organizations that don't accept change and that make adjustments to their business model to keep
up with changes are doomed to fail. There are events or situations that occur that affect the way a
business operates, in a positive or negative way. These events or situations can have either a
positive or a negative impact on a business and are called environmental factors.
● Internal Factors
– Strategic plan
– Top managers
– User requests
– Information technology department
– Existing systems
● External Factors
– Technology
– Suppliers
– Just-in-time (JIT)
– Customers
– Customer Relationship Management (CRM)
– Competitors
REASON FOR SYSTEMS PROJECT
● Main Reasons for Systems Projects
– Systems request
– Improved service
– Support for new products and services
– Better performance
– More information

– Stronger control

– Encryption and biometric devices

– Reduced cost

Factor that affects systems projects

– Internal and external factors affect every business decision that a company makes, and
IT systems projects are no exception
RESULTS OF PRELIMINARY INVESTIGATIONS

● Preliminary investigation

● Interaction with Managers and Users

Planning the Preliminary Investigation

– During a preliminary investigation, a systems analyst typically follows a series of steps

– The exact procedure depends on the nature of the request, the size of the project, and
the degree of urgency

● Step 1: Understand the Problem or Opportunity

– Determine which departments, users, and business processes are involved

– A popular technique for investigating causes and effects is called a fishbone diagram,
or Ishikawa diagram
● Step 2: Define the Project Scope and Constraints

– Present versus future

– Internal versus external

– Mandatory versus Desirable

– Regardless of the type, all constraints should be identified as early as possible to avoid
future problems and surprises

● Step 3: Perform Fact-Finding

– Conduct interviews

● Determine the people to interview

● Establish objectives for the interview

● Develop interview questions

● Prepare for the interview

● Conduct the interview

● Document the interview

● Evaluate the interview

● Review documentation

● Observe operations

● Conduct a user survey

● Step 4: Evaluate Feasibility

– Evaluate the project’s operational, technical, economic, and schedule feasibility

● Step 5: Estimate Project Development Time and Cost

– What information must you obtain, and how will you gather and analyze the
information?

– What sources of information will you use, and what difficulties will you encounter in
obtaining information?

● Step 6: Present Results and Recommendations to Management

– The final task in the preliminary investigation is to prepare a report to management

– The format of the preliminary investigation report varies from one company to
another
● Introduction

● Systems request summary

● Findings

● Recommendations

● Project roles

● Time and cost estimates

● Expected benefits

● Appendix

CONSTRAINTS

A condition or event that prevents the project from fully delivering the ideal solution to customers
and end-users. This is part of the expectation-setting that business
analysts have to perform on an ongoing basis to keep customer and
end-user expectations realistic throughout the project.

You might also like