- Published on
Adding Case Studies
- Authors

- Name
- MDolce
Table of Contents
- Problems we need to solve:
- For example, to start the development of a new Case Studies page or content area, we need to introduce Use Case Requirements to identify to ensure we are meeting the business needs and the user requirements to establish acceptance criteria for UAT testing.
- Establishing requirements for our Case Studies methodology:
- Challenges:
- Solution?
- REF(s):
Problems we need to solve:
Introducing Case Studies for integrated project solutions.
A large case study may involve multiple projects to get to a solution. This may involve multiple development, research, analysis opportunities to decode the solution.
For example, to start the development of a new Case Studies page or content area, we need to introduce Use Case Requirements to identify to ensure we are meeting the business needs and the user requirements to establish acceptance criteria for UAT testing.
Establishing requirements for our Case Studies methodology:
- The Business Team creates a defines a business need or process that requires a
new changeor establishinga new way of practicefor workflows. - This includes documentation and communication with users and business members, identified as
stakeholdersimpacted by the change or introduction of the new practice. - Creating a list of their needs or
user storiesevolves into a list of requirements, categorized by role or organizational purpose. - These requirements are then converted into development
jobsdefined by a set of acceptance criteria to ensure the job is done correctly. - Finally, users then test,
QA. - If any discrepancies are found, a list of
issuesis created to fix them.
Challenges:
- Documentation
- Tracking
- Data structures
Solution?
TBD