News
-
Week 3 Class 5 Tue Sep 10 Posted: Sep 10
Announcements:
- Brightspace & Exercises Uploads of assignments to Brightspace may not be available until the end of class, even when the Class Meeting is posted early.
-
Action-Oriented Titles
The primary goal of user stories is to capture a specific need or goal of a user in the context of software development. It's about "what the user wants to do" or "achieve" with the software.
Benefits of Action-Oriented Titles:
- Clarity Action-oriented titles make it clear what the expected outcome or behavior of the system should be
- Focus on Value Emphasizing actions reminds the team to focus on delivering value and functionality rather than just creating artifacts
- Facilitates Testing It is easier to deriving test cases from action-oriented stories
-
User Story Titles and the Number Grammatical Category
Strongly consider using a title with a singular noun for a user story, instead of a title with a plural noun, because it emphasizes the atomic nature of the action.
Plural Singular Upload Documents Upload a Document Send Messages Send a Message Add Products to Cart Add a Product to Cart Register for Events Register for an Event View Notifications View a Notification Search for Jobs Search for a Job In general, user stories with singular titles are going to be easier to implement. There can be exceptions, as "View Notifications" may be simpler than "View a Notification" due to not having to select just one.
The most important aspect is clarity and understanding. If "Purchase Clothes" effectively communicates the intent without ambiguity and your team finds it more natural, it's also acceptable. The choice between singular and plural should ultimately be guided by what best serves the clarity and focus of the story in your context.
- Development Environment: Git Setup by next class.
Class
- Exercise 9: HFSD Chapter 2 p 47 Cubicle Conversation
- HFSD Chapter 2
- Exercise 10: HFSD Chapter 2 Crossword
- HFSD Chapter 3
- Exercise 11: Team User Stories II
Unless stated otherwise, all exercises are due by 3 pm on Wed Sep 11
-
Exercise 11: Team User Stories II Posted: Sep 10
Your team is to correct the current user stories and increase the number of user stories. Very carefully go over your user titles and descriptions. Add more user stories and see what you are missing.
Remember to split any user stories that you can. Apply the "and" rule.
- I want a lot of user stories. Do not make any judgments on whether they are worthwhile or not. Generate as many as you can
- The User Stories do not belong to an individual team member. They belong to the team. So feel free to make changes to stories, even if you are not the original author.
- For this assignment, no User Story should have a title that includes "Login" or similar terms. Assume that they have already logged in or (much better) do not have to log in.
- You have not performed an estimation process. Do not fill in the estimate with some guess or random number.
In addition to the team work of extracting user stories from the app description, each team member will turn in to Brightspace individual notes that includes:
- The new total number of user stories
- The titles of at least 3 new user stories or user stories with changed titles
The individual notes are due by the end of class uploaded to Brightspace. They can be in the form of a PDF (print to file from a computing device), or a JPG (picture taken via your phone).