Business Analyst Blog with tips, techniques and resources for every BA.
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 MoreOne 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 MoreTo 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 MoreConsider 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 MoreIn 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 MoreI’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 MoreHave you ever spoken to someone who wouldn't look you in the eyes? A lack of eye contact can indicate insincerity or uncertainty. Body language is an extremely crucial form of communication that is often taken for granted. When was the last time you read someone’s body language?
Read MoreThere’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 MoreIt 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 MoreIn a perfect world, all stakeholders would be able to completely articulate what they need, making life much easier for analysts. In reality however, they aren’t always in a position to provide information on what their requirements are. This is because they don’t always know what to request for.
Read MoreIn 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 MoreThe 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
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 MoreI once attended a supposed brainstorming session in which only 3 of the 8 participants got round to contributing to the discussion. They had prepared a list of recommendations based on their findings and all they did was reel out their discoveries. A meeting should not be incorrectly tagged as a brainstorming session if it's not going to be conducted as such.
Read MoreIIBA's Certified Business Analysis Professional (CBAP) Certification is one of the most recognized certifications for Senior Business Analysts. The exam is based on the Business Analysis Body of Knowledge (BABOK®) Guide, which contains accepted practices in Business Analysis. Preparing to take your CBAP exam may seem like a herculean task; it can be quite daunting but it doesn’t have to be. Through this post, I’ll share the tips that helped me pass the CBAP exam. We all have different approaches to learning but here are some key points that can help you prepare for your CBAP Exam.
Read More
Logical fallacies can be described as mistakes or errors in reasoning. Recognizing logical fallacies in yourself and others will help to sharpen your critical thinking skills. Practise identifying these logical fallacies in everyday situations.
Read MoreOne day after a lecture, I walked up to my Professor, Dr. Tony Cornford to autograph a copy of his book which I had just purchased. He signed on it and here are his words: “Don’t believe everything.” I didn’t really think much of it until I stumbled on the book again after 3 years. And then it struck me.
Read MoreAs a first step in rising up to the call of producing high quality requirements and turning the tide of ICT projects, this post points out the tricky nature of requirements and mistakes that can be avoided when compiling requirements specification documents.
Read MoreEvery software project is unique and there’s no guarantee that the approach or strategy that works well for one project will work for another. There are however, some basic guidelines business analysts can adopt in order to add value to software projects.
Read MoreUsing the analogy of werewolves, the monsters of folklore who transform from the familiar to the horrific, Brooks describes software projects. The familiar software project can easily be transformed into a monster of missed schedules, overrun budgets and defective software. Unlike werewolves that can be laid to rest with a silver bullet, software projects are a different ball game.
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.
