My boss is from the old school and he keeps talking about our ‘requirements repository’. We are trying to do agile, specifically Scrum. Are the user stories the requirements repository in Scrum? What should I tell him?
Although use cases are valuable for many projects, sometimes event analysis is a more effective requirements elicitation technique. Valuable as they are, use cases aren’t the ideal tool for every type of product. A complementary requirements elicitation strategy is to explore the various events that a system or product could experience and how it should respond to each of them. The response depends on what state the system is in when it detects the event. Event analysis is particularly well-suited for middleware products and real-time systems that include both software and hardware components.
In today's agile and automation driven times, knowing relevant aspects of brain's mode of working will help. It will help with finding more optimal (and conscious) ways to improve creativity and adaptability in our work. In turn this will help in becoming more successful as a Business Analyst. Let's explore a few scenarios from a business analyst's job. Let's validate if the steps are re-used because they work the best (default mode). Or it is because they are actually suited for the situation.
In the world of Business Analysis, where interpersonal skills, communication skills, and analytical acumen are celebrated, there exists a silent yet enormous barrier that often goes unnoticed—the barrier of “Fear.” To ascend from being a proficient business analyst to a truly exceptional one, it is important to confront and conquer the Top 10 Fears...
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: