Requirements Gathering Activity
Customers will be meeting with developers in groups to discuss the details of the project to be implemented. Groups will meet in the order of the team pairing pages (section 1, section 2) and then switch part-way through the class session.
Customers
Elaborate on your project with the development team and help them to define the features your application need and the target user(s). Answer any elaboration questions they may have. Remember, you do not know what technology will be used for implementation, so avoid implementation details. If at any time, you have questions whether something is feesible or reasonable, I’m happy to help.
Developers
Work with your customers and build a set of user stories. These user stories will be added to your repository’s Issues on GitHub. Each story needs:
- Title (Action/Verb phrase)
- Short description
- ~3 sentences to explain as a rough guideline .You can expand the description with notes as needed.
- Priority
- Estimate
You may find that you have more user stories than number of features desribed in the project proposal, this is okay. DO NOT WORRY ABOUT HAVING TOO MANY USER STORIES, JUST FOCUS ON THE PROCESS FOR NOW. The important thing at this stage of the project is to record the requirements as stories.
After you have your user stories, work with your group to come up with estimates. You can use planning poker to help. User stories will also get tasks in the form of Sub-Issues on GitHub. While tasks and estimates do NOT need to be completed by the end of the day (02/05/2025) do not neglect these tasks as I will evaluate your development process at a later date.
Deliverable:
A set of >= 5 requirements in proper User Story format in your project’s GitHub Issues.