Blog Posts

"Essential Accessories for a Successful Requirements Elicitation Interview: A Visual Guide"

17/12/2023

Requirements Elicitation: Interview Accessories

Requirements elicitation interviews are crucial in understanding client needs for a project. Having the right accessories can significantly enhance the efficiency and effectiveness of these interviews. Here are some key accessories and a brief description of each:

Notepad and Pens: Essential for taking notes, a notepad and pens ensure you capture all details accurately. Digital notepads or tablets with stylus pens are also popular for their convenience and ability to store notes electronically.
Voice Recorder: A voice recorder captures the entire conversation, allowing you to focus on the discussion without missing any details. It's useful for reviewing specific points later and ensuring nothing is overlooked.
Laptop/Tablet: A laptop or tablet is vital for accessing documents, presentations, and software tools during the interview. It can also be used to show examples, prototypes, or to take digital notes.
Project Documentation: This includes any existing project briefs, specifications, or related documents. Having these on hand helps in referencing specific details and ensuring alignment with current project goals.
Question List: A pre-prepared list of questions ensures that all critical topics are covered during the interview. It serves as a guide to steer the conversation and make sure all necessary information is gathered.
Whiteboard and Markers: For in-person interviews, a whiteboard is a great tool for brainstorming, diagramming processes, and visually capturing ideas. It facilitates interactive discussion and helps in explaining complex concepts.
Internet Connection (Wi-Fi/Dongle): Reliable internet access is crucial, especially for accessing cloud-based documents, conducting online research during the interview, or for any web-based demonstration.
Business Cards: Exchanging business cards at the beginning of the interview helps in establishing a professional connection and facilitates future communication.
Printed Handouts: These can include agendas, diagrams, or any other relevant material that you want to discuss. Handouts are useful for providing a tangible reference for participants during and after the interview.
Refreshments: Offering refreshments can create a more relaxed and comfortable environment, especially for longer interviews. This can encourage open and honest communication.

0 Comments

Requirements Elicitation - A Throwback Memory

17/12/2023

0 Comments

On a clear, vibrant morning in Tokyo, with the majestic Tokyo Tower in full view from the conference room, I was about to lead a critical session for an Insurance Policy Management System implementation. As an Indian Business Analyst & Product Implementer, this was a significant milestone in my career, especially considering the international scope of the project.

My audience was a group of four attentive Japanese clients, each a key decision-maker from a top-tier insurance company in Japan. Known for their precision and high standards, they represented a challenging yet exciting opportunity. Dressed in formal business attire, I felt a sense of determination as I prepared to present our general insurance product capabilities.

The session began with the customary exchange of business cards and respectful bowing, an elegant dance of professional courtesy. I initiated the discussion by outlining our objectives, emphasizing the system's capacity to streamline their current insurance policy management processes.

As the presentation unfolded, I could sense their keen interest peppered with a healthy dose of skepticism. Discussing complex features like policy underwriting, claim management, and customer data security, I was mindful of the linguistic nuances and the importance of clarity and communication in such a high-stakes environment. A pivotal moment came when I demonstrated how our system could seamlessly satisfy Japanese regulatory requirements on policy premium calculations. One client, Mr. Takahashi, noted how this feature resonated with a key requirement of the Japanese Insurance industry i.e.. changing insurance rating tables and introduction of custom insurance products to the insureds. This opened a floodgate of engaging discussions, blending technical specifics with country specific insights.

We found common ground in our mutual commitment to precision and excellence. Our conversation expanded beyond the confines of insurance technology, touching upon the parallels between our diverse business cultures. It was enlightening to see how our different perspectives could converge to innovate in the insurance sector.

The atmosphere in the room shifted from formal to collaborative as we delved deeper into the potential of the system to enhance their operations. The Tokyo Tower outside, a symbol of modernity and resilience, mirrored our own journey in that room – blending tradition with innovation.
As the session concluded, we had not only tailored an implementation plan but also fostered a sense of mutual respect and partnership. We captured this moment of cross-cultural collaboration with a group photo, the Tokyo Tower standing tall in the background.
Leaving the meeting, I reflected on the day's success. It wasn't just about bridging technological gaps; it was about connecting worlds – understanding each other's cultures and building enduring relationships. That day, under the watchful gaze of the Tokyo Tower, we laid the foundation for a project that was as much about people and cultures as it was about technology in the insurance sector.
Late during the day it was time to prepare the feedback report to for my Project Director present in India,

0 Comments

Prominent Software Project Documents organized across Project Phases

14/11/2023

In this post we have listed these documents only. In subsequent posts we will briefly explain the intent, purpose and importance of these documents.

Use Case Description 3 Examples with Free Use Case Template

3/11/2023

Use Case Description Examples with Free Use Case TemplatePicture

Use Case Diagram for Food Delivery App

Use Case Description Example 1: "Make Payment By Credit Card" use case for a Mobile E-Commerce Food Delivery project:

Use Case ID and Name:

ID: UC-01
Name: Make Payment By Credit Card

Author:

[Author's Name]

Date Created:

[Creation Date]

Primary Actor:

Customer

Secondary Actors:

Payment Gateway

Description:

This use case describes the process of a customer making a payment using a credit card to complete an order for food delivery through a mobile e-commerce application.

Trigger:

The customer confirms the order and chooses to make the payment using a credit card.

Preconditions:

PRE-1: The customer has added items to their cart and proceeded to the checkout.

Postconditions:

POST-1: The payment is successfully processed, and the order is placed.

Normal Flow:

The customer selects the "Make Payment By Credit Card" option during the checkout process.
The system prompts the customer to enter their credit card information, including card number, expiration date, and CVV.
The customer enters the required credit card information.
The system validates the credit card information and checks for available funds.
If the validation is successful, the system sends a request to the Payment Gateway.
The Payment Gateway processes the payment and sends back a confirmation of the transaction.
The system updates the order status to "Paid."
The system confirms the order and provides an order confirmation to the customer.
The customer receives an order confirmation with details of the payment.

Alternative Flows:

None

Exceptions:

1. If the credit card information is invalid or the payment is declined, the system informs the customer, and they can retry or choose an alternative payment method.

Priority:

High

Business Rules:

BR-1: The system must use a secure and trusted Payment Gateway for processing credit card payments.
BR-2: The customer's credit card information should be encrypted and securely stored.

Assumptions:

AS-1: The customer has already added items to their cart and proceeded to the checkout.
AS-2: The Payment Gateway is available and operational.
AS-3: The credit card payment process complies with all legal and regulatory requirements.

Other Information:

This use case is a critical part of the mobile e-commerce food delivery system and involves sensitive financial information. Security and compliance with payment processing regulations are of utmost importance.

Use Case Description Example 2: "Register on Mobile App" use case for a Mobile E-Commerce Food Delivery project:

Use Case ID and Name:

ID: UC-02
Name: Registration on the App

Author:

[Author's Name]

Date Created:

[Creation Date]

Primary Actor:

Customer

Secondary Actors:

None

Description:

This use case describes the process of a customer registering on the mobile e-commerce food delivery application to create an account.

Trigger:

The customer launches the mobile app for the first time or chooses the registration option.

Preconditions:

PRE-1: The mobile app is installed on the customer's device.
PRE-2: The customer is not already registered with the application.

Postconditions:

POST-1: The customer's registration information is successfully recorded, and they have an active account in the application.

Normal Flow:

The customer launches the mobile app.
The customer selects the "Register" or "Sign Up" option.
The system presents a registration form with fields for the customer to enter their information, such as name, email, phone number, and password.
The customer enters their registration information.
The system validates the entered information for completeness and uniqueness (e.g., checking for duplicate email addresses).
If the validation is successful, the system creates a new customer account and records the registration information.
The system sends a confirmation to the customer, welcoming them to the application and confirming their registration.

Alternative Flows:

None

Exceptions:

1. If the registration information is incomplete or contains errors, the system informs the customer and prompts them to correct the information.
1. If the customer attempts to register with an email that is already in use, the system informs the customer to choose a different email address.

Priority:

High

Business Rules:

BR-1: Customer registration information should be stored securely and in compliance with data protection regulations.
BR-2: Passwords should meet security requirements, including complexity and encryption.

Assumptions:

AS-1: The customer has a compatible mobile device with the application installed.
AS-2: The customer's device has an internet connection for registration.
AS-3: Registration information should be validated and stored securely.

Other Information:

Customer registration is a critical step for the application, as it allows customers to use personalized features and place orders. Security and data privacy are of utmost importance during the registration process.

Use Case Description Example 3: "Add food to Cart" use case for a Mobile E-Commerce Food Delivery project

Use Case ID and Name:

ID: UC-03
Name: Add Food to Cart on the App

Author:

[Author's Name]

Date Created:

[Creation Date]

Primary Actor:

Customer

Secondary Actors:

None

Description:

This use case describes the process of a customer adding food items to their shopping cart within the mobile e-commerce food delivery application.

Trigger:

The customer is browsing the application's food menu and selects one or more food items to add to their cart.

Preconditions:

PRE-1: The customer is registered and logged in to the application.
PRE-2: The application's food menu is accessible.

Postconditions:

POST-1: The selected food items are added to the customer's shopping cart.

Normal Flow:

The customer launches the mobile app and logs in.
The customer navigates to the food menu or a specific restaurant's menu.
The customer selects one or more food items they wish to order by tapping or clicking on them.
The system adds the selected food items to the customer's shopping cart.
The system updates the cart to reflect the added items and their quantities.
The customer has the option to continue browsing and adding more items to the cart or proceed to checkout.

Alternative Flows:

None

Exceptions:

None

Priority:

High

Business Rules:

BR-1: The application should update the cart in real-time, showing the most up-to-date content.
BR-2: The customer should be able to review the cart and make changes before proceeding to checkout.

Assumptions:

AS-1: The customer is using a compatible mobile device with the application installed.
AS-2: The application's food menu is regularly updated to reflect the available items.
AS-3: The customer is connected to the internet to fetch the food menu and update the cart.

Other Information:

The "Add Food to Cart" use case is a fundamental interaction within the application, allowing customers to select the items they wish to order. Real-time updates and a user-friendly cart interface are essential for a seamless user experience.

Use Case Diagram Template : Credits Karl Wiegers and Seilevel Partners LP.

use_case_template-1.pdf
File Size:	111 kb
File Type:	pdf

Download File

User Acceptance Testing - 10 Points to remember

1/11/2023

"User Acceptance Testing is not just an activity in the project, but a powerful process that helps shape and ensure the success of the final product, aligning it with the needs and expectations of the end-users."

User Acceptance Testing (UAT) is a type of software testing where end-users or stakeholders test the system to ensure it meets their needs and requirements. UAT is performed after the software has gone through other types of testing, such as unit testing, integration testing, and system testing. The purpose of UAT is to validate that the system functions as intended, meets the end-users' needs, and is ready for release or ready to be deployed in the live environment.

"UAT or User Acceptance Testing is performed on real client data involving actual and complex use cases as opposed to test data which may be utilised be the development or testing team for testing purposes in absence of real client data in some cases."

User Acceptance Testing

User Acceptance Testing - 10 Points to Remember

UAT is performed by end-users or stakeholders, not the development team. This ensures that the system is tested from the perspective of those who will use it.
UAT is typically the final stage of testing before the software is released to production. It helps to identify any last-minute issues or bugs that need to be fixed.
The purpose of UAT is to validate the software against the user's requirements, business processes, and use cases. This ensures that the system functions as intended and meets the end-users' needs.
UAT can be performed in different ways, such as manual testing, automated testing, or a combination of both. The choice of method depends on the complexity of the system and the resources available.
UAT test cases should be developed based on the user's requirements and business processes. This ensures that the tests are relevant to the end-users and cover all the essential functionality of the system.
The UAT test plan should be developed in collaboration with the end-users and stakeholders. This ensures that the testing aligns with their expectations and requirements.
UAT should be performed in a test environment that is similar to the production environment. This ensures that the system behaves the same way in both environments.
UAT results should be documented and shared with the development team. This allows the team to address any issues that were identified during testing and make any necessary changes before release.
UAT should be performed on the entire system, not just individual components. This ensures that all parts of the system work together as intended.
UAT should be performed by a diverse group of end-users to ensure that the system meets the needs of all users, regardless of their background or experience.

How to Organise User Stories across Sprints

31/10/2023

Let us learn this with the following examples

Online Shopping Website:
- Sprint 1:
  - As a customer, I want to search for products by keyword, so that I can find what I'm looking for quickly.
  - As a customer, I want to create an account, so that I can save my preferences and order history.
- Sprint 2:
  - As a customer, I want to add products to my shopping cart, so that I can purchase them later.
  - As a customer, I want to view my shopping cart, so that I can see what I've added.
- Sprint 3:
  - As a customer, I want to checkout and make a payment, so that I can complete my purchase.
  - As a customer, I want to receive a confirmation email, so that I can track my order.

Travel Booking App:
- Sprint 1:
  - As a user, I want to search for flights, so that I can find one that meets my requirements.
  - As a user, I want to filter my search results by price, duration, and airline, so that I can make an informed decision.
- Sprint 2:
  - As a user, I want to book a flight, so that I can secure my travel plans.
  - As a user, I want to view my itinerary, so that I can see all my booked flights.
- Sprint 3:
  - As a user, I want to cancel a booked flight, so that I can make changes to my travel plans.
  - As a user, I want to receive a confirmation email, so that I can keep track of my booking.

Project Management Tool:
- Sprint 1:
  - As a user, I want to create a new project, so that I can start organizing my work.
  - As a user, I want to add team members to my project, so that we can collaborate.
- Sprint 2:
  - As a user, I want to create tasks within my project, so that I can break down my work.
  - As a user, I want to assign tasks to team members, so that we can work together.
- Sprint 3:
  - As a user, I want to track the progress of tasks, so that I can see how the project is progressing.
  - As a user, I want to generate reports on project status, so that I can share updates with stakeholders.

This is how we can split user stories across multiple sprints, allowing the team to deliver value incrementally and iteratively.

Attributes of an User Story

31/10/2023

"User stories are the currency of meaningful conversation in agile development, translating customer needs into actionable work for the team."

A user story is a concise, informal description of a software feature or functionality from the perspective of an end user. User stories are a common way to capture and communicate requirements in agile development methodologies, particularly in Scrum. User stories typically consist of several key attributes, which help teams understand and prioritize the work to be done. These attributes include:

Title or Header: A brief, descriptive title that summarizes the essence of the user story. It should be simple and easy to understand.

User Role: The user or persona for whom the feature is being developed. This helps the team understand who will benefit from the feature.

User Story Statement: A short, narrative description of the feature, often written in the following format: "As a [user role], I want [an action] so that [benefit/value]." For example, "As a customer, I want to be able to reset my password so that I can regain access to my account."

Acceptance Criteria: Detailed, specific conditions or criteria that must be met for the user story to be considered complete. These criteria define the scope and functionality of the story and serve as a basis for testing and validation

Priority: The relative importance of the user story in the product backlog. It can be assigned a priority value or ranked based on the needs of the project or product.

Estimate: An estimate of the effort required to implement the user story. This could be in terms of story points, ideal days, or any other unit of measurement the team uses for estimating work.

Definition of Done (DoD): The agreed-upon set of criteria that must be satisfied for the user story to be considered "done" and ready for release. It ensures that the feature is complete and meets the team's quality standards.

Dependencies: Any external factors, user stories, or tasks that the team needs to consider or address while working on this user story.

Notes and Comments: Additional information or context that might be relevant to the user story, such as technical considerations or clarifications.

Attachments: Any relevant documents, mock-ups, or diagrams that can help in understanding and implementing the user story.

User stories are intended to be brief and focused on the user's perspective, allowing for flexibility and adaptability in agile development. The goal is to provide just enough information to initiate a conversation between team members, including developers, testers, and product owners, to refine and implement the feature effectively.

How to schedule your Software Project

31/10/2023

"Failing to plan is planning to fail." - Alan Lakein

When scheduling a software project, it's essential to establish a structured approach to prioritizing requirements. This process can be organized into four key categories: Efficiency, Curtsy, Exigency, and Emergency, often represented by the acronym "ECEE."

Efficiency: Prioritizing for efficiency means considering the natural order in which project modules should be developed. This involves sequencing requirements based on their interdependencies, ensuring that foundational components are built before more complex features. By adhering to this order, the development process becomes smoother, as modules are constructed in a logical and progressive manner. Example: You have to build a software system for your client which has functionalities for

Employee Database
Employee Attendance
Leave
Payroll.

The efficient or natural order to develop this system could be 1-2-3-4

Curtsy: The 'Curtsy' approach focuses on client satisfaction by giving priority to requirements that are most important to the client. These could be features that directly address the client's needs, preferences, or competitive advantages. By putting the client's wishes at the forefront, the project is more likely to result in a product that meets or exceeds their expectations. Continuing with our earlier example project let us say this project takes 4 months to complete and let us hypothetically assume each of the 4 modules will be delivered in 4 iterations or 4 delivery cycles or 4 sprints. However the client has to start his business and has the preference to immediately mark the attendance to start with. In this case the project can be taken up with capturing / importing say employee id (unique) , employee name and moving ahead with the attendance module.

So here the order to develop the system will be 2-3-4-1

"Time management is not about doing more; it's about doing what matters." - Unknown

Requirements Prioritisation Techniques - Must haves for a Business Analyst toolkit

31/10/2023

Requirements Prioritisation Matrix

"The key is not to prioritize what's on your schedule but to schedule your priorities." – Stephen R. Covey

Requirements prioritization is a fundamental aspect of project management and product development. It involves the strategic ranking of requirements based on their importance, value, and impact on the overall project goals. By prioritizing requirements, teams can focus their efforts on the most critical features, ensuring that resources are allocated effectively and that high-value functionalities are delivered early. This process helps in managing scope and adapting to changing project dynamics, aligning stakeholder expectations, and delivering the most valuable components first, thereby increasing the project's chances of success. Effective requirements prioritization is a key element in delivering products that meet customer needs and achieve project objectives while staying within constraints and timelines.

"You can do anything, but not everything." – David Allen

Requirement Prioritisation Techniques in Agile Development

5 Common Insurance Processes

29/10/2023

Insurance Domain or Insurance competency has become a steady revenue earner for IT companies. Demand for Business Analysts, Subject Matter Experts and Product Owners is on a significant uptrend. Here we cover 5 common Non-Life Insurance Processes.

Non-life insurance, is also known as property and casualty insurance. This covers a wide range of insurance types that provide protection against risks other than life and health. Here are five common non-life insurance processes:

Underwriting Process: Underwriting is the process of assessing the risk associated with insuring a potential policyholder and determining the terms and conditions of the insurance policy. Non-life insurance companies use various data sources and risk assessment models to evaluate the likelihood of a claim occurring. This process helps insurers set appropriate premiums and coverage limits.
Claims Processing: Claims processing involves managing and evaluating insurance claims made by policyholders who have experienced a loss or damage covered by their insurance policy. This process includes verifying the claim, assessing the extent of the damage, and determining the compensation amount based on the terms of the policy.
Policy Issuance and Management: This process involves the creation, issuance, and ongoing management of insurance policies. It includes capturing customer information, setting up policy terms, generating policy documents, and ensuring accurate record-keeping throughout the policy's lifecycle.
Premium Collection and Accounting: Premium collection is the process of collecting insurance premiums from policyholders. Non-life insurance companies manage billing cycles, payment processing, and account reconciliation. This process is crucial for maintaining the financial health of the insurance company.
Risk Assessment and Loss Prevention: Non-life insurance companies engage in risk assessment and loss prevention activities to reduce the likelihood of claims. This involves offering risk management advice to policyholders to help them mitigate potential risks, implementing safety guidelines, and promoting practices that reduce the occurrence of covered incidents.

These processes collectively support the functioning of non-life insurance companies, ensuring that policyholders are protected against a wide range of risks and that the insurer's operations are efficient and profitable.

If you have what it takes and you wish to take up a role of a Business Analyst or Subject Matter expert you can whatsapp us at https://wa.me/919810055734

<<Previous

Forward>>

"Essential Accessories for a Successful Requirements Elicitation Interview: A Visual Guide"

Requirements Elicitation - A Throwback Memory

Prominent Software Project Documents organized across Project Phases

In this post we have listed these documents only. In subsequent posts we will briefly explain the intent, purpose and importance of these documents.

Use Case Description 3 Examples with Free Use Case Template

Use Case Description Example 1: "Make Payment By Credit Card" use case for a Mobile E-Commerce Food Delivery project:

Use Case Description Example 2: "Register on Mobile App" use case for a Mobile E-Commerce Food Delivery project:

Use Case Description Example 3: "Add food to Cart" use case for a Mobile E-Commerce Food Delivery project

Use Case Diagram Template : Credits Karl Wiegers and Seilevel Partners LP.

User Acceptance Testing - 10 Points to remember

"User Acceptance Testing is not just an activity in the project, but a powerful process that helps shape and ensure the success of the final product, aligning it with the needs and expectations of the end-users."

"UAT or User Acceptance Testing is performed on real client data involving actual and complex use cases as opposed to test data which may be utilised be the development or testing team for testing purposes in absence of real client data in some cases."

How to Organise User Stories across Sprints

Attributes of an User Story

"User stories are the currency of meaningful conversation in agile development, translating customer needs into actionable work for the team."

How to schedule your Software Project

"Failing to plan is planning to fail." - Alan Lakein

"Time management is not about doing more; it's about doing what matters." - Unknown

Requirements Prioritisation Techniques - Must haves for a Business Analyst toolkit

"The key is not to prioritize what's on your schedule but to schedule your priorities." – Stephen R. Covey

"You can do anything, but not everything." – David Allen

Requirement Prioritisation Techniques in Agile Development

5 Common Insurance Processes

Insurance Domain or Insurance competency has become a steady revenue earner for IT companies. Demand for Business Analysts, Subject Matter Experts and Product Owners is on a significant uptrend. Here we cover 5 common Non-Life Insurance Processes.

Archives

Services

Company

Support

In this post we have listed these documents only. In subsequent posts we will briefly explain the intent, purpose and importance of these documents.

Use Case Description Example 1: "Make Payment By Credit Card" use case for a Mobile E-Commerce Food Delivery project:​

Use Case Description Example 2: "Register on Mobile App" use case for a Mobile E-Commerce Food Delivery project:​

Use Case Description Example 3: "Add food to Cart" use case for a Mobile E-Commerce Food Delivery project

Use Case Diagram Template : Credits ​Karl Wiegers and Seilevel Partners LP.

"User Acceptance Testing is not just an activity in the project, but a powerful process that helps shape and ensure the success of the final product, aligning it with the needs and expectations of the end-users."​

"UAT or User Acceptance Testing is performed on real client data involving actual and complex use cases as opposed to test data which may be utilised be the development or testing team for testing purposes in absence of real client data in some cases."​

​"User stories are the currency of meaningful conversation in agile development, translating customer needs into actionable work for the team."

"Failing to plan is planning to fail." - Alan Lakein​

"Time management is not about doing more; it's about doing what matters." - Unknown

"The key is not to prioritize what's on your schedule but to schedule your priorities." – Stephen R. Covey​

"You can do anything, but not everything." – David Allen​

Requirement Prioritisation Techniques in Agile Development

Insurance Domain or Insurance competency has become a steady revenue earner for IT companies. Demand for Business Analysts, Subject Matter Experts and Product Owners is on a significant uptrend. Here we cover 5 common Non-Life Insurance Processes.

Archives

Services

Company

Support

Use Case Description Example 1: "Make Payment By Credit Card" use case for a Mobile E-Commerce Food Delivery project:

Use Case Description Example 2: "Register on Mobile App" use case for a Mobile E-Commerce Food Delivery project:

Use Case Diagram Template : Credits Karl Wiegers and Seilevel Partners LP.

"User Acceptance Testing is not just an activity in the project, but a powerful process that helps shape and ensure the success of the final product, aligning it with the needs and expectations of the end-users."

"UAT or User Acceptance Testing is performed on real client data involving actual and complex use cases as opposed to test data which may be utilised be the development or testing team for testing purposes in absence of real client data in some cases."

"User stories are the currency of meaningful conversation in agile development, translating customer needs into actionable work for the team."

"Failing to plan is planning to fail." - Alan Lakein

"The key is not to prioritize what's on your schedule but to schedule your priorities." – Stephen R. Covey

"You can do anything, but not everything." – David Allen