Task: Project Instructions

Your project is to create all of the documents you need for your Scrum project. You can use the e-commerce store we discuss in the lessons, or you can use your own project. Your documents should include the following:

Product backlog, with issue types and organised into epics
Definition of done
At least five tickets with clear acceptance criteria

Solution:

1. Product backlog: I have used the product backlog provided by you and based the acceptance criteria on it.

Scrum Project - image 1 - student project

2. Definition of Done:

General Criteria:

All Acceptance Criteria Met: Every user story or task has been implemented according to its defined acceptance criteria.
Code Complete:
- All code has been written, reviewed, and tested.
- Code adheres to the team's coding standards and best practices.
Unit Tests Pass: Unit tests for all new or modified functionality pass successfully.
Integration Tests Pass: Integration tests for the entire system pass successfully.
User Acceptance Testing (UAT) Passed: The feature has been successfully tested by stakeholders or product owners in a UAT environment.
Documentation Updated: Any necessary documentation, including user manuals, API documentation, and architectural diagrams, has been updated to reflect changes.
Performance Considerations Addressed: The feature meets performance requirements and has been tested under expected load conditions.
Security Checks Completed: Appropriate security measures have been implemented and tested to ensure the protection of user data and system integrity.

Design and User Experience:

Responsive Design: The website is responsive and functions correctly across different devices and screen sizes.
Consistent Branding: The design elements and branding are consistent throughout the website.
Accessibility Considerations: The website complies with accessibility standards (e.g., WCAG) and is usable by individuals with disabilities.

Deployment:

Deployment Ready: The feature is ready for deployment to the production environment.
Environment Configuration: The necessary configuration changes for deployment have been made.
Rollback Plan: A rollback plan is in place in case of any issues during deployment.

Release:

Product Owner Approval: The Product Owner has reviewed and approved the feature for release.
Versioning: The release version has been updated according to the project's versioning scheme.
Release Notes: Release notes have been prepared detailing the changes introduced in the current release.

3. Acceptance criteria:

1. User story: As a Visitor, I want to the name of the product (Product page).

Acceptance criteria:

The product name is prominently displayed on the product page.
The product name is legible and clearly visible to the visitor.
The product name is correctly aligned with other elements on the page.
The product name accurately reflects the name of the displayed product.

2. User story: As a Visitor, I want to see the product image (Product page).

Acceptance criteria:

A high-quality image of the product is displayed on the product page.
The product image is clear, well-lit, and properly sized.
The product image accurately represents the appearance of the product.
Visitors can enlarge the product image for a closer view, if desired.

3. User story: As a Visitor, I want to see the product specifications (Product page).

Acceptance criteria:

The product specifications are listed in a clear and organized manner on the product page.
Specifications include key details such as dimensions, materials, and features.
Specifications are accurate and up to date with the product information.

4. User story: As a Visitor, I want to see the product reviews (Product page).

Acceptance criteria:

Product reviews are displayed on the product page, if available.
Each review includes the reviewer's name, rating, and comments.
Reviews are sorted by relevance or date, with the most recent or helpful reviews displayed first.
Visitors can easily access all reviews and filter them based on rating or other criteria.

5. User story: As a Visitor, I want to add a product to my basket (Product page).

Acceptance criteria:

Visitors can click on an "Add to Basket" button or similar action to add the product to their basket.
Upon clicking, the product is successfully added to the visitor's basket.
The visitor receives visual confirmation (e.g., a popup message) indicating that the product has been added.
The basket icon or counter updates to reflect the addition of the product.

6. User story: As a Visitor, I want to view my basket (Checkout).

Acceptance criteria:

Visitors can navigate to their basket page from any page on the website.
The basket page displays all items currently in the visitor's basket.
Each item in the basket is listed with its name, image, price, and quantity.
Visitors can easily adjust quantities or remove items from their basket.

7. User story: As a Visitor, I want to proceed to checkout (Checkout).

Acceptance criteria:

Visitors can proceed to the checkout process from their basket page.
Upon clicking the "Proceed to Checkout" button, visitors are taken to the checkout page.

8. User story: As a Visitor, I want to enter my credit card details (Checkout).

Acceptance criteria:

The checkout page includes a secure form for entering credit card details.
Visitors can input their credit card number, expiration date, CVV, and billing address.
Credit card information is encrypted and securely transmitted to prevent unauthorized access.

9. User story: As a Visitor, I want to submit my order (Checkout).

Acceptance criteria:

After entering credit card details and confirming the order, visitors can submit their order for processing.
Upon submission, visitors receive a confirmation message indicating that their order has been successfully placed.
Visitors receive an email confirmation containing details of their order and estimated delivery time.

10. User story: As a Visitor, I want to browse all products (Homepage).

Acceptance criteria:

The homepage displays a selection of featured products or categories.
Visitors can easily navigate to view all products by clicking on a designated link or button.
All products are organized and displayed in a visually appealing and user-friendly manner.

11. User story: As a Manager, I want to see a list of orders (Order management).

Acceptance criteria:

The manager dashboard includes a section for viewing a list of all orders.
Each order in the list is displayed with relevant details such as order number, date, customer name, and status.
Managers can easily filter and sort orders based on various criteria (e.g., date, status, customer).

12. User story: As a Manager, I want to view the details of an order (Order management).

Acceptance criteria:

Managers can click on an order from the list to view its detailed information.
The order details page displays all relevant information about the selected order, including items purchased, customer details, and order status.

13. User story: As a Manager, I want to mark an order as dispatched (Order management).

Acceptance criteria:

Managers can update the status of an order to "Dispatched" from the order details page.
Upon marking an order as dispatched, the order status is updated accordingly.
The customer receives a notification (e.g., email) informing them that their order has been dispatched.

Christopher Theus

--

1