Fluid WMS: Feature Checklists

Feature Checklist: Address Entries

Cover-image-WMS.png

Feature Checklist: Address Entries

Scenario

 Adding job collection and delivery details

Given

 a user is creating or editing a job in the WMS
When the user needs to specify 'collect from' and 'deliver to' addresses
Then The system should provide input fields for both addresses and pre-populates addresses where applicable, 

Good When

Bad When
Users can easily find and fill in 'collect from' and 'deliver to' fields
The address fields are not clearly labeled
System validates the addresses to ensure they are complete and accurate, and pre-populates existing addresses.
Address validation fails, allowing incomplete or incorrect addresses to be saved and does not pre-populate existing addresses.
Users can edit addresses at any stage before the job is accepted by an operative.
Users cannot edit the addresses after initially setting them, leading to potential errors in job assignments.
Completed When

Jobs in the WMS accurately includes 'collect from' and 'deliver to' information, streamlining the logistics process and enhancing operational efficiency.
Start When

When purchase order has been issued to the client.
Feature Priority
  • High Priority 
  • Medium Priority
  • Low Priority   
Client Approves Feature

  • Approved
    Once approved, inform us by email, we will close the feature checklist and begin the process.
Agreed Timeline

Once approved the process will continue as

  • Create mock ups of the feature within 14 days of 'Start When'
  • Schedule of the project will be agreed within 14 days of ‘Start When',
  • Development of the feature once mocks up have been approved.
  • Q/A and delivery 7 days after development cycle

Estimated development time for this feature would be 5 days,

Feature Checklist: Report Issue

Cover-image-WMS.png

Feature File: Report Issues

Scenario

 Reporting an issue via the platform

Given

 User encounters a problem or error within the WMS
When User clicks the 'Report Issue' button
Then System should allow the user to describe and submit the issue


Good When

Bad When
The 'Report Issue' button is accessible on all pages of the WMS.
The 'Report Issue' button is difficult to find.
The issue reporting process is straightforward, encouraging users to report problems.
The reporting process is overly complex, deterring them from submitting issues.
Users receive confirmation that their issue has been submitted and is being addressed
There is no confirmation of issue submission, leaving users unsure if their report was received.
Completed When
Users can easily report issues through the WMS, ensuring quick response to any problems.
Start When

When purchase order has been issued to the client.
Feature Priority
  • High Priority 
  • Medium Priority
  • Low Priority   
Client Approves Feature

  • Approved
    Once approved, inform us by email, we will close the feature checklist and begin the process.
Agreed Timeline

Once approved the process will continue as

  • Create mock ups of the feature within 14 days of 'Start When'
  • Schedule of the project will be agreed within 14 days of ‘Start When',
  • Development of the feature once mocks up have been approved.
  • Q/A and delivery 7 days after development cycle

Estimated development time for this feature would be X days,

Feature Checklist: New Item Not Mandatory

Cover-image-WMS.png

Feature File: New Item Not Mandatory

Scenario

 Adding a job without requiring a new item.

Given

 User is creating a job in the WMS.
When Job does not require adding a new inventory item.
Then System should allow the job to be saved without adding a new item, the 'complete' button for the operative should be apparent at the top of the screen, and the 'collect' item button should be removed.


Good When

Bad When
Users are able to create jobs without adding inventory items.
The option to skip adding a new item is not clear.
The system indicates that adding a new item is optional, but the 'collect' options has been removed.
Users cannot bypass the 'Add New Item' option indicating that it is mandatory, and the 'collect' button remains.
Users can easily bypass the 'Add New Item' step.
The lack of clarity regarding the optionality of adding new items is confusing..
Completed When

A job can be created easily without the need to add a new item, operatives can 'complete' a job by clicking the corresponding button at the top of the page, and the 'Collect' button has been removed from the inventory screen altogether.
Start When

When purchase order has been issued to the client.
Feature Priority
  • High Priority 
  • Medium Priority
  • Low Priority   
Client Approves Feature

  • Approved
    Once approved, inform us by email, we will close the feature checklist and begin the process.
Agreed Timeline

Once approved the process will continue as

  • Create mock ups of the feature within 14 days of 'Start When'
  • Schedule of the project will be agreed within 14 days of ‘Start When',
  • Development of the feature once mocks up have been approved.
  • Q/A and delivery 7 days after development cycle

Estimated development time for this feature would be X days,

Feature Checklist: Customer Notifications

Cover-image-WMS.png

Feature File: Customer Notifications

Scenario

 Sending automatic confirmation upon job acceptance

Given

 Fluid accepts a job in the WMS
When the job is accepted
Then an automatic message is sent to the customer confirming the job acceptance and scheduled time


Good When

Bad When
Confirmation messages sent automatically without any unintended delay.
Notifications are not sent or are unintentionally delayed.
Message includes all relevant job details, including the scheduled time and any other relevant information.
Confirmation messages don't share required information about the job.
Customers receive confirmation in a clear format without the need for additional assurance.
Messages are unreadable or unoptimised for all required devices
Completed When

Every accepted job triggers an immediate, accurate, and formatted confirmation to the customer.
Start When

When purchase order has been issued to the client.
Feature Priority
  • High Priority 
  • Medium Priority
  • Low Priority   
Client Approves Feature

  • Approved
    Once approved, inform us by email, we will close the feature checklist and begin the process.
Agreed Timeline

Once approved the process will continue as

  • Create mock ups of the feature within 14 days of 'Start When'
  • Schedule of the project will be agreed within 14 days of ‘Start When',
  • Development of the feature once mocks up have been approved.
  • Q/A and delivery 7 days after development cycle

Estimated development time for this feature would be X days,

Feature Checklist: Admin

Cover-image-WMS.png

Feature Checklist: Admin

Scenario

 Admin user wants to access admin panel and define user roles

Given

 User with admin privileges can access the admin panel through a clearly define 'admin' button on the homepage
When User can define or edit access levels for different user roles
Then System provides a clear interface for setting permissions based on user roles, changes should be savable and immediately effective across the WMS


Good When

Bad When
The interface for defining user access levels clearly categorises different permissions and roles.
Admins cannot define roles as the system doesn't allow for these edits to be made.
Administrators can easily access admin panel, add, remove, or modify user roles and their corresponding access levels.
Admins cannot access the admin panel from the homepage as there is no 'Admin' button.
The system implements changes immediately across the platform.
There is a delay in the implementation of changes across the platform, or they are not made at all.
Completed When

An 'Admin' button is present at entry level, and an admin-level user can login in and edit user capability and access levels across the whole WMS platform.
Start When

When purchase order has been issued to the client.
Feature Priority
  • High Priority 
  • Medium Priority
  • Low Priority   
Client Approves Feature

  • Approved
    Once approved, inform us by email, we will close the feature checklist and begin the process.
Agreed Timeline

Once approved the process will continue as

  • Create mock ups of the feature within 14 days of 'Start When'
  • Schedule of the project will be agreed within 14 days of ‘Start When',
  • Development of the feature once mocks up have been approved.
  • Q/A and delivery 7 days after development cycle

Estimated development time for this feature would be X days,