Week 18 & 19 : Kick-Off A New Initiative (#SWABA Series)
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.
Hello friends! Welcome back to another installment of my blog series, where I dive deep into the world of business analysis and share my journey with you all. In these past couple of weeks, things have been buzzing with activity as I continue to take charge of an exciting initiative. Let's unpack what I've been up to and the lessons I've learned along the way.
#1 Complexity Gradually Increases
As I navigate through my role as a beginner business analyst, I've noticed that the initiatives I'm involved in are becoming more complex. In Week 18 and 19, I took the reins of an initiative that was already in progress, but was soon to be impacted by a new project kicking off. Decision making and prioritization became key focal points, requiring a deeper level of analysis as we tackled new challenges each day.
Requirement Gatherings
Requirement gatherings have been at the forefront of my responsibilities during these weeks. Here's how I applied what I've learned in previous weeks:
Model : I've adopted a collaborative approach to requirement gatherings, recognizing that perfection isn't always necessary. The level of complexity and readiness to kick-off varies depending on the business strategy, with different initiatives requiring different levels of detail.
Method / Tools : Utilizing tools like the following :
Confluence for documentation,
JIRA cards for internal collaboration,
Trello for cross-departmental coordination,
Slack for asynchronous communication,
Zoom for synchronous meetings (or as we call them, "catch-ups"),
Figma for design has streamlined our process.
Artefacts: From comprehensive requirement documents detailing initiative background, stakeholders, in-scope vs. out-of-scope items, decision-making processes, timeline, design, release plans, and testing, to concise JIRA cards summarizing the work to be done, we've ensured clarity and alignment across the board.
Kick-Off Meeting
One significant milestone in our process is the kick-off meeting. This alignment session, held before the initiative is ready to begin, ensures that the documentation contains sufficient information for the team to hit the ground running. While I haven't led a large kick-off session yet, it's on the horizon, and I'm eager to apply my learnings in the weeks to come.
#2 Embracing Learning
Each day presents new opportunities for learning, and I've fully embraced this mindset. Whether it's understanding stakeholder needs or refining our project approach, I've come to appreciate the value of continuous learning in my role.
Attention to Detail Matters
Paying attention to detail has been paramount, particularly in refining the design of our website and app UI/UX. Even the smallest elements can significantly impact user experience, underscoring the importance of meticulous craftsmanship in our work.
Self-improvements :
As a beginner, it is important for me to review/ refresh my memory on the list of products/ features that my team (sub-domain) is working on; this will enable a productive conversation when running an initiatives
Continue to take note and learn the new acronyms, new jargon and terminology use in software development - this can be a steep learning for someone who has never work in Software Development domain like me ~ solution to this is, play around the products and put on a user hats
Ask a lot of questions and be smart to use “Clarification Question” ~ “Here is what I understand from our conversation, <share what I think I understood in my own words>, is this what you meant?”
Get support from mentor and team members to help me understanding the initiative / problem we are solving from designer - product - engineer - business perspective.
Pace myself (Something I think new beginner needs to patience with when learning BA role)
Agile Work Processes
Our journey isn't always linear, and I've learned to embrace the flexibility inherent in our work processes. Mini kick-offs within larger project scopes have taught me the value of adaptability and nimbleness in project management.
Informal Communication Practices
Lastly, our team has adopted more casual and spontaneous communication practices, eschewing formalities in favor of open dialogue and collaboration. This practices enable agility within our dynamic, enhancing our overall effectiveness.
And there you have it, folks - a glimpse into my adventures as a business analyst in Weeks #18 and #19. Stay tuned for more insights, anecdotes, and learnings in the weeks to come as I continue to swot my way through this exhilarating journey. Until next time, happy analyzing!
p/s : It’s Eid, hope you had a blast one with family and friends :)
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