Final Project

This is the final project of the IBM Introduction to Agile Development and Scrum course at Coursera.

It's the result of the following lab exercise:

Stakeholder requirements

Following are the requirements from your stakeholders that you should use to create the user stories in Kanban board.

1. Need the ability to create a product in the catalog.
2. Need the ability to retrieve a product from the catalog.
3. Need the ability to update a product in the catalog.
4. Need the ability to delete a product from the catalog.
5. Need the ability to Like a product in the catalog.
6. Need the ability to Dislike a product in the catalog.
7. Need the ability to list all products in the catalog.
8. Need the ability to query a subset of products in the catalog.
9. Must be hosted in the cloud.
10. Must have automation to deploy new changes to the cloud.

Instructional tasks

To help you finish the final project, we have provided a list of instructional tasks to guide you:

1. Create a new GitHub repository called agile-final-project and ensure it is public.
2. Create a Project in your GitHub repository and name it Final Project.
3. Create an issue template for the new repository similar to the labs.
4. Create issues for the stakeholder requirements listed above (10 in total). Fill in the As a… I need… So that… section of the template.
5. Move requirements 7 and 8 issues into the Icebox.
6. Move the remaining issues into the Product Backlog.
7. Conduct a Backlog Refinement meeting and rank the Product Backlog to match the requirements order.
8. Update the top 5 stories in the Product Backlog with acceptance criteria following the Gherkin Given… When… Then… syntax.
9. Create a technical debt label.
10. Add labels of either enhancement or technical debt to all stories in the Product Backlog.
11. Create a sprint milestone with a duration of 2 weeks, named Sprint.
12. Conduct a Sprint Planning meeting. Add the top 4 stories to the sprint, assign them to the sprint milestone, and assign story point estimates. Move these 4 stories to the Sprint Backlog.
13. Simulate a sprint by assigning the top story to yourself. Move it to the In Progress column.
14. Move the story to Review/QA. Take the next story from the Sprint Backlog, assign it to yourself, and move it to the In Progress column.
15. Move the story in Review/QA to Done. Move the story from In Progress to Review/QA. Take the next story off the Sprint Backlog, assign it to yourself, and move it to the In Progress column.
16. Move the story in Review/QA to Done. Leave the story in the In Progress column where it is. This marks the end of the sprint.
17. Ensure your burndown chart displays correctly.
18. Share the URL of your kanban board for peer review.

Grading Criteria Overview

There are a total of 20 points possible for this final project. The grade will be based on the following tasks:

1. Submit the URL for your final project kanban board. (1 pt) 
2. Put a github/ISSUE_TEMPLATE in the repository. (1 pt)
3. Follow the story template, “As a… I need… So that…” (2 pts)
4. Acceptance criteria following the Gherkin “Given… When… Then…” syntax. (2 pts)
5. Put labels on all the stories, starting with the Product Backlog. (2 pts)
6. Assign estimates to all the stories, starting with the Sprint backlog. (2 pts)
7. Create a Sprint or Milestone with a title. (2 pts)
8. Assign the Sprint or Milestone to the stories, starting with the Sprint Backlog. (2 pts)
9. Assign all the stories to yourself and move them to In Progress. (2 pts)
10. Create a burndown chart for the Sprint or Milestone. (2pts)
11. Label stories for requirements 9 and 10, as technical debt. (2 pts)