Insula Scheduling - Agile Sprints (public)

Insula implements an agile sprint methodology for the scheduling and delivery of all software development, customer projects, and consulting services.

• New work/projects are allocated to a specific numbered sprint which is an indication of when the work will start.

• Sprints run for a three week period in which work is conducted.

• Subject to the nature of the work, delivery of completed work can occur at any time during the sprint, or in the delivery window, the week following the sprint end date (aka "Release" week).

• Not all work is started and completed in a single sprint (ie. for projects that will run for more than three weeks).

• Completion and delivery of work will be coordinated and communicated via project management activities, ticket updates, etc. on the specifics of what is required.

Please note that all schedules are subject to change without notice.

Understanding the Schedule

Start - The sprint starts on a Monday, after which new work scheduled to start in the sprint will begin. Work continuing from previous sprints is ongoing.

End - The sprint ends on a Friday, by which time work scheduled for delivery in the sprint is principally complete (if not already delivered/released during the sprint).

Release - At the conclusion of successful review, testing and QA activities on work to be delivered in the sprint it is published/released.

• In the case of customer-specific projects these will be directly delivered to customers.

• In the case of on-premise software solutions this may be the publish of software updates, upgrades, etc. for customers to download and install.

• In the case of cloud solutions this may be the publish of updated/new cloud software.