As we prepare for the demos and evaluation of a digital asset management system, we feel the next best logical step is to create a list of user stories. These stories will help us better evaluate how the software works for our needs as a church.
User stories are a tool used in software development to help the stakeholder communicate the expected needs of a product with the developers.
“In software development and product management, a user story is an informal, natural language description of one or more features of a software system. User stories are often written from the perspective of an end user or user of a system.” via Wikipedia
So as we move forward with this project, we need to hear from you! Please use the Google Sheet linked below to help describe the needs of the users of the digital asset management system.
There are three elements that are needed for each story:
- Expected Results
The role defines the type of user (IE: Photographer, administrator, etc). The process describes the type of work done. And the expected results describe what you would expect this type of user to do.
A few ground rules:
- Don’t worry about duplication. We will combine them later if needed.
- Please don’t delete other peoples work.
- Help us see the blind spots. We need to know the ways people would use the software.