So, today, we will have a different type of post compared to our previous posts on the Business Analyst role in Agile Scrum.
What exactly do I, a Business Analyst, do in a typical day? I will not make this post some kind of technical mumbo-jumbo and this jargon or that complex word. What I’m, sharing is a simple but straightforward day in my typical workday. So, let’s get started!
Morning, before work
It’s not a healthy habit but check the phone first thing in the morning to check for emails or messages to get an overview or idea if any situations require your immediate attention or not and make a note accordingly. Once done (should not take more than 5-10 mins), do your routine (I recommend coffee, exercise, and any of your chores) and get ready for your workday.
First Half of work – Work in full force
Usually, you will get approximately 30 minutes before the first meeting. Start reviewing your notes (if taken) with emails and messages to list items you will be working on today and review any tickets/stories that require your attention. It’s a simple to-do list, which you will merge with yesterday’s EoD list (More on this below). Do not add details to this. This is a simple list to make your day easier.
Then it’s time for a daily standup if you are in a (semi) scrum team. See, in Scrum, only developers do daily scrum and collaborate on the issues they are working on. It’s not exactly a status report meeting. But Scrum is flexible so that team members can provide their daily updates using the same format. Also, if there is no scrum master (which is the case I’ve observed), you will be running this so get to it, son! It shouldn’t take more than 15-20 mins (remember, the “official” daily scrum is timed at 15 mins max).
This is also the best time to follow up on all previous requests you might have made to anyone or follow up with the clients/stakeholders (if they are in a similar timezone). Once done, start working on the highest priority items first, based on the to-do list created (remember?!). I do not take any calls in the first half (unless there is an immediate requirement) as you can push for the most significant productivity during the first half. Schedule them in the 2nd half. Work on the Research and Analysis during this for the maximum output.
Second Half – After Lunch effects
So, you’ve taken lunch and will most likely feel like not working (I know I do) so take those scheduled calls and get the input or feedback from the Development and Quality Analyst team, and if required, provide your input as well. Then get ready for the scheduled (or unscheduled) evening meetings with the clients and/or stakeholders. This includes requirements elicitation, status updates, discussion of the blockers, backlog refinement, or specific requests from the stakeholder’s end. Additionally, you may have a daily standup of the “complete” team if you work globally and with multiple teams.
Once done, you start preparing for the next day and create a to-do of the items that you will work on tomorrow, next week, or in some cases, next month. Again, these are simple to-do lists to make sure you are tracking all the items and not missing anything, set up follow-ups and meetings as and when required. If you have some time, work on process improvements or upskill because nobody says no to a highly skilled multi-talented person.
Conclusion – Logout
Depending on your responsibilities, you might have late-night meetings but in most cases, it’s mitigated by migrating the work hours to the later part. For example, If you are in India, you may be working an 11.00 to 20.00 or 12.00 to 21.00 shift to collaborate with your US counterpart.
In conclusion, your days are busy. You will rarely get time to sit idle but it’s exciting and you will learn new things, interact with different types of people, and will impact directly the project or the company. It’s a highly demanding role but if you try, you’ll thrive and earn big bucks!
Thank you for reading. Until next time!