Challenge yourself by keeping up with practical business analysis techniques you can apply on the job.
User story maps are an interesting and collaborative way of eliciting user requirements. One of the reasons why I find it so powerful is because it provides a unique approach for aligning discussions relating to the user, their goals, the process that supports the accomplishment of their predefined goals; and the requirements that need to be addressed to solve business problems.
Read MoreData mining can be described as the process of improving decision-making by identifying useful patterns and insights from data.
Read MoreA data dictionary holds data about the fields in a database, such as field definitions, meanings and allowable values that reflect how data is used within a domain or organization.
Read MoreAre you a business analyst involved in the documentation of business rules and creation of complex decision tables?
A concept model provides a great way of documenting definitions and communicating precise meanings of terms to stakeholders.
Read MoreEmploying the user journey mapping technique involves adopting a user-centric approach to product design, revealing opportunities to delight customers and identifying pain points that can be addressed thereby creating a product with an improved user experience.
Read MoreWithin the context of agile software development, the product backlog is a platform where all the potential work (product backlog items) that need to be delivered are recorded, tracked and prioritized. Though owned by the Product Owner, anyone may suggest items to add to it.
Read MoreFailure Mode and Effects Analysis (FMEA) is a proactive technique that can be applied to the early detection of failures or defects in products and services. It is a systematic risk assessment process used by analysts looking to reduce the chances of faults by detecting problems and their possible repercussions in time for remediation.
Read MoreIf you are in business, here is a brief overview of how cause and effect analysis helps you find viable business solutions. Guest post by Lucas Cappel.
Read MoreBusiness Process Model and Notation (BPMN) is a global standard for constructing process models, with more organizations using it and schools teaching it as a subject.
Read MoreThe terms “Quality Assurance (QA)" and “Quality Control (QC)” can be confusing or even misunderstood to mean the same thing. In this article, the goal is to clarify the real meaning of the two terms and explain their differences.
Read MoreThe textual representation of a use case shows the interaction between the actors textually and at an appropriate level of detail. There are several set elements that every textual representation of a use case should contain:
Read MoreOriginally released in 2005 by BPM Group, the 8-Omega framework has been adapted and embraced by a large number of organizations around the world for the improvement of business processes.
Read MoreRequirements scope statements are defined later in the project life cycle and are relatively fluid. As long as they still fall within the boundaries set by project scope statements, they can be updated and modified to reflect the changing needs of the project.
Read MoreThe SCRS approach encourages analysts to present practical and feasible business solutions that flow from the current strategy and are in tune with the business’ overarching vision and goals. Think of SCRS as an action plan for solving business problems.
Read MoreProcess performance metrics generate accurate data, bringing more efficiency and effectiveness to the decision-making process. The data generated by process performance metrics can be aggregated and displayed on a unified dashboard to provide a panoramic overview of the company’s performance.
Read MoreWhen deciding between different designs, you want to base your decision on rational arguments instead of subjective preferences. One methodology for establishing a procedure to select the best option from multiple available options is Pugh Matrix, also known as the decision matrix.
Read MoreConsequently, systems developed using the traditional approaches to software development are rigid and difficult to change. It’s often necessary to modify a large number of parts of the system just to implement a single, small change. The traditional approaches to software development are effective only in situations where requirements are specific and unlikely to change over time.
Read MoreOne increasingly popular method for breaking down a process into smaller and more easily understood parts, which this article will focus on is called ICOR, which stands for Inputs, Outputs, Controls, and Resources.
Read MoreThe essence of VPEC-T analysis is to provide a collection of mental filters and guides. Together, they provide a simplified communication method that prevents loss in translation from business needs to IT solutions.
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.
