Project Management Software for Software Development Teams in Reading

Lots in progress, not much done

A common pattern on a busy development team: everyone has two or three things open, the review column holds a dozen pull requests, and the sprint ends with plenty of work nearly finished. Each developer is busy, but code isn't reaching production, because starting something new feels more productive than reviewing someone else's change.

Per-column WIP limits are the simplest fix. Set a limit on in progress and another on review. When review is full, the board shows it, and the next developer to free up reviews a colleague's pull request before opening a new branch. It feels slower for a day and is faster by the end of the sprint.

On Team and Business, ShipSprint connects to GitHub, so the columns stay accurate without anyone dragging cards. Starting a branch moves the card into progress and merging the pull request closes it. The WIP limits are therefore counting real work, not cards someone forgot to move.

Bugs that arrive mid-sprint

The other drain on a sprint is unplanned work. A production bug comes in, someone fixes it, and the planned feature slips without anyone recording why.

ShipSprint's triage inbox is where every new request, bug or feature lands first. The lead or whoever is on triage that week decides whether it's urgent enough to enter the current sprint or goes to the backlog. Urgent items join the board as cards, so the sprint review can show exactly what was added and what it displaced.

On Business, delivery forecasts are recalculated from measured velocity as sprints close, so a run of interrupted sprints shows up as a moving forecast date long before the deadline itself.

Using ShipSprint from Reading: notes for the team lead

Who you're buying from. Quantuva Technologies Pvt. Ltd. develops ShipSprint in Hyderabad, India. We have no office or local entity in the UK; support is through email and in-app chat.

Time zones. IST is 5 hours 30 minutes ahead of Reading in winter and 4 hours 30 minutes ahead in summer. Replies usually come the same working day, Indian time, so a problem connecting GitHub reported in your morning will normally be picked up while you're still at work.

Billing. Each seat is charged in Indian rupees through Razorpay, and your bank converts it. For VAT on software services bought from abroad, check with your accountant.

Data protection. Bug reports and logs pasted into cards can include user data covered by the UK GDPR and the Data Protection Act 2018. Read the sub-processor list and security overview, and check them against your obligations and any customer contracts before doing so.

For sprint planning, capacity on Team and up counts approved leave and the public holidays, notably the bank holiday weekends, Easter, and Christmas to New Year.