Open BdwinE opened 5 years ago
Please review the edits that I made to the Story to see if they match your intent.
The Acceptance Criteria requires additional editing to ensure that they are measurable.
Please review the edits that I made to the Story to see if they match your intent.
The Acceptance Criteria requires additional editing to ensure that they are measurable.
The edits you made look good, and what type of things do you suggest I change about the Acceptance Criteria to make it more measurable? Should it be more or less specific?
Probably "more" specific, but primarily more unambiguous in how a proposed solution is to be evaluated.
For example, to determine whether a proposed solution includes an "overwhelming block of text" there needs to be an unambiguous means by which that is measured.
Likewise, what is the way that "clear" is determined? How do we know that instructions are "as short as possible"? (Might "clarity" and "shortness" sometimes be in conflict? If so, which has priority?)
The use of an example was helpful. Using examples from the actual domain (such as, BlueJ, BlueJ Extensions, IDEs, or CS-1 student labs) might be even more helpful.
User Story
Essential components
Story
As a user I want an intuitive user interface so that the product is easy to learn and easy to use.
Acceptance Criteria (Not Yet Verifiable)
Supporting Information
The interface may make or break a product. If something isn't user friendly then most people aren't going to enjoy using it, leading them to look for other alternatives. While on the other hand, a simply to use UI that provides many features add elegance to all the hard work done in the background and makes it an enjoyable experience for the user.
See also: https://www.nngroup.com/articles/measure-learnability/