Business Analyst Blog with tips, techniques and resources for every BA.
Regardless of size and complexity, the goal of the business case remains the same: to convince decision-makers to approve a proposal. Here are some of the things a business analyst must keep in mind for a winning business case. Guest post by Shuba Kathikeyan
Read MoreFrom analysing data and preparing deliverables to supporting stakeholders through other stages of the solution development lifecycle, the role of the BA is certainly key to successful projects. The end of the elicitation event does not signify the end of business analysis activities, but the beginning of the BA’s involvement in other aspects of the project.
Read MoreA Design Thinking approach enables Business Analysts to solve the wicked business problems they’ve always faced, but from a user-centric standpoint and following an iterative process. Guest Post By Cassandra Naji.
Read MoreIf you understand the sources of your mistakes, you are better able to take the corrective steps that will help you avoid those mistakes in the future, fill the knowledge gaps you have and become a better professional. This article is based on the ideas from Mindset Works.
Read MoreAs professionals, we typically make decisions based on logic and information that is available to us. For example, Business Analysts typically make decisions on which techniques to apply when solving business problems and assist stakeholders in making decisions on which solutions to adopt. Cognitive biases can lead to bad decisions and errors in judgment and as such, BAs should be aware of them.
Read MoreAs discussed in the previous article, Solving Complex Business Problems: An Introduction to Soft Systems Methodology, the steps of SSM can be applied in any particular order and the analyst may choose to skip or apply steps depending on what is needed to understand the problem situation. The steps of SSM that will be applied in this article include:
Read MoreSome business problems are by their nature, complex to handle. Due to their complexity and the non-suitability of traditional problem solving methods, Soft Systems Methodology (SSM) can be used as the methodology for arriving at recommendations for action and positive change. This recommendation for action can range from making minute changes to a process to introducing a new information system.
Read MoreThis list of requirements prioritization techniques provides an overview of common techniques that can be used in prioritizing requirements.
Read MoreSelecting a Requirements Management Software should be done with as much care as when selecting any other software. You should identify which features are required for your project beforehand and assess if the tools currently available to you do not already meet your needs before hunting for requirements management solutions with all the bells and whistles you don't need.
Read MoreAlthough it can be challenging to keep the glossary up-to-date and for stakeholders to agree on every single definition contained in the glossary. The effort spent is well worth the benefit of developing accurate requirements due to a shared understanding of business terms.
Read MoreManaging change requests is particularly important in ensuring that the business does not spend its limited resources on changes that offer no real value at the expense of projects that can deliver real value and lasting benefits.
Read MoreThe Business Analysis: building better stakeholder relations through prototyping article, published on Justinmind blog, discusses 6 tactics that can help Business Analysts create good stakeholder relationships throughout the software development lifecycle. One of them is incorporating excitement requirements to increase stakeholder satisfaction.
Read MoreThis piece is a continuation of Why Do Business Analysts Miss Software Requirements? and provides more reasons why Business Analysts may miss out on key requirements necessary for system development.
Read MoreA project that ends with a deluge of change requests once operations have started can only signify one thing—missed requirements or unmet expectations. Requirements may be missed for many reasons on business projects. This article explores the reasons why requirements can end up as missed and some best practices to keep in mind for successful software implementation.
Read MoreRequirements development and management can falter at various points in a project, causing you to build your software on a faulty foundation of requirements. Prototyping can help a Business Analysis team avoid some of the most common mistakes in requirements development and management. Guest Post By Cassandra Naji.
Read MoreWhile a cruise ship captain is responsible for the vessel, its crew and the passengers, a facilitator is responsible for the outcome of the requirements elicitation event. Still, there are many similarities between a ship captain and an event facilitator:
Read MoreSoftware requirements and the decisions made relating to them, carry through from the point of conception until the product is working in the live environment. One of the key activities that need to be completed during software projects is assigning priorities to requirements.
Read MoreAre you in search of a BA Job or just looking to step up your BA career?
Many suggestions to help your career may seem quite obvious, but can often be overlooked or not fully explored. Guest Post By Anthony Sherick, Founder of Business Analyst Jobs.
Read MoreIf you’re a business analyst involved in a BPM project, use these free courses to get up to speed on BPM concepts:
Read MoreEmpathy is one of the key traits any business analyst should have. It is the trait that brings out the interest and concern that is necessary for supporting the delivery of great solutions to the business.
Read MoreThis business analyst blog contains practical insights into business analysis, software testing and business process management. I will be sharing business analyst tips, CBAP Certification tips, lessons learnt and insights into all the things I've learnt during my BA career.
