Tips For Business Process Improvement

Tips For Business Process Improvement

I once came across a trainer who equated process specialists to purple squirrels because of how hard they are to come by. Process specialists have the ability to interview stakeholders effectively, analyze feedback and have a deep understanding of at least one improvement methodology. Another course I attended recently on strategic business process improvement struck a cord so I’ve compiled some fundamental nuggets analysts should be aware of in improving business processes.

Read More

How to Improve Stakeholder Relationships

How to Improve Stakeholder Relationships

Someone once asked me, “How do you handle a difficult stakeholder?”. It’s never a pretty situation managing a stakeholder who is obviously opposed to your project for whatever reason. It’s even worse when the stakeholder goes the extra mile to ensure your project doesn’t succeed. Managing stakeholders is no different from managing personal relationships with people. 

Read More

Proof of Concept: Benefits & Risks of Prototyping in Business Analysis

Proof of Concept: Benefits & Risks of Prototyping in Business Analysis

I once worked on a project that involved a series of discussions and consultations on whether to build or buy software. After extensive analysis, the decision was made to build the system in-house. To get started however, we had to prove that it could be done. We did this through a proof of concept (POC).

Read More

Applying the Kano Analysis Model to Requirements Identification & Prioritization

Applying the Kano Analysis Model to Requirements Identification & Prioritization

Because stakeholders make decisions both at conscious and unconscious levels, they are unable to express everything they want in a solution. The Kano Model is a technique that allows the analyst elicit and categorize requirements along two axes: How well requirements are executed and the level of customer satisfaction.

Read More

Is Automated Software Testing the Way to Go?

Is Automated Software Testing the Way to Go?

Testing is a crucial part of software development projects as it reveals the true quality of software products. If there are any bugs or coding errors in the system, software testing can reveal those flaws and help to deliver effective applications. However, deciding whether to take the manual or automated testing route is usually the challenge - Guest Post By Prashant Chambakara.

Read More

Effective Interview Sessions: Before, During and After

Effective Interview Sessions: Before, During and After

Interviews are a popular technique with analysts. Unfortunately, they’re not that simple. Great interviews do not just happen. They have to be carefully planned with every minor detail ironed out before the day. Without further ado, this post outlines the basic but crucial factors that analysts should be aware of before, during and after an interview session.

Read More

Stakeholder Profiling in Business Analysis: Why it Counts

Stakeholder Profiling in Business Analysis: Why it Counts

One of the 48 Laws of Power, as stated by Robert Greene, an American Author, is to always know who you're dealing with. You cannot assume that different people will react the same way to your strategy or plans. That's why it's important to gather as much information about a person that either support or contradict your beliefs about them when dealing with them.

Read More

Can A Tester Without Coding Skills Perform Testing?

Can A Tester Without Coding Skills Perform Testing?

To meet the demands of quick product delivery, companies want to perform testing at a faster pace. At present, recruiters are torn between demanding for testers with good coding knowledge and those without. It is obvious that a tester who has to spend time writing automated test codes will take a longer time. So, the question is - Can a tester without coding skills perform testing? Guest Post By Prashant Chambakara

Read More

4 Steps to Getting a Head Start on Requirements Elicitation

4 Steps to Getting a Head Start on Requirements Elicitation

Consider this scenario: You’ve been charged with introducing a new Information System to support the work of inexperienced stakeholders. Some are inexperienced on the job while others know very little about the technology, opportunities and constraints related to the new information system. In this scenario, techniques such as interviews and workshops (events-based elicitation techniques) may not yield sufficient results. What is the way forward?

Read More

Problem Solving: Unveiling the Multiple Faces of the PIECES Framework

Problem Solving: Unveiling the Multiple Faces of the PIECES Framework

In a quest to prevent solving the wrong problem, numerous techniques like the cause and effect diagram and 5 Whys have been introduced. One problem solving tool that shouldn’t go without a mention is the PIECES framework. What makes it so unique is that it can be applied to analysis at multiple levels to deliver different results, depending on how you apply it.

Read More

Why Non-Functional Requirements Matter

Why Non-Functional Requirements Matter

I’d always thought that if the ICT Department delivered a system that satisfied all the functional requirements of users, one could call it a successful system. I thought that if the system worked exactly the way stakeholders said they wanted it to work, everyone could call it a day. You can imagine my reaction when I came across an article that challenged this view. 

Read More

Getting Requirements Right: 5 Mistakes to Avoid

Getting Requirements Right: 5 Mistakes to Avoid

There’s no one formula for getting requirements right. Projects are different and come with various challenges, opportunities and methodologies to contend with. Having an idea of what mistakes to avoid can improve the quality and accuracy of your requirements. This post is a continuation of 5-Step Plan to Eliciting Accurate Requirements, and it points out the missteps to avoid when eliciting requirements.

Read More

Resolving A Messy Situation: Soft Systems Methodology

Resolving A Messy Situation: Soft Systems Methodology

It is not in all cases that a project is launched from a clearly defined problem statement and plan of action. In some cases, the situation requires careful study aimed at resolving conflicting views on the causes of a problematic situation. Soft Systems Methodology when applied, can make all the difference. 

Read More

The 5 - Step Plan to Eliciting Accurate Requirements

The 5 - Step Plan to Eliciting Accurate Requirements

In the real world, business analysts often have to go the extra mile to elicit requirements, regardless of the circumstances. Despite the difficulty of identifying these elusive requirements, business analysts are expected to rise up to the challenge - every single time. This post outlines 5 steps that can be taken to improve the accuracy of requirements.

Read More

The Project Manager and Business Analyst Collaboration

The Project Manager and Business Analyst Collaboration

The BA and PM roles are complementary and support each other. To hire one without the other introduces the risk of losing the benefits that come with having these two specialists support each other to deliver a solution of the right quality, at the right time and within the available budget.

 

Read More

Common Problems Faced by Business Analysts and Possible Solutions

Common Problems Faced by Business Analysts and Possible Solutions

Business Analysts are communicators and facilitators brought on projects to elicit requirements by sifting through masses of information and relating these requirements to the technical team. This role is extremely vital but comes with unique difficulties that every BA should know about and endeavour to rise above. Being aware of the pitfalls that come with the profession will prepare you to tackle them if and when they arise.

Read More