Business Process Modeling allows us to increase our understanding of business processes and improve communication with stakeholders and implementation teams. Business analysts will create diagrams that represent business processes. These diagrams can be used to elicit requirements, define scope, and improve communication within the team.
Communication / Product Management / Requirements / Requirements Models / Software requirements specification / Use Cases
Posted on:
Communicating Intent With Implementers
Giving a functional spec to developers and testers is not sufficient for creating great software. To a developer, a spec is only the what and not the why. And for a tester, the software requirements specification is neither. Use cases provide the why that explains the intent of the system for the implementation team.
Communication / Product Management / Requirements / Requirements Models / Use Cases
Posted on:
Communicating Intent With Stakeholders
We can build a prototype of what the stakeholders don’t want, and then get feedback and fix it. Or we can review use cases of what we intend to build, confirm that each stakeholder wants it, and build it right the first time.
Foundation series / Requirements / Requirements gathering / Software requirements specification
Posted on:
Foundation Series: Data Dictionary Definition
What is a data dictionary and how is it used when communicating and managing requirements?
Product Management / Requirements / Requirements gathering
Posted on:
Four Assumptions of the Apocalypse
Business Analysts often start with four erroneous assumptions when eliciting requirements. 50% of errors in software projects are caused by requirements errors. These four faulty assumptions, presented by James A. Ward, can exacerbate the error-prone process of gathering requirements.
Lists / Requirements / Writing
Posted on:
Outside Reading: Top 10 Signs You Should Not Write Requirements
Seilevel has a post that presents the top 10 signs that you should not pursue a career writing requirements, check it out. Thanks Joy for the great article!
Product Management / Requirements / Requirements Models / ROI / Use Cases
Posted on:
Verify Correct Requirements with Use Cases
The next piece in the puzzle of how and why we apply use cases to product management. Verification of requirement correctness.
Product Management
Posted on:
Product Managers Play Tug-of-War
63% of product managers report to marketing and 24% report to development. 22% of requirements managers report to marketing with 55% in the development organization. These reporting structures can over-emphasize the needs of new users and super-users, while shortchanging the needs of the majority of users. Product managers will constantly be playing tug-of-war to get time to do the right thing.
Product Management / Requirements / Requirements Models / Use Cases
Posted on:
Requirement Completeness Validation with Use Cases
In our article, The 8 Goals of Use Cases, the first goal is that our use cases must support requirement-completeness validation. In this article, we explore how to address this goal and how use cases can help. There are many pieces to this puzzle, and this article is one of them.