The Role of BAs in User Interface Design
/As far as the customer is concerned, the interface is the product - Jef Raskin.
Read MoreAs far as the customer is concerned, the interface is the product - Jef Raskin.
Read MoreThe quote by William Shatner certainly underscores the importance of the interview as a fact-finding technique. While interviews provide analysts the opportunity to learn about stakeholders’ needs, stakeholders in the process of being interviewed, also start to unravel the intricacies of what they want – their elusive requirements.
Read MoreWhile User Acceptance Tests (UATs) sound extremely straightforward in theory, reality is a different ball game - they come with many challenges. This article explores 5 challenges of UAT and proffers recommendations on how they can be tackled.
Read MoreUser Acceptance Testing (UAT) is a phase in the software development life cycle where the intended users of a system participate in validating that the solution meets their needs. There are varying perspectives to the definition of UAT. While some see the UAT as a “test of requirements”, others argue that the same deficiencies missed in the framing of requirements will be missed during testing if this philosophy is adopted.
Read MoreEmotional Intelligence is about identifying and understanding other people's emotions with the objective of channelling these emotions towards a positive outcome. A person with a high emotional intelligence is able to decipher his emotions as well as that of others to help him form healthy working relationships.
Read MoreThe case of a guide dog leading its blind master is a popular analogy here – A dog with intelligent disobedience will disobey an instruction that puts his master in danger, even if the instruction is from the master.
Read MoreWhat if it’s only 20% of the requirements that will actually deliver the most (80%) business value? What if it’s only 20% of the business problems that cause the most issues within the organization? Focusing on key issues and tasks instead of attempting to tackle everything at once can help you achieve huge benefits in the short term.
Read MoreProcesses should continue to be monitored, measured, updated and improved long after they've been automated. Business Process Management is not a one-off initiative but a mindset that should be nurtured within the organization. Knowing what can go wrong on your BPM journey will help you manage any accompanying risks and opportunities.
Read MoreImagine a captain that's trying to decide on the best course to sail to get to his destination, the feasibility study can be likened to a map that displays the routes (options), landmarks (milestones), signs (risks/rewards) which help the business decide on which course to follow.
Read MoreDefining (and documenting) a process is one of the first steps to understanding how it works. Process improvement starts first with understanding how the process works, so whether you’re interviewing process participants or observing a process, here are 10 process components that will help you arrive at a high-level description of the process.
Read MoreRequirements are usually not cast in stone. Stakeholders gather insights and more knowledge of their true needs with time. This means that they can change their minds about requirements, no matter how late in the game. Requirements should therefore be managed proactively in anticipation of change.
Read MoreA risk is an event or condition that may or may not happen. If we fail to manage or identify risks before they happen – they can become serious problems. To avoid constant firefighting on your project, risk analysis should be approached proactively.
Read MoreThis article discusses 6 warning signs your processes may be in need of attention. Look out for these signs and work towards eliminating them.
Read MoreBusiness analysts often have to deal with the volatile nature of requirements, scope creep and the difficulties inherent in ensuring that stakeholder groups have a common understanding of requirements. Requirements elicitation at its core is difficult to accomplish, due to the nature of requirements. This post is a compilation of 8 tips you can apply to improve the outcome of your requirements elicitation effort. Guest Post By Melisa Marzett.
Read MoreBPMS projects are often under immense pressure to deliver quick business value and benefits. One of the key questions organizations implementing BPMS often ask is, “Which process do we implement first?”. The answer to this question is extremely important since the first process can set the pace for the entire BPM Project.
Read MorePeter F. Drucker once stated:
There is nothing so useless as doing efficiently that which should not be done at all.
If you understand lean principles and are able to examine the business from the customer’s perspective, you start to understand what adds value, what doesn’t add value and can discuss along these lines with stakeholders on how improvements can be made.
Read MoreBusiness cases are developed to confirm the feasibility and viability of proposed projects before they are launched. Here's a list of 20 tips to keep in mind on the journey to convincing stakeholders that your recommendation is the way to go.
Read MoreWhen sign-offs are sought without political undertones and with the right intentions, there are certainly benefits to be had. The sign-off process should be approached as an opportunity for discovery that allows stakeholders to ask questions and get clarification on their areas of concern. A huge benefit of obtaining sign-off on requirements is that it indicates stakeholders are aware of, and are committed to seeing the solution live and in action.
Read MorePersonally I am very fond of strawberries and cream, but I have found that for some strange reason, fish prefer worms. So when I went fishing, I didn’t think about what I wanted. I thought about what the fish wanted. I didn't bait the hook with strawberries and cream. Rather, I dangled a worm or grasshopper in front of the fish and said: "Wouldn't you like to have that?" Why not use the same approach when fishing for people? ― Dale Carnegie, How to Win Friends & Influence People. Guest Post By Nicola Joseph.
Read MoreRequirements Review Sessions or Structured Walkthroughs are designed to communicate, check and confirm requirements with stakeholders. During these sessions, participants are expected to ask and respond to questions, proffer suggestions and provide comments on the solution that is about to be implemented. To maximize the limited time you have with stakeholders, follow these key steps to ensure you get it right the first time.
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.
Business Analyst Glossary | Privacy Policy & Disclosures | Advertisements | Submitting A Post | BAL Services
Australian Business Number (ABN): 27 735 714 328