One of the quickest ways to prove your competency as an agile business analyst is getting certified. Though having experience on agile teams is valuable, it’s also worthwhile going the extra mile to formalise that experience by getting certified. Certification is also a great path for those without experience on agile teams to get their feet wet.
As I’ve always been a fan of certifications, I’ve set a new goal for myself this month: to pass the PSM certification, offered by scrum.org.
If you’re looking for a starting point to learn scrum fundamentals, I’ve created two sets of flash cards that may be used by anyone aspiring to write the Professional Scrum Master assessment. It is based solely on the contents of the Scrum guide.
Have a go and let me know what you think:
Failure 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.
If 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.
A roles and permissions matrix, an audit requirement in some organizations, is used to ensure that business activities are covered by identifying the responsibilities and roles linked to them.
Business 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.
The 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.
The 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:
Originally 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.
Requirements 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.
The 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.