Explain how we can tell when a project or some portion of a project (say, for example with respect to some specific bit of functionality) is complete? We need to go back to our product backlog and the user stories that we collected there to determine if we are finished.
For each user story we need to write acceptance criteria to specify how we will determine when that user story is complete. Let’s refer back to the product backlog from Mountain Goat Software that we worked with in Module 6. For the News portion of the website I have the following user stories:
News
As a site visitor, I can read current news on the home page so that I stay current on agile news.
As a site visitor, I can access old news that is no longer on the home page, so I can access things I remember from the past or that others mention to me.
As a site visitor, I can email news items to the editor, so they can be considered for publication. (Note: this could just be an email link to the editor.)
As a site a site editor, I can set the following dates on a news item: Start Publishing Date, Old News Date, Stop Publishing Date so articles are published on and through appropriate dates. These dates refer to the date an item becomes visible on the site (perhaps next Monday), the date it stops appearing on the home page, and the date it is removed from the site (which may be never).
As a site editor, I can assign priority numbers to news items, so I can indicate which articles I want featured most prominently on the site. Note: Items are displayed on the front page based on priority.
The first thing to do is identify the roles of the system users, then determine the inputs and the corresponding expected outputs. When these are achieved then that portion of functionality is complete, done, fini! See the table below that is constructed reflecting this information for the News functionality on the website.
User Role Input Output
Site Visitor Home Page –> click news link Presentation of news page
Site Visitor Home Page –> click archive link Presentation of archived news
Site Visitor Home Page –> click contact editor Initiation of link to external email
Site Editor Admin Page –> set publish start date News item appears on date set
Site Editor Admin Page –> set old news date News transfers to archive on date
Site Editor Admin Page –> set stop publish date News stops appearing on site
Site Editor Admin Page –> assign news priority News articles ordered by priority
Now it’s your turn for the Course and Events given below.
Create a table similar to the one above that specifies what needs to be achieved by the system to be able to declare that functionality complete. You can create your table in MS Word or Excel. Attach the completed file to this assignment.
Courses and Events
As a site visitor, I can see a list of all upcoming “Project Management Certification Courses” and can page through them if there are a lot, so I can choose the best course for me.
As a site visitor, I can see a list of all upcoming “Other Courses” (non-certification courses) and can page through them if necessary, so I can choose the best course for me.
As a site visitor, I can see a list of all upcoming “Upcoming Events” so I can decide if I want to attend any. (Events are things such as the Scrum Gathering, conferences, free seminars, etc.)
As a trainer, I can create a new course or event, so site visitors can see it.
As a trainer, when I create an Other Course or Event, I am charged a listing fee for that activity so I don’t list events I don’t really intend to hold.
As a site administrator, I can set the listing fee per Other Course or Event so that we have flexibility on what (if anything) to charge in the future.
As a trainer, I can update one of my existing courses or events so that it reflects accurate information.
As a trainer, I can delete one of my courses or events, so it’s no longer listed if I cancel for some reason.
Criteria
Correctly identified scenarios for testing for completion of user story
Correctly and completely specified required user input for tested scenario
Correctly and completely specified output that is consistent with applicable user stories
