Project Management Software for Software Development Teams in Stockholm

Coming back in August to a board that explains itself

After the long July holiday, the first morning back is often spent reconstructing what happened. Which pull requests merged while you were away? Was that half-finished branch abandoned or handed to someone? Why did the team change approach on the API? If the answers live in chat history and one colleague's memory, the first week back goes on archaeology.

ShipSprint keeps that record as a side effect of normal work. On Team and up, the board follows GitHub: opening a branch moves the card, a merged pull request closes it. Nobody has to update status before going on holiday, so the board in August reflects what actually happened in July. Decisions go in the built-in wiki with page history, next to the work they affect, so the reason for the API change is written down where you'll look for it.

Capacity planning on Team and up counts approved leave and public holidays, including Midsummer and Christmas to New Year, so the sprints either side of the summer are planned with the people who will actually be in.

The review queue is usually the bottleneck

Most teams don't run out of people who can start work. They run out of people who can review it. Cards pile up in "in review" while everyone opens something new, and the sprint ends with lots of things nearly done.

Per-column WIP limits make that visible. Put a limit on review, and when the column is full the board shows it, which is the team's cue to finish reviews before picking up the next card. It's a simple rule that a board can enforce better than a stand-up.

New requests from product, support or other teams go into a triage inbox rather than straight onto a developer's plate. Someone decides what gets scheduled. Developers start each day on a "my day" screen with their own items, a one-tap time log and an "I'm blocked" button that pulls in the person who can help, with the context attached.

What engineering leads get on Business

Delivery forecasts on Business are recalculated from the team's measured velocity at the end of each sprint, so a date that won't hold before the summer shows up in spring, not in late June. The owner command center reads every team's board directly, and a Monday digest arrives assembled. Scorecards are built from delivered work and self-logged hours, adjusted for approved leave, and visible to the person they describe. There are no screenshots, no keystroke logging and no activity tracking anywhere in the product.

Using ShipSprint from Stockholm: the essentials

Who you're buying from. Quantuva Technologies Pvt. Ltd. in Hyderabad, India, builds ShipSprint. There's no office or local entity in Sweden. Support is by email and in-app chat.

Time zones. IST is 4 hours 30 minutes ahead of Stockholm in winter and 3 hours 30 minutes ahead in summer. When setting up the GitHub connection, start in your morning so any question is answered the same working day, Indian time.

Billing. Billing is per seat in Indian rupees through Razorpay, and your bank converts it to kronor. For how VAT applies to software bought from outside the EU, ask your accountant.

Data protection. Logs, stack traces and bug reports pasted into tasks can contain personal data covered by the GDPR. Go through the sub-processor list and the security overview and check them against your obligations and customer contracts.