Hello friends,

Welcome back to my #SwottingAsABusinessAnalyst (SWABA) series. Read my previous post here.

If you're new here, explore the initial post of my journey 'Swotting' as a budding Business Analyst.

During weeks 16 and 17, I had the chance to dive into practical business analysis work, applying the theories I've been learning. In this reflection, I'll share my key takeaways from this hands-on experience.

Related blogpost : Week 4- 6 Newbie Swotting As A Business Analyst

Context :

Let’s refer to the sample of scenario that I used from last week’s blogpost

In that blogpost, I’ve shared the theoretical steps to solve problems that benefit the business. In week 16 and 17, I was given an opportunity to take up a small piece of work (an initiative that’s worth 2.5 days of works from planning to release) and put the theory into practice.

(Note, due to confidentiality of company’s info, I am using the sample scenario that we discussed in last week’s blogpost instead - refer image below)

Related blogpost : Using Data To Identify Problems

Scenario : Addressing a Drop in CTR on LookForJob.com

#1 Problem Identification

Problem Identification (Shift the Business or Run the Business):

I delved into identifying problems and their root causes. For instance, observing a drop in clicks on the Apply Job page banner suggested a user engagement problem due to recent layout changes.

Problem identification :

The drop in clicks on the banner on the Apply Job page suggests potential user engagement issues, possibly caused by recent layout changes.

Root Cause Identification

Can we rootcause the issue?

How long have we been seeing this issue and what is the size of the click declines?

What recommendations do you (BA and team) have?

Initiative Execution:

I took on a small piece of work, enhancing the visual design of a badge, based on approved proposals. This initiative was swiftly executed, taking only three days to complete.

Other notes :

• Business strategy are divided into different categories such as “Shift the Business”( transformation) and “Run the Business” ( Operation)

• The size of works can be varies for both business strategies (STB and RTB)

• Additionally, the team utilizes a document called the Design Proposal or Product Canvas, curated by the Product & Design experts. This comprehensive document encapsulates details regarding problem identification, root cause analysis, and proposed solutions. It serves as a crucial tool for obtaining approval before proceeding with the execution of the work.

#2 Requirement Gathering and Acceptance Criteria

I learned that in Agile environments, gathering requirements and creating JIRA cards can happen simultaneously. This involves consolidating all initiative details and potential tasks needed to solve the problem.

Refer attached image (template) as reference to how I did it.

Requirement Gatherings on JIRA Card :

#3 Kick-off Sessions

• These sessions are crucial for setting expectations and fostering collaboration among team members. We discussed various aspects, including initiative context, design coherence, effort estimations, and FAQs.

• Refer the list of agenda items in the image below:

#4 Delivery

Handover to Engineers for Delivery and Layout Reviews

• After the kick-off, the work was handed over to engineers for coding and building the design. Active communication ensured the layout matched the plan.

• Layouts is commonly done using CSS (Cascading Style Sheets)

Regrouping and Release

• A quick regrouping session with product owners, UX designers, and engineers ensured the layout aligned with the plan. If all was well, the new design was released.

• It can either be done via zoom call or on Slack messages

#5 Post-Release Tracking

• Tools like Amplitude were used for monitoring product performance post-release. Data-driven insights helped in continuous learning and optimization for user engagement.

• And the result of the data, will reiterate the delivery process all over again (#1 to #5)

For continuous improvement begin again from Step 1 to 5, Repeat

In conclusion, these weeks were invaluable for my growth as a Business Analyst. Each stage presented unique challenges and learning opportunities, reinforcing the importance of adaptability, collaboration, and continuous improvement in the field. Armed with these insights, I'm excited to tackle future projects with confidence and innovation.

Found my content helpful? Consider to tip me a coffee via Ko-fi!

You can also explore my other blog post on Agile Delivery, Project Solutions, Agile Mindset and Career Bits on WorkWizard. Leave me a comment, would love to hear if we are on the same wavelength!

Read this article on medium : https://medium.com/@wawahalim