2. SWOT analysis
Weakness
Strength
Flexing Implementing / Execution
Cheaper Expense of rework
No Baggage (Pre Conceived Ideas) Communication Barrier
Remove the problem Quality (poor)
Skills and Techniques Direct Stakeholder contact
Development (Co-Location and IT Agile) BA’s Offshore won’t push bar – takes longer
Working day can be longer Requires handholding
Behaviour/ cultural
Time difference
Opportunities Threats
Future Gain Wrong requirement
Learning for onshore BA’s Loss of onshore resource
Tap into highly skilled individuals / sharing case studies Change of supplier
Do more projects Change in skill sets
Global expansion Breach
Access to new markets Stakeholder disengagement
Loss of Control / knowledge
Loss of information/ security / intel prop
Poor PR
Politics
Career s for onshore
3. PESTLE Notes gathered
Political Is it acceptable to send jobs offshore?
Reducing the opportunity of working in the UK
Economic downturn requires inward
Third party to be based in stable country
Economic Cheaper
Possibly cheaper but tasks may take longer due to lack of knowledge
Exchange rate impact
Different cost of housing while on/ offshore
Sociological Immigration
Cultural Assumption
Cultural understanding – i.e equality
Potentially splitting families to make on/offshore work
Technological Data Security
System Access
Legal Intellectual Property
Employment law
Access to production data an issue
Can you prevent third parties sub-contracting? Once you contract out you lose control.
Contractual ambiguity
Contract wrangling
Environmental Different time zone for communication
4. Customer Journey for analysis offshore
Agreement on the fact that Offshore due to the global company having a presence offshore vs Outsourced offshore would not
change the customer dramatically.
End User Business Stakeholders Colleagues
Who is the Customer?
Who does that include? End product users Project managers, Subject Matter Other BA’s
Expects (the Knowledge Holders),
Project Sponsor, Developers and
testers.
What are their The end product has kept Successful delivery of project – on Hints, tips, coaching,
expectations their views, needs and time, on budget and according to peer review of work
wants into account in the plan. produced, support,
design of the product or Quality teamwork, lessons
service. Be the conduit in obtaining the learned
To be given the information required to design the
opportunity to have a say product or service.
Record information shared in an
accurate and timely manner.
Trust in expertise.
Build a relationship to gain the
trust
Continued…
5. …Continued
Who is the Customer? End User Business Stakeholders Colleagues
Touch points Research gathering Project Lifecycle offers a number of Peer Reviews
Sales touch points for BA’s offshore
Complaints based on type of analysis and
support. Ones discussed:
Business Case development, high
level requirements and
solution design, approach to
requirements, gathering of
requirements and test.
Moments of Truth Using the end product or Gates – quality checks, approvals,
service reviews etc.
Every interaction with a Every interaction with a stakeholder.
customer Gathering the requirements
Business and Technical Design to
complaint each other.
