Nick Zeeb

Feature Checklist: Lockout Schedule

Cover-image-Nick-Zeeb.png

Feature Checklist: Lockout Schedule

Scenario

Setting Regular Lockout Periods

Given

 User accesses the lockout scheduler in mobile app
When

User sets a regular lockout period by selecting start and end times and dates and names the lockout period

image.png
Then System should save and activate the lockout period as specified and devices should be shut off and locked during these periods

Scenario

Adding Time Extensions to Lockout Periods

Given

 Lockout period is approaching its end
When

User selects to extend the time in increments of 5 minutes (up to 20 minutes)

image.png
Then System should extend the lockout period or countdown accordingly and keep the devices shut off and locked for the selected time. 

Scenario

TV lockout state is enabled by default

Given

User is setting up a lock out time
When

The time is setup
Then

the lockout state is set to on as its default setting.

Screenshot 2024-04-11 at 16.53.18.png


Good When

Bad When
Users can easily set, name, and activate both scheduled and immediate lockout, ensuring devices adhere to these schedules without fail.
There are more it takes more than 5 clicks to set a schedule excluding the name from start to enabled.
The system allows for cancellation and extension whilst running.
Setting the time is hard on a mobile phone or laptop screen.
The system can be used without any training or guidence
Reading documentation or support is required to access new features.
Completed When
  • System is able to cancel countdown timers upon user request, with immediate effect on the lockout period and device accessibility.
  • System reliably saves and activates regular lockout periods as specified by the user, with all targeted devices responding correctly by shutting off and locking at the set times.
  • System consistently allows for the editing of lockout periods, with all changes in times, dates, or names being accurately updated and reflected in the operation of the devices.
  • System provides a responsive and accurate roller selection interface for date and time settings, allowing users to precisely set or edit lockout periods with ease and efficiency.
  • System successfully processes user requests for extending lockout periods in 5-minute increments across all devices involved.
  • It takes less than 5 tap/clicks to set a new timer.
Start When

FCL and Mockup Screenshots signed off by 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 7 days of 'Start When'
  • Schedule of the project will be agreed within 7 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 10 days,

Feature Checklist: Kid's Wifi Lockout

Cover-image-Nick-Zeeb.png

Feature File: Kid's Wifi Lockout

Scenario

Setting Lockout Periods to Disable Kids' WiFi

Given

 User is setting or editing a lockout timer for devices
When

The kids' WiFi is automatically included in the lockout timer as default

Screenshot 2024-04-25 at 13.53.19.png
Then

User should be able to:

  • Set specific start and end times for the lockout that includes the WiFi
  • Activate the lockout timer, during which the WiFi network will be automatically disabled


Good When

Bad When
The option to disable the kids' WiFi network is integrated into the existing lockout timer setup a set to 'on' as default.
The system does not provide confirmation when the WiFi network is locked or unlocked.
Users can specify exact times for the WiFi network to be disabled and re-enabled, matching the lockout period for other devices.
The lockout fails to activate or deactivate at the designated times, leaving the WiFi active.
The system confirms the activation of the WiFi lockout.
The option to include the WiFi network in the lockout is unclear or absent
Completed When
  • The user can reliably schedule the kids' WiFi network to be disabled during selected lockout periods.
  • The lockout settings can be applied accurately, with immediate feedback provided to the user.
  • All designated lockout functionalities, including WiFi control, are easily managed from a single interface within the system.

OR

  • The Kids' WiFi is locked automatically along with other devices when a lockout timer (one off or regular) is set and activated.
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: Countdown Timer

Cover-image-Nick-Zeeb.png

Feature Checklist: Countdown Timer

Scenario

Setting a One-Off Lockout Timer

Given

 User wants to create a lockout time on kids' devices and WiFi without creating a schedule
When

User accesses the lockout timer feature in the home automation interface

Screenshot 2024-04-22 at 15.35.33.png
Then

the user should be able to:

  • Select the specific time for the devices and WiFi to be locked.
  • See the time remaining until the lockout engages, cancel it or extend in 5 minute increments.
  • See the time remaining until the lockout ends, cancel it or extend in 5 minute increments.

Scenario

Delaying the 'Lock' timer

Given

The lock time has been delayed 

Screenshot 2024-05-08 at 08.57.48.png
When
  1. The lock time is before the selected unlock time
  2. The lock time is after the selected unlock time
Then
  1. The unlock time remains the same
  2. The unlock time automatically sets to 5 minutes after the new lock time


Good When

Bad When
User can choose a period of time to set a one off lockout timer.
A one off time is set as a schedule 
User can see the length of time until the timer begins or ends.
User cannot extend the time until the timer starts, or end.
  User can cancel the time at any point, extend the timer in 5 minute increments and press cancel to exit the one-off timer function. 
User cannot cancel the timer at any point.
The unlock time stays the same if the lock time is delayed to a time before it is set to unlock.
The unlock time changes if the lock time is delayed to a time before it is set to unlock.
The unlock time automatically changes to five minutes after the lock time, if the lock time is set to after the original unlock time. 
The unlock remains the same, if the lock time is set to after the original unlock time. 
Completed When
  • The user can access the one-off lockout capability through the system.
  • Select a specific period of time for the lockout time to be active.
  • Choose to extend time until timer starts or end in 4-minute increments
  • Cancel the timer completely 
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: Master Switch - Boy's Devices

Cover-image-Nick-Zeeb.png

Feature Checklist: Master Switch - Boy's Devices

Scenario

Operating the Master Switch

Given

The user accesses the master switch on the app

Screenshot 2024-05-13 at 09.49.09.png
When
  1. The user toggles the switch to Red
  2. The user later toggles the switch to Green
Then
  1. The system should immediately shut off all children's devices, overriding any active settings or timers.
  2. The system should restore all the previous settings and timers as they were before the Red switch activation taking into consideration how much time has passed since the switch was activated. 


Good When

Bad When
Switching to Red locks all targeted devices, with visual confirmation provided to the user.
When switched to Red the devices remain unlocked.
Switching to Green unlocks the devices and reinstates all previous settings and timers taking into consideration the amount of time that has passed.
When switching to Green the devices remain locked and no previous settings or timers are reinstated as per the desired setting. 
The button light switches from red to green successfully confirming the current setting.
The switch light does not change between Red and Green to indicate the current setting.

Completed When

The switch successfully controls the state of children's devices and WiFi with instant effect and clear feedback provided to the user for both Red and Green settings, locking when switched to Red or unlocking when switched to Green and reinstating existing settings.
Start When

Signed off by 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,