Project Management Software for Software Development Teams in Vienna

A board that doesn’t depend on who remembered

When a codebase is shared between a Vienna team and developers elsewhere, whether a second office, a nearshore partner or a few remote contractors, nobody sees anyone else finish work. Status comes second-hand, and a card stays in “in progress” for days after the branch merged because the person who’d move it was in another meeting.

On Team and up, ShipSprint takes that job away. A branch linked to a card moves it, and a merged pull request closes it. The board shows what GitHub shows, to everyone in the workspace, wherever they are.

Code review is the other usual bottleneck. Per-column WIP limits on “in review” stop pull requests from piling up behind a reviewer in another office, and make the queue visible before it costs the sprint.

Sprint planning across offices and holidays

On Business, delivery forecasts are recalculated from the team’s measured velocity as each sprint closes. Everyone, in Vienna or elsewhere, sees the same projected date, so the scope discussion can happen early and in writing.

Capacity planning on Team and up counts approved leave and out-of-office. Austrian teams should plan around Christmas to New Year, Easter and the July and August summer holidays, when long leave is common. Spring church holidays such as Ascension, Whit Monday and Corpus Christi also take days out of May and June sprints. Colleagues in other countries keep their own public holidays, so record each person’s days off rather than assuming one calendar.

Nothing in ShipSprint monitors developers: no screenshots, keystroke logging or activity tracking, which matters if your works council reviews new tools. Business scorecards use delivered work and self-logged hours, are adjusted for leave and are visible to the developer they describe.

Using ShipSprint from Vienna: the practical side

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

Time zones. IST is 4 hours 30 minutes ahead of Vienna in winter and 3 hours 30 minutes ahead in summer. If the GitHub connection needs help, ask in your morning with the details; replies usually come the same working day, Indian time.

Billing. You pay per seat in Indian rupees through Razorpay, and your bank converts to euros. How Austrian VAT and the reverse-charge rules apply to software bought from outside the EU is a question for your tax adviser.

Data protection. Developer names, emails and any customer details pasted into bug reports are personal data under the GDPR. Compare the sub-processor list and the security overview with your obligations and client contracts, and keep secrets out of tickets.