Campus Edition In Progress Board
This page gives a real-time snapshot of the work the Talis Aspire Campus Edition development team currently has in progress. Click here to read about how the board works.
NEW: Small defects are now progressed by the support team. View the current defects stack
The stackStory at the top gets implemented next |
In progressDevelopers drinking 5.2 espressos per hour |
Next releaseDue 3pm on Thursday 16th February |
|---|---|---|
|
Est. wait 8 days New feature: Assign a List OwnerImprovement: Search by list owner New feature: Acquisition review states New feature: Implement higher-performance report runner with date, text and select-style filters Improvement: Make recent updates faster New feature: Create new report type to run against universe.talisaspire.com |
Improvement: Allow handing of eBook data retrieved via DOI Improvement: Optimise Javascript files by minifying and consolidating files Improvement: Improve the "This resource appears on" functionality + provide a warning when editing (and option to create a new resource) Improvement: Allow bookmarking from sites with malformed URLs Improvement: Consolidate calls to Google Books JSON API into one AJAX request Improvement: When bookmarking, allow catalogue ID to be passed to Dynamic Parser Improvement: Retain student numbers when a review is completed Task: Create Bookmarking Recognizers Improvement: Make Dynamic parser ignore title when any of the RFT title is present |
No stories awaiting release at present |
How the board works
Stories (or cards) on the left hand side sit in the stack waiting to be picked up by developers. The developer always picks up the next card at the top of the stack. As they are picked up and progressed through development, they travel from the left hand side of the board to the right. They eventually leave the board completely once they are released and available for use by customers.
We release new features on a regular basis, usually every week.
By monitoring the average time it takes for stories to travel through the board, Talis can predict the average time customers will have to wait to use the feature from the point a card is picked up by a developer (i.e. leaves the top of the stack and coding starts) to when it leaves the board completely (i.e. is live and released into product). Predicted wait times will be shown on the top of the stack column on the left hand side.
Are all stories displayed on the In Progress Board?
No - there are some exclusions. For example, specific project work for customers is not included, nor are very small stories such as changes to wording or labels. If we are fixing security defects these are also suppressed. Prototyping, research and very technical stories without direct customer value are also hidden. This means that sometimes the In Progress column might look a little light - but rest assured, we're always working hard to deliver a better system!