Home

User Story Examples and User Stories

Let us observe some user story examples here. It helps us to provide overview how to write user stories.

User Story Examples
User Story Examples

Feature: Refund item

Scenario: XYZ returns a faulty item


Given XYZ has bought a item for so and so amount
And he/ she has a receipt
When he/ She returns the item
Then XYZ should be refunded with so and so amount

Scenario: User enters correct user name and password


Given that I am on the sign-in page
When I enter my user name and password correctly
And click ‘Sign In’
Then I am taken to the dashboard

 Scenario: User does NOT enter correct user name and password


Given that I am on the sign-in page
When I enter my user name and password incorrectly
and click ‘Sign In’
Then I see an error message ‘Sorry, incorrect user name or password.”

User Story:

As a Branch User

I want to upload customer documents into DMS

So that I can view or retrieve documents when required.

Scenario:  User uploads a document

Given a document is uploaded,

When the upload request is received

Then allow the upload if the file name is one of the following: (file list here)

Allowed file names: Account opening form, PAN, Voter ID, Passport.

Scenario: Upload documents into DMS (Data Management System)

Given that the CRT Customer Profile is created,

When the documents are uploaded,

Then send all the uploaded documents to DMS (Data Management System)

Scenario: Ensure so and so documents have been uploaded.

Given a document is uploaded,

When the upload request is received

Then ensure to maintain what documents received and what documents uploaded.

Scenario: File size of each document is between x and y kb

Given a document is uploaded,

When the upload request is received

Then allow the upload if the document size is between x and y kb

Scenario:  Document format/type is so and so

Given a document is uploaded,

When the upload request is received

Then allow the upload if the document format / or type is so and so.

Allowed file formats: .pdf,  .tif  .jpg

UC2:  User should be notified with successful upload of documents.

User Story:

As a Branch User

I want to get notification when documents successfully uploaded.

So that I can ensure that documents successfully uploaded into DMS.

Scenario: Documents uploaded successfully

Given a document is uploaded successfully

When the uploaded request is received

Then user should get notification as “Document uploaded successfully”

It should be done via SMS or mail id.

I mentioned some of the user story examples above.

Sample BA Document Templates

FREE DOWNLOAD

Send download link to:

I confirm that I have read and agree to the Privacy Policy.

Subscribe to get exclusive content and recommendations every month. You can unsubscribe anytime.

What is Requirement Traceability Matrix (RTM)?

What is Requirement Traceability Matrix (RTM)?

What is Requirements Traceability Matrix
What is Requirements Traceability Matrix

Requirement Traceability Matrix (RTM) is a document, we can prepare in simple excel format also, it maps and traces client requirement with test cases. It captures all requirements given by the client/ Captured in BRD or FRD/FSD. The main goal of Requirement Traceability Matrix is to verify that all requirements are checked via test cases so that no functionality is unchecked during Software testing.

Why Requirement traceability matrix or RTM is required?

A Requirement traceability matrix is used to record and track the relationship of the project requirements to the design, documentation, development, testing and release of the project/product. This is done by maintaining an excel sheet which lists the complete user and system requirements for the system (in form of use cases) which are in turn mapped to the respective documents like Functional Requirement, Design Document, Software Module, Test Case Number, etc.

An RTM is maintained throughout the lifecycle of the various releases in a project and it’s a vital document to track project scope, requirements and changes in any project.

The Requirement Traceability Matrix or RTM Contains below:

  • Requirement ID
  • Requirement Description
  • Functional Requirement
  • Status
  • Architectural/Design Document
  • Technical Specification
  • Software Module
  • Test Case Number
  • Tested In

Why Requirement Traceability Matrix (RTM) is needed?

  • Requirements Traceability Matrix (RTM)is used to trace the requirements.
  • To test all the test cases.
  • To ensure all the requirements are covered and tested/verified.
  • By using Requirements Traceability Matrix (RTM), we can able to identify if any requirement is not covered.
  • It helps to cover the all the requirements and all are validated and tested as per the requirement.

What is the Advantage of Requirements Traceability Matrix (RTM):

  1. We can ensure all the test cases covered.
  2. It allows to identify the missing functionality easily
  3. It is easy to track the overall test execution status
  4. It allows updating the test cases if any change in requirements or any change request comes.
  5. We can ensure all the requirements covered and tested.
  6. It helps to improve the quality of the product.
  7. As we covered most of the test scenarios it helps to improve the client satisfaction.
  8. As we tested most of the test scenarios it helps to avoid the escalation from the client.

Sample BA Document Templates

FREE DOWNLOAD

Send download link to:

I confirm that I have read and agree to the Privacy Policy.

Subscribe to get exclusive content and recommendations every month. You can unsubscribe anytime.

Why Requirements Traceability Matrix  or RTM is Important?

The main responsibility of Testers or QA team to understand the Business Requirements/ Client requirements. And they need to test the application end to end. And team responsible to deliver the product without bugs or Defects. To achieve this goal, every QA or Tester should understand the requirement clearly and create positive and negative test cases.

Requirements provided by the client should be split into different scenarios. And Team needs to prepare or write the test cases as per the requirements, Team ensures to cover all the requirements and scenarios when writing test cases. Once team writes the test cases then team starts the testing for each Test Case. Each of this Test case must be executed individually.

How testing team or QA team will ensure to test all scenarios.

Here we may think that how testing team/ QA team to make sure that the requirement is tested considering all possible scenarios/cases? How to ensure that any requirement is not left out of the testing cycle?

A simple way is to trace the requirement with its corresponding test scenarios and test cases which team already written the test cases.

The traceability matrix is simply a worksheet that contains the requirements with its all possible test scenarios and cases and their current state, i.e. if they have been passed or failed. This would help the testing team to understand the level of testing activities done for the specific product.

I hope this article helped you to provide overview on what is Requirements Traceability Matrix  or RTM.

To know more about what is Requirements Traceability Matrix you can browse on Google to get more knowledge.

In a Business Analyst view this article is enough to understand what is Requirements Traceability Matrix or RTM.

Sample BA Document Templates

FREE DOWNLOAD

Send download link to:

I confirm that I have read and agree to the Privacy Policy.

Subscribe to get exclusive content and recommendations every month. You can unsubscribe anytime.

FAQ’s

What is requirement traceability matrix with example?

Requirement Traceability Matrix (RTM) is a document that maps and traces user requirement with test cases. It captures all requirements proposed by the client and requirement traceability in a single document, delivered at the conclusion of the Software devlopement life cycle

What is the purpose of the requirements traceability matrix?

A requirements traceability matrix is a document that demonstrates the relationship between requirements and other artifacts. It’s used to prove that requirements have been fulfilled. And it typically documents requirements, tests, test results, and issues.

What are the 3 types of requirements traceability?

There are three types of RTM: forward traceability, backward traceability, and bidirectional traceability

What are the four types of requirements traceability?

The Four Types of Derived Requirements Traceability
Forward to Requirements. When customer needs evolve, requirements may have to be adjusted in response. …
Backward From Requirements. …
Forward From Requirements. …
Backward to Requirements. …

Who prepares RTM?

#1) Business Requirements

It is usually prepared by ‘Business Analysts’ or the project ‘Architect’ (depending upon organization or project structure)

What is RTM tool?

In a software development project, Requirements Traceability Matrix (RTM) is a document which is used to validate that all the requirements are linked to test cases. … A Requirements Traceability Matrix is usually in tabular format as it holds multiple relationships between requirements and test cases

How do you create a requirement traceability matrix?

How to Create a Traceability Matrix in Excel
Define Your Goal. …
Gather Your Artifacts. …
Create a Traceability Matrix Template in Excel. …
Copy and Paste Requirements From Your Requirements Document. …
Copy and Paste Test Cases From Your Test Case Document. …
Copy and Paste Test Results and Issues (If You Have Them)

Is RTM required in agile?

In agile there are no requirements but stories, so traceability matrix does not exist in traditional sense. Well, stories describe requirements but when you complete story, you close it and then you close an iteration and forget about that story. It is done, accepted, and closed.

Which phase is RTM prepared?

To answer your first point, RTM is something that is prepared as and when the requirements are ready. If you plan to adopt a practice of creating RTM in your project, you can mention this point in your Test Plan irrespective of the fact that it is created or not. Test Plan and RTM are not related.

What are Scrum Meetings?

What are Scrum Meetings

What are Scrum Meetings
What are Scrum Meetings

We discussed and observed what is Scrum and Scrum Roles, now we look into some other important terms and terminology. That is what is Sprint and what are Scrum Meetings  and what team discuss in Scrum Meetings.

What is Sprint Zero?

What is Sprint Planning?

We can say Sprint is nothing but Time Frame. Team discusses and decides what the prioritized items are and how much effort required achieving that. For example 3 user stories/ Requirements prioritized items are in product backlog, so team discuss about these three user stories, how much effort required and  how many man days required to complete these prioritized user stories in this sprint.

For example Sprint duration is 2 weeks, and then team needs to complete those 3 user stories within this time frame, which includes, Design > Development > Test > Integrate.

Scrum Meetings:

Daily Scrum Meeting: This happens every day where team will just discuss on 3 questions. Everyone should participate in this meeting, and meeting should be completed in 15 to 30 minutes.

  1. What did you do yesterday?

Here you need to explain what you have done yesterday and what the status of tasks assigned to you is.

  1. What will you do today?

Here you need to explain what you will do today to complete the assigned task as per schedule.

  1. Is there any impediments stopping you?

Here you need to explain if you are facing any issues to complete the assigned task. For example your task is depending on another task or functionality and it is pending with some other team. Then you need to explain the same in meeting, then Scrum Master will take a call and discuss with the concerned team to resolve the issue.  Scrum Master Note down these points and discuss offline with concerned teams.

These questions are depending on your scheduled Daily Scrum Meeting. For example if your meeting is at Morning then above questions will applicable.

If your meeting is scheduled at evening then questions as below.

  1. What did you do today?
  2. What will you do tomorrow?
  3. Is there any impediments stopping you?

Every team member of the team should participate in this meeting and need to update the status. As every individual team member should participate in this meeting, Scrum Master will discuss with individuals and schedule meeting as per convenient time.

For example you are working on Indian standard time as you are in India, but if your development team in some other country, then Scrum Master should coordinate and schedule meeting as per convenient time, and Scrum Master is the responsible person to ensure every team member joins in meeting.

Sprint Review Meeting or Scrum Review Meeting: This will happen at the end of the sprint where team will give demo on completed stories to product owner. As per above example Sprint completed in two weeks, then team will have this meeting and give demo on developed product. Usually it will take 3 to 4 hours.

Sprint retrospective Meeting: This will happen at the end of the sprint where team will answer these 3 questions.

What went well in the sprint?

What did not go well?

What are the required areas of improvements in next sprint?

This is continuous process, team discuss at the end of every sprint to improve the quality.

You may get this question in interviews also what are scrum meetings and what team will do in these meetings.

I hope it helped to provide overview of What are Scrum Meetings.

To know more about what are scrum meetings and what is scrum we can visit scrum official website.

What is Scrum in agile methodology?

What is Scrum?

What is Scrum

Scrum:  Scrum is not a methodology, Scrum is a framework. That means it provides opportunity to work as per the project needs or requirements with cross functional team to reach the project goals. It helps us to interact with the people easily.

Scrum is very popular now days and we can say without putting Agile  in your resume you will not get even interview calls also.  Don’t worry and do not think too much to understand what is scrum. Let us discuss in simple words.

Mostly it will use in implementation of projects.

When we are discussing about Scrum, we should understand and remember the ScrumTerminology and terms used. I am trying to explain in simple way.

Product Backlog:

Need to prepare the product backlog, it contains the list of user stories, user story is nothing but requirements.

Once we prepare the Product backlog, will prioritize the user stories which can be implemented in this Sprint.

ScrumRoles:
  1. Product Owner(PO)

    : He will decide what needs to done in this sprint/project and he is the responsible for managing the product backlog. He will be the responsible person for product like how product should be and all.

  2. He interacts with Business Analysts and Customers. This role may be played by BA or any person who is having strong knowledge on product and who works with end users for a long time. Depends on the project client also may play this role.
  1. ScrumMaster (SM)

    He will monitor the performance of the team within the sprint. Team will raise all their concerns and issues to ScrumMaster.

  • He is responsible to provide solutions to the team. He will interact with the stake holders to address the issues and concerns raised by the team. This role can be played by any person in team usually Business Analyst will play this role.
  • Development Team (Cross functional team who are self organized)

Scrum Team: Resources who are working in this project are formed as Scrum team which comprises of Business Analyst, Developers and Testers.

If you are looking for Certification, you can refer scrum.org

Business Analyst Job Description Insurance Domain

Business Analyst Job Description Insurance Domain

Business Analyst Job Description Insurance Domain
                        Business Analyst Job Description Insurance Domain

General Accountabilities:

– The Senior Business Systems Analysts will provide technical support and advice to the Client Relationship Managers, Service Managers and/or Operations Executives on business processes and systems issues in both run mode and development of new processes/support. Sr.BSA may also become key resources potentially available to support new clients through block conversions.

– Analysts are liaisons between operations and other areas such as Information Technology, Finance, Marketing, etc. to ensure sound business solutions are formed and implemented with quality. Sr.BSA’s are responsible for facilitating the flow of ideas and information between departments

Duties and Responsibilities:

– Facilitating business need identification

– Completing research and providing analysis as needed to support Management in decision making

– Developing and executing proposed business and technical solutions

– Developing business requirements for the business/technology solutions that will allow the client and internal customer departments to become more efficient and effective

– Largely able to independently write unambiguous, verified requirements to a testable level (functional and non-functional requirements)

– Creation of artifacts such as Illustrationinput, output requirements, Test strategy, Validation rules, Unit Test cases etc;

– Estimating implementation costs and efforts

– Attend client meetings and assist in the coordination of Solution Definition

– Assist Technology Solutions teams in documenting scope, defining gaps and updating implementation estimates

– Documenting flows and procedures for Performance Quality as a results of implementations

– Ensuring quality of solutions delivered (leading user acceptance testing)

– Identifying, developing and executing continuous improvement opportunities

– Other support to operations areas as identified

Experience required:

– 7 – 10 years- work experience in systems or quantitative analysis and business solutions development

– 5+ years- experience in US life insurance products (i.e. In forced Whole Life, Term Life,). Should be able todemonstrate life insurance industry knowledge

– Understanding of various applications used in life insurance industry including Policy administration system, agent management system or peripheral application including web portals.

– Work experience inInforce Illustration is mandatory (Inforce business projection knowledge)

– Strong customer service skills with excellent relationship management skills with the ability to interact positively and successfully with all level of associates and managers to meet business needs

– Basic understanding of technology system interfaces and data integration, networks, and operating systems

– Knowledge of Business Process Modeling using decision tables/trees and data flows, etc.

– Work experience or an education in programming and also knowledge in database

– Microsoft PC software experience (i.e., Excel, Word, Access and Project)

– Experience in project management and/or client/block conversions

– Must be a self-starter, flexible and motivated

– Analytical, organized with excellent written and verbal communication skills

– Willingness to develop industry-related knowledge

– Proven application of analytical skills and solution focused mindset

– Familiarity with project management methods (SDLC, PMI, ITIL, Agile, Waterfall, etc.)

Qualifications :

Should have BE/BTech/MCA or MBA qualification from reputed instituteswork experience in business analysis and application development

– Insurance certifications such as LOMA / FLMI / AAPA / CLU

– CBAP (Certified Business Analyst Professional) certification preferred

I hope it helped you to provide overview of Business Analyst Job Description Insurance Domain

Business Analyst Job Description in Health Care

Business Analyst Job Description in Health Care

Business Analyst Job Description in Health Care

The Business Analyst is required to have good experience in implementing software systems in healthcare domain. He/she should have an experience in creating requirement specification and testing and has good communication skills.

Duties and Responsibilities:

Identify software product needs and create requirements in the form of business specification and use case documents.

Closely work with the client and the software development team in developing the product.

Carry out the testing from the end user perspective before releasing for UAT.

Manage the scope of development in order to align with the business and the project needs.

Create and carry out product demos to the client.

Maintain traceability of requirements to ensure 100% test coverage.

Ensure the accurate deployment of solutions through review of problem logs, assistance with test plans and test matrices and other analysis activities.

Facilitate the transfer of knowledge about the direction of the business units to others who support them.

Take lead in enterprise level initiatives and drive them from the requirement perspective.

Proactively track developments in healthcare IT, including standards, technologies and workflows.

Key Technical Skills and Knowledge:

Healthcare/RCM domain knowledge ( Medical Billing / Medical Coding/ Accounts Receivable ,Rejections, Appeal

Schedule meets with stake holder/ requester

Understand requirements

Prepare requirement documents

Explain requirements to Testers

Good communication skills

Should have knowledge of MS Office (Word, Excel, PPT)

Knowledge of AI / ML / NLP/ OCR is added advantage

It helps to provide overview of Business Analyst Job Description in Health Care

Business Analyst Job Description in Payments

Business Analyst Job Description in Payments

Business Analyst Job Description in Payments
Business Analyst Job Description in Payments

  • Should be able to participate in bank meetings to understand complex requirements or to explain functionality
  • Should assist the project manager and project test manager of delivery projects
  • Is responsible for creating the documentation of high level requirement (HLR) according to the project process
  • Is responsible for any change in functional scope
  • Should present change request to project manager
  • Is responsible for approving team implementation plan together with project test manager and project architects
  • Is required to respond to any questions or clarifications during development, test case preparations and testing and the SMEs should answer questions on issues that can not be solved by the BA?s in the development teams
  • Should participate in planning and tracking
  • Participate in FAT
  • Responsible for describing requirements according to project mission and project master plan
    Tasks:
  • Conducts requirements analysis
  • Create HLR
  • Create work packages and user stories
  • Must define all requirements according to the project process and get them verified by the project manager
  • Get input on described requirements from project architect and test manager
  • Communicate functional scope and requirements to the teams through: Documentation (High level requirements, Capability documents, Flow charts)
  • Makes sure that understanding of functional scope and requirements is verified through quality assurance of team implementation plan
  • Should ensure the requirements are understood by the teams
  • Is responsible for identifying and describing dependencies together with the BA?s and the SME should communicate these dependencies to the SME in the dependent project
  • Is responsible for transferring the functional knowledge of the HLR to the team writing the user stories
  • Should assist in planning and tracking
  • Participate in meetings with the customer
  • Participate in FAT planning and execution
    Competence/Tools / Technology:
    Required:
  • International banking/payment
  • SEPA
  • ISO20022
  • SWIFT
  • AccountingSkills / Experience:
  • 5 years relevant experience
  • Strong domain knowledge payment/banking
  • Requirements analysis and specifications
  • Understand complex value chains and integrations between several systems
  • Understand the bank and customers needs
  • Experience from Agile Project Methodology
  • Excellent communication/collaboration skills
  • Fluent industry language skills in English
  • Structured and process oriented
  • Able to work distributed and in global and multi-cultural teams

I hope it helped you to understand the Business Analyst Job Description in Payments

Business Analyst Job Description BFSI

Business Analyst Job Description BFSI

Business Analyst Job Description BFSI
Business Analyst Job Description BFSI

Business Analyst Job Description BFSI

  • Act as an SME in area of Financial Crime Compliance for all Corporate and Income events
  • Should have strong understanding on various Data Governance model and Data Quality
  • Exception handling of automated interfaces
  • Identify, capture, and track voluntary corporate actions
  • Exception handling on events transactions
  • Coordinate with IT support teams in case of any IT related issues impacting BAU
  • Building core knowledge in team during set up and shaping activities as well running projects, working closely with Operation Leads
  • Ensure the team is resourced with sufficient well trained and well-motivated staff, and are developed to their potential in line with current and predicted operational needs
  • To effectively shape and manage process for the client, ensuring a high level of quality performance across projects.
  • Act as a KYC subject matter expert on compliance, regulatory regulations and global KYC requirements
  • Well verse with KYC documents and good understanding on regulators mainly of US and UK OCC, FATCA, USA PATRIOT ACT, BSA, EU Directives, MIFID I/II
  • Maintaining an external focus and strong network within the industry to identify trends in the project
  • Maintenance of Service Levels in department and by overall engagement, ensuring a high level of customer service at all time
  • Identify and diagnose sub-optimal business performance
  • Reporting of issues of concern to Operations Support, Senior Leadership, and where appropriate, to the client
  • Initiate and promote improvements to processes and techniques to achieve higher levels of efficiency and effectiveness and to maximise productivity gains
  • Aim to operate at industry best practice level, where available
  • Constantly seek opportunities to digitize the existing process
  • Aim to operate at industry best practice level, where available
  • Min 10+ years in an operational environment (KYC/AML/CDD/EDD) domain, with strong knowledge of various Corporate Actions
  • Clear vision, understanding and proven track records of in Risk and Investment Banking Domain
  • Strong analytical and problem-solving skills and the ability to use information to generate creative solutions to benefit the business.
  • Strong in excel and advance excel
  • Good to have SQL knowledge
  • Strong communication and relationship management skills.
  • Strong presentation skills

I believe it helped you to provide the overview of Business Analyst Job Description BFSI domain

Business Analyst Job Description & Career Profile: IT

Business Analyst Job Description: IT

Let us observe the sample Business Analyst Job Description.

The Business Analyst (BA) acts as a liaison between either a development group and an external client/vendor, or a development group and an internal business sponsor. The BA is responsible for the collection/analysis, authoring, and communication of requirements in order to satisfy the client/sponsors needs. Depending on the nature of the project, the BA may also undertake a combination of project management, technical implementation and testing analyst tasks. The BA is expected to have either a strong proprietary knowledge base or multiple years of previous BA experience in requirements analysis and authoring. The Lead Business Analyst is additionally expected to exhibit strong leadership in many areas including defining/improving standards, mentoring other Senior and Associate BAs, and implementation / project management of critical projects.

Major Responsibilities / Accountabilities

  • Develops and improves business processes within the technology and business organizations and understands client requirements, specifying and analyzing these to a sufficient level of detail to ensure clarity of definition. Collects, writes formal specifications and communicates business requirements between development and client to design and implement business solutions.
  • Responsible for building and maintaining a relationship with Data Provider e.g. Exchanges, Contributors.
  • Responsible for the collection, analysis and documentation of a client’s business needs and requirements.
  • Participates in short term planning sessions with a client to improve a business process within an assigned client area.
  • Uses a structured requirements process to assess near-term needs.
  • Uses a structured change management process to shepherd projects from requirements gathering through design, testing, implementation, client transition and on-going systems maintenance
  • Provides business process and systems analysis, requirements specifications, consult on development and testing management for implementing technology-based editorial business solutions focusing on increasing productivity, data accuracy, automation and efficiency while reducing redundancy and costs.
  • Responsible for modelling and analysing client and system processes in order to identify opportunities for technological improvements, process synergies, and business efficiencies
  • Identify, recommend and develop methods, tools and metrics for client business process and systems operational support
  • Provide client systems support in order to resolve issues and contribute to on-going systems maintenance and evolution.
  • Identifies business priorities and advises client on options.
  • Ensures change management and communication of change is done in a systematic way for projects where initial requirements may evolve during the lifecycle of the project.
  • Responsible for generating systems documentation for operational support and end user information. Conducts operational and end user training and support transitions of operational support to client.
  • Develops relationships with a client by being proactive, displays a thorough understanding of their business, and provides innovative business solutions. Works with clients to ensure smooth transitions to new systems and/or business processes.
  • Develops a basic awareness and understanding of Thomson Reuters technologies, products, and services.
  • Recommends metrics to ensure customer satisfaction.

Scope and Impact

  • Performs work within several business segments, engaging in moderate to complex business processes across multiple business processes or segments of the business.
  • Project team member for projects of medium to large scope and moderate to high complexity projects.
  • Responsible for coordinating work of development teams, business clients and others and be accountable for the work delivered. Fully responsible for quality of own work, and possibly some accountability for more junior members of the team.
  • Responsible for managing projects through the development lifecycle including requirements gathering, functional specifications, testing, implementation, training, transition and maintenance.
  • May be involved in defining and managing requirements for implementation by remote or third party teams.
  • Responsible for management of own time, and coaching/mentoring more junior team members.
  • Responsible for estimating effort required for own work, and checking other team member estimates.
  • Able to plan tasks necessary to lead to the production of adequate business and system functional requirements.
  • Accountable for compliance with agreed policies, standards and procedures.

Skills

  • Demonstrated expertise in requirements management best practice and ensures these practices are used.
  • Demonstrated expertise in business process re-engineering
  • Demonstrated expertise in business process analytics and understanding of six-sigma process improvement techniques
  • Demonstrated expertise in Business Process Modelling preferable with experience in Oracle BPMS/BAM nomenclature & tool sets
  • Experience working with an Agile development methodology
  • Experience working with a globally distributed team of customers, stakeholders, business owners, developers and QA staff
  • Experience working with a Services-oriented application architecture
  • Understands principles in performance requirements and helps formulate Key Performance Indicators for a project.
  • Understands principles of usability and helps ensure products are fit for purpose.
  • Understands the effects of technology used within Development, and the impact on the business client.
  • Understands basic financial information and markets and the future direction of the industry.
  • Understands the development organization and other specialized areas such as Product Management and Data and future direction of the business for an assigned client area

Relationships: Internal / External

  • Development leads (e.g. Managers, Project Managers, Project Leaders, Technical Leads)
  • Architects
  • Development staff
  • Third party Development Leads & Architects
  • Customer Segments
  • Customer Segment Partners
  • Data Providers
  • May include external clients, Capability Managers and Business users.

Professional Experience

Must have a solid understanding of the client’s existing business processes, the key drivers and measures of success of the business, and the short and long term direction of the business and technology. Demonstrated ability to understand project business requirements and facilitate implementation of team member’s understanding of these as well. Demonstrated expertise in information systems, business operations, requirements analysis, and integration/design of client solutions. Needs to have a high level understanding of the overall Thomson Reuters Development or internal systems architecture in order to understand the issues & implications of proposed systems & hardware solutions. Requires some relevant technical or business work experience, ideally a background in business area supported. Requires experience with and understanding of Business Operations and requirement management processes, as well as expertise business modeling concepts utilizing BPMS . Must have experience in information systems, development life cycle, Agile development methodology, business process development and leadership skills. Must have exceptional communication skills, ability to work independently and drive for results.

Must have experience

  • Are senior level with ~5+ year experience as a business/system analyst
  • Have experience with new product development
  • Experienced in an environment where the BA drives from Ideation through requirements/specifications, supports dev & QA, supports UAT, supports/guides business implementation
  • Experience with back-end specifications/ technical requirements (Databases, API, services, service integration, JSON/message queues)

I hope it provided you the overview of Business Analyst Job Description.

What is JIRA Tool ?

What is JIRA Tool?

What is JIRA

What is JIRA?

Initially I was also thinking what is JIRA and how to use JIRA, JIRA is a project management tool. It can be used to track the requirements status like what is the current status of the requirement assigned to user whether it is open or closed or under processing.

We will discuss in detail what is JIRA and advantages of using JIRA?

Here I am not going to explain how to use JIRA and all, I am trying to provide overview about JIRA tool.

What is JIRA?

JIRAis a tool developed by Australian Company Atlassian. This software is used for bug tracking, issue tracking, and project management. The name “JIRA” is actually inherited from the Japanese word “Gojira” which means “Godzilla”. The basic use of this tool is to track issue and bugs related to our project.

Jira is especially useful for software development because it has built in templates that can be used to help you create a software development project.

For example Jira has a Scrum template that can be customized to fit in with your requirements.

The template can be used to create the development project, once your development project is created, then you can create your backlog, plan your sprints, and your software releases.

A Scrum board would also be created with different columns. The columns show the different status that the cards are in such as backlog, development, Quality Assurance (Q & A), demo and closed which shows the status of the cards.

A kanban board also already available, we can customize as per our requirement. We can use Scrum board or Kanban board as per our requirement.

Has below standard formats.

  • Scrum board tracking.
  • Kanban board tracking
  • Cumulative flow charts.
  • Burn down charts.
  • Sprint reports.

We can create customized boards as per our requirement. It helps us to understand how many tasks we have and what the status of each task is.

Assume we have 5 developers in our team, and we have 50 requirements in our hand, and out of 50 requirements 20 prioritized. So here we need to assign these tasks to our developers.

So here I can customize the boards and fields as per my requirement. If we observe in above example 30 requirements yet to prioritized so I can mark status as “to be process” and 20 requirements I need to assign to my developers. So we can assign 4 tasks to each of the developers and I can give the due dates also as per the requirement.

As per above example 4 I  assigned to X and 4 assigned to Z, so here I can track the requirements x is having how many tasks in his bucket and how much time required to complete the task and actual hours taken to complete the task.

We can track the same for Issues also.

Issue Tracking : Jira can also be used to track issues during software development. It can be used to identify and create new issue tasks, prioritize issues for completion, and track them using a workflow.

You can specify details about the issue which helps with replications and resolution.

Time tracking: Jira can be used to keep track of the the time spent on tasks and issues. This would help with future sprints planning. The time tracking views available include :

  • Working hours per day
  • Working hours per week

WorkFlows

A JIRA workflow is a set of statuses and transitions that an issue goes through during its lifecycle. JIRA workflow encompasses five main stages once the issue is created.

  • Open Issue
  • Resolved Issue
  • InProgress Issue
  • ReOpened Issue
  • Close Issue
error

Enjoy this blog? Please spread the word :)