<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Randima Thilakarathna on Medium]]></title>
        <description><![CDATA[Stories by Randima Thilakarathna on Medium]]></description>
        <link>https://medium.com/@randima-thilakarathna?source=rss-5ddb6f16b935------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dPDywa5Gig5oUHPTjidROQ.jpeg</url>
            <title>Stories by Randima Thilakarathna on Medium</title>
            <link>https://medium.com/@randima-thilakarathna?source=rss-5ddb6f16b935------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 04:14:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@randima-thilakarathna/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Product vs Project: A business Analyst’s point of view]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.datadriveninvestor.com/product-vs-project-a-business-analysts-pov-8ca4c82b8527?source=rss-5ddb6f16b935------2"><img src="https://cdn-images-1.medium.com/max/2600/1*nft-rNWBUMM9w95lcPCXmw.jpeg" width="6016"></a></p><p class="medium-feed-snippet">About working on both sides of the fence as a BA</p><p class="medium-feed-link"><a href="https://medium.datadriveninvestor.com/product-vs-project-a-business-analysts-pov-8ca4c82b8527?source=rss-5ddb6f16b935------2">Continue reading on DataDrivenInvestor »</a></p></div>]]></description>
            <link>https://medium.datadriveninvestor.com/product-vs-project-a-business-analysts-pov-8ca4c82b8527?source=rss-5ddb6f16b935------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ca4c82b8527</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Randima Thilakarathna]]></dc:creator>
            <pubDate>Sun, 03 Jul 2022 18:01:49 GMT</pubDate>
            <atom:updated>2022-07-22T04:20:49.490Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Business Analyst and the stakeholders]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.datadriveninvestor.com/business-analyst-and-the-stakeholder-28342e93ed18?source=rss-5ddb6f16b935------2"><img src="https://cdn-images-1.medium.com/max/1297/1*IZ1R5HuMzYY2bAt2i27JuA.png" width="1297"></a></p><p class="medium-feed-snippet">As a business analyst, you need to work with multiple parties on a day-to-day basis. For me, as a business analyst who is exposed to the&#x2026;</p><p class="medium-feed-link"><a href="https://medium.datadriveninvestor.com/business-analyst-and-the-stakeholder-28342e93ed18?source=rss-5ddb6f16b935------2">Continue reading on DataDrivenInvestor »</a></p></div>]]></description>
            <link>https://medium.datadriveninvestor.com/business-analyst-and-the-stakeholder-28342e93ed18?source=rss-5ddb6f16b935------2</link>
            <guid isPermaLink="false">https://medium.com/p/28342e93ed18</guid>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Randima Thilakarathna]]></dc:creator>
            <pubDate>Mon, 03 May 2021 10:57:26 GMT</pubDate>
            <atom:updated>2021-05-03T11:59:10.793Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[About Me —  Randima Thilakarathna]]></title>
            <link>https://medium.com/about-me-stories/about-me-randima-thilakarathna-88e02c0a6e45?source=rss-5ddb6f16b935------2</link>
            <guid isPermaLink="false">https://medium.com/p/88e02c0a6e45</guid>
            <category><![CDATA[about-me]]></category>
            <category><![CDATA[my-story]]></category>
            <dc:creator><![CDATA[Randima Thilakarathna]]></dc:creator>
            <pubDate>Wed, 16 Dec 2020 12:03:13 GMT</pubDate>
            <atom:updated>2020-12-16T12:03:13.069Z</atom:updated>
            <content:encoded><![CDATA[<h3>About Me — Randima Thilakarathna</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bxRlV90lfbXyw-b07IjdCg.png" /><figcaption>Galle, Sri Lanka. Timo Gotz/Shutterstock</figcaption></figure><p>I was born in a small paradise called Sri Lanka, in a beautiful coastal city called Galle which is famous for the old dutch fort and beautiful beaches.</p><p>Let me start off with a small story. As a small girl, I always had wonderful memories of different cultural festivals we celebrated. Every year April 14th our family would celebrate Sinhala Hindu new year and this is one of the most happening days of my entire childhood.</p><p>On new year’s day, we perform all activities according to auspicious times, and exchanging money was one of the highlights of that day for me. Obviously, I had no money to give as I was just a kid. But I always had plans for every rupee and cent that I estimated that I’d receive on that day. Once I’ve received money from my parents, grandparents and other relatives I remember badgering my father to take me to the book store in Galle town.</p><p>But there was one problem. Most shops were closed on new year&#39;s day and the day after. But I’d not stop my nagging till my father would take me to the book store. I remember that the store was closed. I’d circle around a couple of times and come back home feeling distraught. This happened multiple times till I somehow managed to buy the books that I was eyeing.</p><blockquote>This I think is how I fell in love with writing.</blockquote><p>Reading different books by different authors, imagining how it would be there in that precise situation that the writer tried to explain, helped me travel far and wide even though I hadn’t set my foot outside Sri Lanka till my late twenties. The more I read, the more I fell in love with writing. I tried to reflect on what I’ve read in my own manner and improvise. The more I improvised, the more it enabled me to become better in writing. I would go on to win creative writing competitions at the national level multiple times.</p><blockquote>Life was good, till I got caught in a rat race</blockquote><p>During this part of my life, I fell out of love with both reading and writing. I was driven by the typical Sri Lanka career dream of becoming a doctor. so I started studying science, chemistry, and physics. Although I gave all that I had it always demanded more. I was spending so much time and effort on something, which at this point of life when I look back I think “what a waste”. I forgot about writing altogether.</p><blockquote>And my love for writing was long lost….</blockquote><p>I didn’t become a doctor. I didn’t become a writer also. Instead, I ended up studying management and Information Technology and became a Business Analyst working on information systems improving Supply Chains. I chose a career that was totally unexpected. My career choice was neither love at first sight or an arranged marriage. I’d say it’s something in between. I didn’t love it at first or didn’t hate it either. But as years passed it started growing on me (in a good way).</p><p>My job kept me and still keeps me excited every day with different problems to solve, different things to learn. But as I started exploring more into learning and improving career-wise, one thing that I noticed was very rarely people wrote about what they do and how they learn something (at least in my discipline). This lead me to try to combine writing with what I do, and what I learn. Then I moved to Singapore and the opportunities to learn and be a part of something interesting got even wider. So now I try to write about what I do.</p><blockquote>I’m still on my path to rediscovering long lost love</blockquote><p>In my spare time try to read as much as possible. Honestly, the habit of reading had totally disappeared from my life. But I’m still trying to get back in on that habit. I’m fortunate enough to meet lots of interesting people, explore different places outside of Sri Lanka. I try to hear what each person has to say and learn and grow as a person. I’m eternally grateful for all the opportunities that I’ve gotten along the way, every step which helped me reach where I am.</p><p>So yeah, this is me in 736 words.….</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88e02c0a6e45" width="1" height="1" alt=""><hr><p><a href="https://medium.com/about-me-stories/about-me-randima-thilakarathna-88e02c0a6e45">About Me —  Randima Thilakarathna</a> was originally published in <a href="https://medium.com/about-me-stories">About Me Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Roots of a good user story…]]></title>
            <link>https://medium.datadriveninvestor.com/roots-of-a-good-user-story-3fe9dada62ed?source=rss-5ddb6f16b935------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fe9dada62ed</guid>
            <category><![CDATA[sdlc]]></category>
            <category><![CDATA[requirements-management]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Randima Thilakarathna]]></dc:creator>
            <pubDate>Fri, 04 Dec 2020 03:57:12 GMT</pubDate>
            <atom:updated>2020-12-06T15:00:53.079Z</atom:updated>
            <content:encoded><![CDATA[<h3>Roots of a good user story….</h3><h4>My story of learning to write a good user story</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bm5LG6N_0xUhvf_-zEXDCg.png" /><figcaption><a href="https://unsplash.com/@youxventures">You X Ventures</a> from <a href="https://unsplash.com/">https://unsplash.com/</a></figcaption></figure><p>It was the early days, right after I started as a Business Analyst. I was still quite new and exploring the best way to do day-to-day tasks. During my first job, when working in a development team, user stories were already split by someone else, and each of the stories and small and defined requirements within it.</p><p>I was used to this pattern where I get assigned to a user story and I analyze and try to add a description explaining what needs to be done and arrange a walkthrough with the DEV. But I never went to lengths of further splitting what was assigned to me.</p><blockquote>What I didn’t understand then, was that when the stories are splitted to miniature size, the scope is clear and helps massively to provide clarity to the requirement it self</blockquote><p>In my next job, I got the opportunity to work on projects where we were building new features with bigger scopes. And I tried approaching these features the same way that I did before. But it didn’t take much time for me to understand that something was not working.</p><p><strong>What can go wrong if a user story is not simple and clear?</strong></p><p>Some of the points that I was able to understand from my experience are as follows.</p><blockquote>It is important to look at a story from the users’ perspective and what goal that particular user was trying to realize through this story and the story should provide the most detailed view of this goal.</blockquote><p>For example let’s take “As a customer, I want to pay for an order” as a user story. There is a stakeholder and a goal mentioned. But when thinking of how the stakeholder can achieve this goal, there are many pathways. There are still unanswered questions like</p><ol><li>What kind of payment?</li><li>Is it a card payment?</li><li>Is it a cash payment?</li><li>If it’s a card is it VISA or Master should there be 2 processes?</li></ol><p>There can be various processes depending on how a customer wants to pay. The fields on a form will be different based on the type of payment the customer chooses. Especially when we build something new sometimes each field had its own behavior and these fine level details have to be elaborated.</p><blockquote>When you approach the feature in bulk it becomes difficult to visualize these granular details beforehand.</blockquote><p>Because so much information is hidden inside one umbrella story it can become difficult to see these granular scenarios. Also normally what you can’t see, your teammates are able to see if they have clarity of the story and when it’s being discussed. But how can they contribute if the story discussed is too big and if it’s easy to forget the full scope and get sidetracked. This actually is linked to the next point.</p><blockquote>When the granular scenarios are missed a lot of communication is required between the rest of the team.</blockquote><p>A lot of discussions follow because the product team, dev team, and QA team need to be on the same page. I’m not saying that if requirements were perfect and documented at a granular level that we don’t have to communicate anymore. Still, there is plenty to communicate because on the way we find many things unforeseen. We need to alter what we do and how we intend to do things accordingly. But a well-structured user story removes ambiguity and provide the team more time to discover and work on unforeseen roadblocks. Which brings me to the last point.</p><p>A good user story helps to manage the team’s resources in an effective manner. We all work with time and resource constraints. This is why we try to estimate stories before taking them into a sprint.</p><blockquote>If a user story is ambiguous and unclear mostly the time estimations given beforehand can go wrong.</blockquote><p>Also, resource allocation can be impacted. If the story was split properly it could have been the workload for multiple people whereas now a single DEV resource will have to take a longer time to complete, resulting in the story to drag multiple sprints.</p><p><strong>So how to write a good story?</strong></p><p>I was trying to understand what makes a good user story. A user story is a simple way to express user requirement and there must be steps we can take to write a good user story.</p><blockquote>A good user story always started with good requirements.</blockquote><p>There are many times of requirements. When I wrote my initial article “<a href="https://medium.com/datadriveninvestor/building-a-house-vs-576d020a598b">Building a House Vs. Developing a Software: The Role of the Business Analyst in Requirements Analysis</a>” I only knew a functional and non-functional requirement. It was basically must have’s and nice to have’s.</p><p>But when I started studying more into requirement analysis I realized, while there is that higher-level division in requirements, there are a lot more detailed level categories</p><p><strong><em>Types of requirements</em></strong></p><ol><li>Business requirements</li><li>Business rules</li><li>Functional rules</li><li>Non-functional requirements</li><li>External interface requirements</li><li>Physical setting requirements</li></ol><p>So when you are trying to solve the problem of a customer all of these aspects needed to be considered and by doing so you can come up with a clear set of requirements that would help you to solve your customer problems.</p><blockquote>Rather than looking at this from a high level, these detailed requirements from various perspectives would help you to look at the micro-level better.</blockquote><p>When you understand micro levels better you can create a better user story with multiple scenarios thought of.</p><p><a href="https://www.datadriveninvestor.com/2020/11/02/artificial-intelligence-leadership-and-talent-management/">Artificial Intelligence, Leadership, and Talent Management | DataDrivenInvestor</a></p><p><strong>Create detailed acceptance criteria within the user story</strong></p><p>I’ve actually never heard of the term acceptance criteria before one of my senior team members suggested it to me. Basically, it was detailed steps that would elaborate on how the user (upon whom the user story is based) would try to achieve the goal of the story. And to do that what requirements are needed to be completed on the way. She was giving me an example of how these steps should be written and it went to such a micro level I remember asking her to do we need to go to this level. She said yes. She asked me to imagine myself as a person who knows nothing about the feature or product.</p><blockquote>Acceptance criteria should help a person (who knows nothing about the product or feature) navigate and get the goal completed.</blockquote><p>Because when you look at the same story/ feature for too long certain points become familiar to you and sometimes you don’t feel like they should be documented even (As they are already normalized to you). But when other team members read into it and develop the feature based on it and start testing it they might see it as a missing point in requirements. It’s something hard for me even now. Still trying to master that.</p><p>That day I was introduced to the format below for a user story and acceptance criteria writing and I never looked back.</p><blockquote><strong>[As a User]role of the person [ I want to be able to] action [so that I would be able to do ] achieve a goal</strong></blockquote><p>I realized by breaking the stories I actually get some guidance naturally to dig deeper into every specific behavior that I expect or can expect with the design. Acceptance criteria helped me to stepwise explain all these behaviors and whenever possible I used wireframes/prototypes in the acceptance criteria. I was telling a story and for another totally new person to imagine, I understood that pictures helped more. Like in storybooks. That is another lesson that I realized.</p><p>To further help in writing stories there are few additional safety measures that one can follow. These attributes can help a good user story to become great. These were introduced by Bill Wake and is currently used in the industry lot. This is known as the <strong>INVEST</strong></p><ol><li>Independent</li><li>Negotiable</li><li>Valuable</li><li>Estimatable</li><li>Small</li><li>Testable</li></ol><p>So whenever I got a set of requirements grouped into a story, I always try to cross-check if the story that I just defined matches these criteria</p><p>So the roots of a good user story go far and wide and can decide if what you do is going to succeed and fail in a way. I’m not saying good user stories would make your feature fail-safe. But it would help you smoothly build something and maintain a clear vision of what needs to be built and once built you have some reference to compare as a business analyst or a product owner/ manager.</p><p>A good user story starts from requirements analysis and ends at the point of software testing and impacts the entire development life cycle where.</p><blockquote>By dividing user stories and mapping small independent, estimable, negotiable, valuable requirements can provide clarity to the feature.</blockquote><p>This would also help to ease your mind from the perspective of creating a good feature and will make life easier for you and your teammates. These are things that I found helpful over time and still, there is a lot to explore and learn so that I can provide more clarity to the team to build features.</p><p>So that’s my story of learning to write a good user story. Hope you enjoyed it and got to learn something too.</p><h4>Gain Access to Expert View — <a href="https://datadriveninvestor.com/ddi-intel">Subscribe to DDI Intel</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fe9dada62ed" width="1" height="1" alt=""><hr><p><a href="https://medium.datadriveninvestor.com/roots-of-a-good-user-story-3fe9dada62ed">Roots of a good user story…</a> was originally published in <a href="https://medium.datadriveninvestor.com/">DataDrivenInvestor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From one grey area to another… Business analysis vs Product ownership]]></title>
            <link>https://medium.datadriveninvestor.com/from-one-grey-area-to-another-business-analysis-vs-product-ownership-d8a1c5ac8d35?source=rss-5ddb6f16b935------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8a1c5ac8d35</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[requirement-elicitation]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[sdlc]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Randima Thilakarathna]]></dc:creator>
            <pubDate>Tue, 21 Apr 2020 05:22:59 GMT</pubDate>
            <atom:updated>2020-04-22T14:01:39.666Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M7ISSnaIh4tESiPoO_ZKiQ.png" /></figure><h3>From one grey area to another….. Business analysis vs Product focus</h3><p>I’ve been writing about being a business analyst for a while now. I always used to dwell on the fact that how much of grey area the title and job role is. I was puzzled about where to next, what to learn and how to become better in what I do. I always felt inadequate and I always looked for content to study and understand but sometimes failed to see a continuation or proper direction on what to study or practice to become better at what I do. My then job role (I started my career as a Business Systems Analyst) began in product support and then gradually moved towards product development.</p><h4>A tiny cog in a well-oiled machine: Working as a BA in a large corp.</h4><p>I was a business systems analyst for a company with a global presence and with a high number of customers. The product itself was huge and served customers from a lot of different industries. To provide solutions to problems that these customers had, there were really large teams. In Sri Lanka only there were more than 1000 employees.</p><blockquote>And there I was, One of these 1000 people trying to solve problems of a customer from another end of the world.</blockquote><p><strong>Then</strong></p><p>There was one problem. For me to see the holistic view of what the product did was not easy. I was an entry-level business analyst so one can say it was not my job. I was always trained to look at a tiny problem and find a solution that would have less or no functional impact on existing functionality. What would happen is I’d get a story from the backlog (Which was nicely curated and prioritized for me by someone else). Work on it with my team. test it and patch it.</p><p><a href="https://www.datadriveninvestor.com/2020/01/16/software-development-process-how-to-pick-the-right-process/">Software Development Process: How to Pick The Right Process? | Data Driven Investor</a></p><p>I had no clue about what this change would do to the product itself. Would it alter the customer journey that some customers already have? Would it make a majority of customers happy? Would there be a set of customers who would not benefit from this? What are we using to measure the success or failure of this improvement etc?</p><h4>Now</h4><p>I recently moved to Singapore and started to work as a business analyst/ product owner in a startup. Initially, I took on several assignments which were more like functional enhancements. Still, there was a lot to think.</p><blockquote>The major difference that I experience at the very first glance was the frequency of asking why.</blockquote><p>And believe me, I didn’t ask why enough and it got me into a lot of problems later. Why are we doing this? Why is this a problem? Why are we solving this right now instead of say 5–6 months down the line? Why is the solution structured this way than that way? So lots of Whys….</p><p><strong>Lessons learned!</strong></p><p>For a while, I was trying to do things the same way I did in my previous role. I felt every day something is not right but really didn’t know how I should change. It took me some time. But made me realize 3 things.</p><ol><li>Your problem might be tiny. But when coming up with a solution you should think from a holistic level. What is the problem? What is the solution?. Is this the right solution? How do we get the quickest validation from internal external customers? How the solution will impact different customers? How do we measure the success of the product?</li><li>When the team is small you need to communicate frequently and keep everyone in the loop always</li><li>Concept of agile like breaking down user stories to a finer level as much as possible, writing acceptance criteria, discussing requirements with the entire team to develop the requirement rather than working on it by your self for while are much better ways of solving a problem of a product.</li></ol><p>For me, it took a while to absorb these concepts and change my mindset. I had to shift my focus to be more product-focused.</p><blockquote>I felt I’d just jumped to the deep end of the pool while knowing very little about swimming.</blockquote><p>And for a while, I was trying to approach product ownership and product management using the same mindset and approaches I used as a business systems analyst and I realized that I was not on the right path.</p><p>I know these concepts or facts are not out of this world or so novel. But me being a novice to working with a product mindset struggled and sometimes learned my lessons the hard way.</p><p><strong>Have a clear idea about it…</strong></p><p>Now I’m mature enough whenever I get some requirements, information about a customer&#39;s problem first to ask the following questions and get a clear idea of what should be done.</p><ol><li>why we are doing this?</li><li>What problem are we going to solve?</li><li>Is it really a problem to the customer?</li><li>How can we solve this? (This is a question I used to ask just from my self. Now I try to involve the whole team before expanding requirements)</li><li>what benefits would come out of this?.</li><li>What is the technical effort that goes into the product vs the expected return from implementing a particular solution?</li></ol><p>I’m not saying I’m an expert and there are a lot more things to learn about being mindful about the product. But hey, At least I got a start.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb2a0d6%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb2a0d6%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/0707f5c806284d01a4a13c7b13a91ce3/href">https://medium.com/media/0707f5c806284d01a4a13c7b13a91ce3/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8a1c5ac8d35" width="1" height="1" alt=""><hr><p><a href="https://medium.datadriveninvestor.com/from-one-grey-area-to-another-business-analysis-vs-product-ownership-d8a1c5ac8d35">From one grey area to another… Business analysis vs Product ownership</a> was originally published in <a href="https://medium.datadriveninvestor.com/">DataDrivenInvestor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a house vs.]]></title>
            <link>https://medium.datadriveninvestor.com/building-a-house-vs-576d020a598b?source=rss-5ddb6f16b935------2</link>
            <guid isPermaLink="false">https://medium.com/p/576d020a598b</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[requirements]]></category>
            <category><![CDATA[requirement-analysis]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Randima Thilakarathna]]></dc:creator>
            <pubDate>Fri, 04 Jan 2019 06:44:11 GMT</pubDate>
            <atom:updated>2019-01-10T13:41:05.779Z</atom:updated>
            <content:encoded><![CDATA[<figure><a href="http://www.track.datadriveninvestor.com/1B9E"><img alt="" src="https://cdn-images-1.medium.com/max/700/0*4GozZ8jNWlOp7v8_" /></a></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*uOT2JdOxRc_eCUvNrQ_KQw.jpeg" /></figure><h3>Building a House Vs. Developing a Software: The Role of the Business Analyst in Requirements Analysis</h3><p>Building a house is a tricky business. The basic and the most important step of this would be to come up with the design or the house plan. Coming up with a design that is aesthetical and user-friendly is also challenging. Even though the house looks beautiful inside out, if it’s not practical or fails in terms of the usability there will be no point at the end. Sometimes the owners of these houses have crazy design ideas as well.</p><blockquote><em>Taking such abstract concepts and building up a home which meets all the criterions and pleasing all involved parties can be very stressful and frustrating.</em></blockquote><p>If the designer, structural or civil engineer or the architect try to involve too much in the design and if the home built at the end is different to the owners’ expectation that regret might haunt the homeowner for a long time as the house itself is a big investment.</p><p>Same can be said for the development of software. Sometimes it could be just one sentence that a business analyst receives. XYZ functionality should help the customers to complete the ABC task.</p><blockquote>But to build upon a mere sentence and to provide something that is more than what was requested is something that we all as business analysts should be trying to do.</blockquote><p>To provide something that exceeds the expectation first thing that should be done would be to identify what is expected.</p><p><strong>Defining the scope</strong></p><p>If it’s a small application, it can be a bit easy to define the scope within a few attempts. But if it’s larger application having a lot of components interacting together scope setting might be bit difficult.</p><p>Let me explain with an example. This might not be “the method” to look at requirements always. But this is how I thought of it Suppose you want to develop a small mobile application that would help users to practice multiple choice questions for Information communication technology subject. Then the most basic requirements here would be as follows.</p><blockquote>· Shall be able to view the questions</blockquote><blockquote>· Shall be able to collect responses</blockquote><blockquote>· Shall be able to validate the responses provided</blockquote><blockquote>· Shall be able to display the summary statistics</blockquote><p>This would be the preliminary level scope.</p><p><strong>Growing up on the preliminary scope</strong></p><p>The above preliminary scope can be improved and developed to sub-levels. But make sure to dive into the depth within the preliminary scope that you defined. In a JIRA environment, these sub levels are called user stories and subtasks. The requirement will be divided into pieces that are meaningful and approachable subtasks.</p><p>If we look at the first requirement where user shall be able to view the questions, there could be many methods that a user might use the application to view past questions. Some of the methods that were thought of were as follows.</p><blockquote>· Requirement 1.1: Shall be able to view questions per year of publication</blockquote><blockquote>· Requirement 1.2: Shall be able to view questions per subject area.</blockquote><blockquote>· Requirement 1.3: Shall be able to view questions in an environment similar to the actual exam (exam simulator environment where you can answer questions while being timed)</blockquote><p>One thing to remember here would be that having a lot of details will help the next person to see the requirements from your eyes. But then again it is a must to always include relevant information here.</p><p><strong>Divide and conquer</strong></p><p>Let’s think that a developer looks at task 1. He or she will try to come up with a design that enables viewing of questions per year of publication. He can take many approaches. The ambiguity here is something that can be further divided. This level I’d like to think of as the subtasks within a user story. So, I decided to further elaborate the requirement 1.1.</p><blockquote>1.1.1 Shall be able to select a paper from a menu containing the included publications</blockquote><blockquote>1.1.2 Shall be able to view the questions and provide one or more responses depending on the type of question</blockquote><blockquote>1.1.3 Shall be able to view the answer for a question upon submitting an answer</blockquote><blockquote>1.1.4 Shall be able to bookmark question for later reference</blockquote><blockquote>1.1.5 Shall be able to resume a paper from where it was stopped after considering user input.</blockquote><p><strong>Nice to have requirements</strong></p><p>Viewing a question in Multiple choice question practice application is a must. It will be a mandatory requirement. But there will be requirements that are not must-haves. These are nice to have requirements.</p><blockquote>These are requirements that we can live without.</blockquote><p>If I refer again to the previous example again it would add value if the users should be able to see their past performance on a dashboard. Or it should be possible to set customized reminders which are either repetitive or onetime to remind the user to follow a routine and complete the papers available.</p><p><strong>Non-functional requirements</strong></p><p>The second half of a proper requirement analysis is to look at the non-functional side of the requirements.</p><blockquote>In general, these requirements stem from the areas of performance, capacity, accessibility, security, clarity, exception handling and so on.</blockquote><p>If I refer to the previous example, in a mobile app the GUI is really important. You are trying to show the bulk of information in a screen that fits the palm. So, overcrowding the screen will make it difficult for the user to interact. Proper user experience is something to keep in mind in this kind of a scenario. If it’s a bulky application having a lot of information being smart on what to show to users and how to show it to the user in a smaller screen is also something to be mindful. But I will stop right there, as it is an altogether different topic.</p><p>Another non-functional requirement that I could think of was the accessibility. The prime reason why we try to do something through the mobile is the ability to attend to that action on the go. If the application doesn’t load or takes a lot of time to load there will be no use of it. These non-functional requirements are most of the time critical and should be considered with greater importance.</p><p><strong>Things to note</strong></p><p>In real-world development sometimes the requirement analysis might not be as straightforward as what I said before.</p><blockquote>Especially if you are working in an agile environment it might be the case where you define requirements while you are progressing through the development lifecycle.</blockquote><p>Also, there will be a lot of back and forth discussions with the developer and even the requirement owner and the end customer. The scope and requirements can heavily differ in such environments.</p><p>Also, business analysts alone might not be able to comprehend everything at once and might require help from other parties to cover the requirements comprehensively. All in all, the aspects of requirement analysis can be tricky and needs to be done thoroughly as rest of the success of the development depends on it. Just like building a home.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb2a0d6%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb2a0d6%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/0707f5c806284d01a4a13c7b13a91ce3/href">https://medium.com/media/0707f5c806284d01a4a13c7b13a91ce3/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=576d020a598b" width="1" height="1" alt=""><hr><p><a href="https://medium.datadriveninvestor.com/building-a-house-vs-576d020a598b">Building a house vs.</a> was originally published in <a href="https://medium.datadriveninvestor.com/">DataDrivenInvestor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What do Business Analysts do? We do a bit of everything …]]></title>
            <link>https://randima-thilakarathna.medium.com/who-are-we-we-are-business-analysts-what-do-we-do-we-do-a-bit-of-everything-580652f22a44?source=rss-5ddb6f16b935------2</link>
            <guid isPermaLink="false">https://medium.com/p/580652f22a44</guid>
            <category><![CDATA[system-analysis]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Randima Thilakarathna]]></dc:creator>
            <pubDate>Sat, 11 Aug 2018 04:11:50 GMT</pubDate>
            <atom:updated>2018-08-14T04:26:06.000Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zF-M6ozDYK5Z7ay_rL257g.jpeg" /></figure><p>Right before the end the final exams of the university I was going through rounds of interviews in different IT companies. The position that I was trying to get in to was having many names. Some companies had it defines as Business Analyst. Another as functional consultant. Another as Business Systems Analyst. But the job description was almost the same from the look of it. I finally became a Business Systems Analyst. But why there were so many names and what kind of tasks were to be performed was something which I was found quite intriguing and dynamic from company to company.</p><h4><strong>Title variations</strong></h4><p>I found a diagram which gave some logical reasoning to the title hierarchy. When considering the below process diagram, I my self is involved in the latter 3 boxes or last 2 (depending on case to case). In that case my title should be a combination of IT Business Analyst and System analyst. So, it kind of logically explained what I did.</p><blockquote>Again, no matter where you are in the process diagram, there is still a chance that you still will be called a Business Analyst as it’s more of a generic name per say.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*P8fsmiXOCW-e2UKwGOIeNw.jpeg" /><figcaption>Source : <a href="http://www.modernanalyst.com/Portals/0/images/Roles%202.jpg">http://www.modernanalyst.com/Portals/0/images/Roles%202.jpg</a></figcaption></figure><p>The role of a business analyst changes based on the company that you work for as well. Some IT companies are product driven companies, and some will be project driven.</p><h4><strong>Role of a Business Analyst in a Project Driven Organization</strong></h4><p>In a project organization there will be a scope to be delivered within a given time under a given budget. In most cases each small project will be specifically designed to suit the requirements of a specific customer. There could be to approaches to this.</p><p>1. Starting from the scratch and building something entirely new based on the exact requirements of a customer</p><p>2. Most project companies keep a skeleton which is then customized, tweaked here and there to meet the requirements of many customers</p><p>In both these scenarios business analysts play a big role in grooming. As I see it’s like building a house and a business analyst does a job that’s very similar to an architect. Approach 1 is very rarely seen. But either way business analyst will have a lot work in communicating to customer identifying the requirements, building SRS (Software Requirement Specification), design how these requirements will be facilitated in the system and even help with wireframe designs of the user interfaces.</p><p>In this kind of setting identifying and eliciting customer requirements to the point will be really important. Also, if something cannot be accomplished, explaining to them that this will not be delivered due x,y,z reasons is a must.</p><h4><strong>Skill set required when taking up the role</strong></h4><p>To go through this cycle the Business analyst might need bit of everything. If he or she is to properly understand the customers view point having some knowledge of the industry, business and technical jargons. Then once you get back to your team and developers and pass on the requirements having bit of understanding on the system perspective is also good. It may take a while to understand the technical perspective especially if you are from a non-technical background.</p><p>It gets bit easier if the same skeleton is modified for different customer requirements. But it will also be tricky if you are working on the same skeleton for a while and if you have done a lot of customizations. But with time you can get really familiar with the capabilities of the existing skeleton and as a business analyst could identify how to grow this skeleton in a more useful way.</p><h4><strong>Role of a Business Analyst in a Product Driven Organization</strong></h4><p>The process becomes holistic rather than working in silos where your focus tends to narrow down a bit, specifically targeting the project scope. Duration becomes more long term and steady teams will be there. In this kind of an environment Business Analyst kind of needs to see the overall picture. How this change would impact other parts of the product kind of thinking.</p><blockquote>Also, a lot Research and development will be involved as well. When the product has a large customer base some of the requests made by customers cannot be always fulfilled.</blockquote><p>In this kind of a scenario if the Business analyst has exposure to these customers, he or she can give input to the Upper management on identifying the most value adding requirements to the product.</p><h4><strong>How Business Analysts can add further value to the product.</strong></h4><p>Once a decision is made on the what adds more value to the product, a business analyst can also be involved in shaping up the raw customer requirement so that it’s ready for implementation. In this process the Business analyst will have to think through on how to merge these new features in such a way that in syncs smoothly with or on top of the existing functionality.</p><blockquote>The requirement sometimes doesn’t start from the customer. In that instance business analyst’s role requires bit of conceptualizing.</blockquote><p>There is a lot of space to be creative. But creativity should always favour and should be in line with the products objectives. Sometimes at the inception we might not know what customers expects and how will they perceive what’s delivered. One size fits all kind of designs require a lot of thinking and time. And might be a tricky thing to do as well.</p><h4><strong>Tasks of Business Analyst that might be common to both product and project-based organizations</strong></h4><p>Some of the most common tasks performed by Business analysts in both product and project type of organizations are as follows.</p><p>1. Identifying bugs and once it’s fixed testing the bug</p><p>2. Documentation of the implementation</p><p>I agree both these might not be done by business analysts as well. It all depends on the organization as well. If you have a specific Quality Assurance team they would do testing part of the development.</p><blockquote>But I feel if the implementation is your brain child it’s better if you as a business analyst go through it at least once before this is exposed to customer.</blockquote><p>If It’s you who did communication with customer and groomed the requirement, then you will know if what done is up to customer expectation or not.Same applies for documentation as well. There could be technical writers overlooking this bit. But in some organizations business analysts might perform this task as well.</p><p>All in all, business analysts do bit of everything. A Business Analyst might not be the person who builds a software but it’s them that ensures that the right product is built.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=580652f22a44" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secrets to a happy marriage… between Agile and documentation]]></title>
            <link>https://randima-thilakarathna.medium.com/secrets-to-a-happy-marriage-between-agile-and-documentation-a89ad85034b2?source=rss-5ddb6f16b935------2</link>
            <guid isPermaLink="false">https://medium.com/p/a89ad85034b2</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Randima Thilakarathna]]></dc:creator>
            <pubDate>Sat, 21 Apr 2018 09:32:05 GMT</pubDate>
            <atom:updated>2018-04-21T09:32:05.542Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aoDalMtqItdxB60XhBbRag.png" /></figure><h4>Balancing documentation in an Agile world</h4><h4>The subject of marriage is quite complex. Marriage is a place where two people with imperfections, various backgrounds trying to work out their differences while making compromises. Well… if you are here looking for marriage advice let me stop you right there. Today we’ll talk about a marriage that’s a bit more technical.</h4><p>I’m interested in a marriage that had been there for quite some time. One that had gone through rough patches and something that had been complicated from the very beginning to say. It’s the marriage between the Agile methodology and documentation. In the software development industry, Agile methodology is a hot topic and most companies in the industry today are practising it.</p><p><strong>Is documentation relevant in the Agile world?</strong></p><blockquote>In the Agile Manifesto, the higher value is given to workable software over comprehensive documentation.</blockquote><p>While it’s true that we need good workable software, documentation is also important, especially in large applications. Good documentation helps create shared knowledge of the application. This, in turn simplifies the transfer of this knowledge. This is vital in large applications, where it’s not humanly possible to keep track of everything.</p><p>It could be very difficult to strike a balance between these two entities. From my perspective, one cannot flourish without the other (Agile developments and documentation).</p><p><strong>Fixing the broken marriage</strong></p><p>But how can we work things out in this complex relationship? There are two key objectives to focus on when documenting in Agile development. One is how to create a shared understanding and the other is communication of this shared understanding in a good manner.</p><p>So how can we create a shared understanding a communicate it in an effective manner? One approach is before documenting anything to ask the following questions from yourself.</p><p><strong>Focus on the audience</strong></p><p>Will this document be used just for the internal use or will external customer or marketing or sales will be referring to this or is it just for my reference?</p><p>More often than not, teams tend to quickly write up some documentation after a hectic sprint without considering who will be reading it. And we say to ourselves, the documentation is done!</p><blockquote>The audience is the key. If a value is not delivered to the specific person who is reading it what’s documented won’t be of any use.</blockquote><p>The documentation should be audience specific. In UX, we create personas to understand each user’s need. One document for all is not a good approach if we are truly focusing on helping all stakeholders.</p><p>Easier said than done right? You must be saying to your selves. With the deadlines and targets set, it is actually difficult to focus on documentation from a practical perspective. But can we do something about it other than delaying documentation until we are compelled to do it? This is something that we all can work on.</p><p><strong>Document as you learn</strong></p><blockquote>One actually interesting approach to this problem could be writing documentation as you learn.</blockquote><p>Let me elaborate. As IT professionals we create knowledge every day. And it’s not just yourself who is in that organization. There are hundreds and thousands who are also engaged in the process of creating new knowledge. For a large product which had been there for sometime, the knowledge base is huge and ever growing. May it be new knowledge or something which had been there for sometime, it’s always a learning curve for the person who is engaged in a particular task. The process of grasping the knowledge is not straightforward and sometimes no matter how hard you try it could be a bit frustrating to absorb everything.</p><blockquote>This is the golden moment to do documentation. Your struggle in trying to understand and absorb something is the learning, and could be valuable for many more to follow you.</blockquote><p>You still might not understand the thing you are struggling to understand. But when you are stuck at some place if you sit back, write everything down that you have observed and learned. At some point, you might actually see a way to go forth since you now see the big picture.</p><p>Even if you fail to find what you are looking for after all this, you can now go and get help from someone without wasting much of their time. This is made possible due to the documentation that you’ve built up while you were learning.</p><blockquote>This kind of writing done during a time where you were struggling for knowledge can be further improved.</blockquote><p>Since you already have a base document, without much effort it could be made publishable. The base document may be something as simple as a scribble in your notebook. But you can do the following improvements to perfect the document and shape it up so that it becomes more useful and ready for circulation.</p><ul><li>Peer review these notes and get more input as to where you went wrong</li><li>Find possible improvements or related knowledge on the same</li><li>Find related documents and link them together</li></ul><p>This is just one way of working this tricky marriage. There are many more methods out there as well. Shall we give a try to work out this marriage then? Jokes apart this is something we all can think about and work on a daily basis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a89ad85034b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Information overload : A Business Analyst’s Perspective]]></title>
            <link>https://randima-thilakarathna.medium.com/information-overload-a-business-analysts-perspective-958c3cb1b45b?source=rss-5ddb6f16b935------2</link>
            <guid isPermaLink="false">https://medium.com/p/958c3cb1b45b</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[documentation]]></category>
            <dc:creator><![CDATA[Randima Thilakarathna]]></dc:creator>
            <pubDate>Tue, 06 Mar 2018 07:52:30 GMT</pubDate>
            <atom:updated>2018-03-06T07:52:30.850Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*DklDwjZ5HrVWgfy54QchBw.jpeg" /></figure><p>Do you know how many videos are available on YouTube currently? It’s almost 5 billion and people around the world upload 3600 hours daily. The number of websites on the internet exceeded 1 billion milestone 4 years ago.</p><blockquote>The volume of information available and the mediums and sources that information is made available is immense.</blockquote><p>But for previous generations, this was not the case and the sources of information available and the amount was restricted than that of today. This difference has triggered a change in almost all industry and impacted the process of learning.</p><p>I initially took a more generic example. Let me further narrow it down and relate it to what I’m doing. I personally feel that new millennial knowledge workers are impacted more by this phenomenon. The information overload is impacting us even without knowing in our day to day lives and even in our work environments.</p><p>Me being a business analyst constantly see this first hand. Every IT system today might have started with an idea noted down on a piece of paper while trying to provide an answer to a question some user had. But that’s just the beginning. There are new requests, customization, bugs, totally new designs are added each day.</p><blockquote>To most of us Business Analysts, Software Engineers, QAs this is our day to day job. But from another point this process in generating a lot of informational output which is vital for the continuation and the future of the product being developed.</blockquote><p>This is something of greater weight than we think and if not properly understood the impact could turn out to be problematic on a higher level. It could be a simple decision that was taken some time back. Maybe it was an e-mail sent from one person to another deciding whether to use option X or Y and in the mail thread in the middle, both parties understood that option X is better than option Y due to A, B and C reason and went ahead with option Y. A simple decision taken during our day to day work may never be documented sand shared simply because it seemed trivial.</p><p>I myself make this mistake sometimes. I’m also sure that I’m not alone on this. Sometimes we fail to see the significance of a piece of information or a decision taken. The main culprit as I see is because we were so engrossed in the process we fail to see certain things as important.</p><blockquote>Without us knowing we have created knowledge and we fail to see it because for us this is some small decision which is of less importance.</blockquote><p>But 10 years down the line when there is someone new and when he or she is looking and the product, process or software that was developed our small decisions might matter and might even confuse that person at the end of the day.</p><p>I feel this is a bit grey area. If I’m to refer in relation to what I do, as business analysts we cannot go on to document everything that happens every day, right? It is not a practical approach and something not to be practiced. So it is a must to decide what should be documented, when it should be documented and how it should be documented as well. This is the tricky part. But at the end of the day there is one thing that we should do always.</p><blockquote>We should review the decisions taken, changes done and discussions as an outside person who might look at the same issue ten years down the line.</blockquote><p>I feel that we should question ourselves is this understandable for someone who is not involved in the development of the product or process from scratch? But we should always keep in mind that there</p><p>If the answer is a yes then you have done a good job and handled the information overload correctly. Well if the answer is no then there is room for development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=958c3cb1b45b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who are we?? We are Business Analysts…. Sorry. Come again ??????……..]]></title>
            <link>https://randima-thilakarathna.medium.com/who-are-we-we-are-business-analysts-sorry-come-again-2675fa959915?source=rss-5ddb6f16b935------2</link>
            <guid isPermaLink="false">https://medium.com/p/2675fa959915</guid>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[what-i-do-for-money]]></category>
            <category><![CDATA[history-of-technology]]></category>
            <dc:creator><![CDATA[Randima Thilakarathna]]></dc:creator>
            <pubDate>Fri, 16 Feb 2018 04:00:20 GMT</pubDate>
            <atom:updated>2018-02-16T04:00:20.050Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/859/1*gb_C5J69Z2UJjCYqxC0FLw.png" /></figure><p>So, what do you do now? Is a question that I get many times when I meet friends and relatives in social gatherings. When I give them the answer I’m a Business Systems Analyst I’ve noticed many times the confused look on their faces. Then I try to explain in the most basic terms what business analysis is all about and sigh…. The cycle just goes on and on, every time I meet someone new. At one point I remember giving up on the explaining aspect so that they would have their own notions that I’m doing something related to IT or that I’m a software engineer.</p><p>During one phase of my life I wanted to be a lawyer, then a doctor and finally a writer. All those professions had been there for quite sometimes and belonged to so-called “traditional career paths”. But why didn’t I have any knowledge of the profession Business Systems Analyst when growing up? I’m not sure if it is the same case Internationally. But in local context I can assure that this is the case most of the time.</p><blockquote>Why is it that our parents’ generation and many among us still seemed confused when this profession is mentioned?</blockquote><p>What I feel as reason behind this odd behavior is caused because career path Business Analyst or Business Systems Analyst was simply a newbie while our generation was growing up and as a result was never included in so-called “Traditional Career Paths”</p><p><strong><em>The Inception</em></strong></p><p>It all began in 1940’s when the world saw the birth of first computers. Till late 1970 the access and use of computers were limited to several institutions like governments, universities and other research institutes. There were many factors in the beginning of computing that led to limited use of computers for commercial use in the corporate sector. Some of the reasons being expensiveness of data storage, difficulties in accessing data, immaturity in programming languages, lack of functionality in systems and User Interfaces that were not user-friendly and so on.</p><p>Times changed quickly. The technology was advancing at such a speed that these constraints were soon overcome and by early 1980’s application of Information Technology within businesses was identified as the next big thing and a frenzy began. Everyone was really hyped and wanted to be a part of it.</p><blockquote>Information Technology was the magical spell that was discovered to drive the businesses to better performance.</blockquote><p>But what we didn’t foresee back then is that Information Technology was merely a tool and a tool would only deliver results if it was used properly and many of the businesses then failed to do this.</p><p>Many projects which started with big ambitions to align IT and business strategy for better performance, failed to deliver the desired benefits often because of a focus on delivering ‘technology’ at the expense of business needs. The business users’ requirements got lost somewhere when software engineers tried to directly interface and deliver solutions. This was because business users and software engineers spoke different languages.</p><blockquote>This gap was to be bridged. Hence this gap became the birthplace of business analysis.</blockquote><p>Later on, as business stakeholders became increasingly IT aware, the newborn role of business analyst evolved to support them in achieving their goals while constantly balancing conflicts between business needs and limited IT resources. Today it has become one of the most evolved job roles within past 2–3 decades.</p><p><strong><em>The present</em></strong></p><p>Almost two decades into the millennium we are heavily dependent on internet and placed even greater demands on IT departments which are most of the time outsourced or off-shored. Organizations themselves have become increasingly globalized, tech savvy and more complex. These changes require their IT infrastructures, often containing hundreds (even thousands) of different systems to be powerful and collaborative than ever. This is a risky move. Processed information which is an output of one system was fed to another system for planning. Things are becoming complicated than ever.</p><p>During these challenging and changing times agile emerged as a more flexible way of developing and updating IT systems in a rapid way.</p><blockquote>It is during this period, the title ‘Business Analyst’ evolved into a multipurpose job title for many project and business domains.</blockquote><p>Different branches emerged of the business analyst role, from being a strategic intellectual driving change within the organization, through acting as a process improvement expert to being responsible for eliciting and documenting requirements for IT systems.</p><p><strong><em>Who we are and what we do</em></strong></p><p>Our role today has different names. Business analyst, system analyst, business system analyst, functional consultant and so on. But all of them point in the same direction when defined in an elaborative manner. We have the business domain on one side. We have the technological domain on the other side and we as business analysts stand in between assessing the two domains and trying to integrate in an optimum manner.</p><blockquote>Today, our profession is widespread. We exist in a lot of industries such as Software, finance, banking, insurance, telecom, utilities and so on.</blockquote><p>But I must say that there is a certain level of ambiguity when it comes to the specific responsibilities of our job role as this varies by organization and by industry. But as I see this it is an opportunity the Business Analyst job role has. We as business analysts work with a certain level of abstraction. This actually makes it easier for us to switch between industries if we have properly mastered the art of business analysis.</p><blockquote>All in all, Business Analyst profession had come a long way since inception and had developed rapidly during last three decades with the boom in the use of Information Technology in the business domain.</blockquote><p>It will keep on expanding until new advancements that collaborate the business and IT domain are available to us. It’s understandable why we when growing up as a generation didn’t see this profession as a career path. But as the trend goes I think soon there will be times that some child in a classroom will tell the teacher that he/she wants to be a Business Analyst.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2675fa959915" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>