Business Analyst Blog with tips, techniques and resources for every BA.
This post is a compilation of websites with resources that can boost your technical skills, and help you become better at work. If yours is one of those organizations that have cut back on training programs; you've been assigned to a new project or perhaps it's just out of your pure interest in the world of techies, you’ll certainly find these websites useful.
Read MoreIt’s best to select a small number of key attributes and establish a system that allows us to add more requirements attributes as we go along, depending on the nature of the project and which attributes are deemed necessary.
Read MoreAs development practices change, so do the reasons why we write requirements and the level of detail we go into with Requirements Specification Documents. Even seasoned business analysts have at one point or the other asked themselves, “What level of detail is enough?”. The answer to this seemingly simple question is inseparably intertwined with the reason why we write requirements in the first place: so that they can be read, understood, and implemented.
Read MoreOne of the main goals of business analysis is to uncover unknown risks and requirements during the requirements discovery phase. But as many business analysts will surely attest to, sooner or later, the problem of scope creep inevitably arises, unless concrete steps are taken to prevent it.
Read MoreThis post comprises a list of free training that business analysts can use to gain the knowledge and experience of what to do when practising business analysis within the context of business intelligence.
Read MoreIt's that time of the year again and here is a list of the most popular 2016 posts, as determined by BAL readers. This list is based on the number of page views received by each post.
Here it goes:
Read MoreWe make hundreds if not thousands of decisions every day. Some more important, others less so. With each decision we make, we shape our future and possibly, come closer to the attainment of our goals. One of the most effective ways to increase productivity and make better choices during requirements elicitation is by organizing facilitated sessions among stakeholders.
Read MoreDocumentation of software requirements should not be seen as optional, but a necessity. While the level of detail may vary depending on the approach adopted, be it Agile or Waterfall, it’s important to keep in mind why documentation is needed in the first place, before one goes too far in the wrong direction.
Read MoreNeeds Analysis is similar to business analysis especially in the sense that it is used to determine the needs of the business, and is centred on understanding the issues and opportunities faced by the business with the objective of finding resolutions, defining approaches to resolving issues and exploiting opportunities. In summary, it’s about:
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 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.
