Project Management Software for Software Development Teams in Toronto

Merged is not the same as released

Teams that deploy continuously can treat a merged pull request as done. Teams that release in windows can’t. Work is merged, then waits for a release candidate, then for testing sign-off, then for the window itself. If the board stops at “done” when the code merges, nobody can see how much finished work is queued for the next release, or which items missed the cut.

ShipSprint splits the job in two. On Team and up, the development board follows GitHub: a branch moves its card into progress and a merged pull request closes it, so the board shows exactly what has merged. The steps after merge go on a release checklist for each window, built from an operations template, with a named owner for the release candidate, testing sign-off, deployment and verification. Per-column WIP limits on the development board show when too much is sitting in review or test, which is usually the real constraint on what makes the window.

Requests that arrive during a freeze, a production bug or a late feature ask, go into the triage inbox. The lead decides whether each one justifies an exception or waits for the next window, and that decision sits on the card.

Will it make the window?

The question a release manager asks every week is whether the planned scope fits before the freeze. On Business, ShipSprint forecasts delivery from the team’s measured velocity, recalculated as each sprint closes, so a scope that won’t fit shows up while there’s still time to move items to the next window rather than in the last days before the freeze.

The decisions behind a release, such as why a feature was held back or what the rollback plan is, belong in the built-in wiki with page history, linked to the cards. Any sentence on a release page can be turned into a task.

Developers can keep their attention in the editor. On Team and up, Claude Code, Cursor, Claude, ChatGPT and Antigravity connect to the workspace over MCP, acting with the developer’s own permissions, and on Business each assistant action is in the workspace audit log.

Buying ShipSprint from Toronto: four checks

Who you’re buying from. Quantuva Technologies Pvt. Ltd., in Hyderabad, India, builds ShipSprint. It has no office or local entity in Canada, and support is by email and in-app chat.

Time zones. IST is 10 hours 30 minutes ahead of Toronto in winter and 9 hours 30 minutes ahead in summer. Support generally replies within the Indian working day, so try the GitHub connection and your release columns during the trial, well before a real freeze.

Billing. Seats are billed in Indian rupees through Razorpay, and your bank converts them into Canadian dollars. Ask your accountant how HST applies to a service from abroad.

Data protection. PIPEDA applies to most private-sector organisations in Canada, alongside provincial laws in some provinces and any client contract terms. Production logs and bug reports can contain personal information, so review the sub-processor list and the security overview against your obligations before pasting them into cards.

Freezes, windows and holidays

Release calendars and public holidays tend to collide. Capacity planning on Team and up counts approved leave and out-of-office, so a release planned near Canada Day on 1 July, Thanksgiving in October or the Christmas to New Year period is planned with the people who will actually be there to ship and support it.