Project Management Software for Software Development Teams in Munich

Work rarely stalls in development

Ask a development team where a sprint went wrong and the answer is seldom "we wrote code too slowly". Work stalls after the code: pull requests waiting for review, builds waiting for a test rig, features waiting for someone from another team to sign off. On most boards all of that sits under "In progress", so nobody can see the queue.

ShipSprint lets you split those states into their own columns and give each one a WIP limit. When "In review" hits its limit, the board makes the bottleneck plain, and the team can stop starting new work and help clear reviews. For teams building software that ships with a device or into a machine, a separate "Waiting for test hardware" column often tells you more about the release date than the whole backlog does.

On Team and up, the board follows GitHub. Creating a branch for a card moves it into progress, and merging the pull request closes it, so the card's position reflects the repository without anyone dragging it.

Will the milestone hold?

When the release date is fixed by a hardware schedule or a customer's plan, the only question that matters each sprint is whether the remaining scope still fits. On Business, ShipSprint answers it from the team's measured velocity, recalculated as each sprint closes. A milestone drifting out of reach shows up while there is still time to negotiate scope, which is a much better conversation than explaining a miss.

Unplanned work is the other threat. Bug reports and requests from other departments land in a triage inbox, and a lead decides what enters the sprint. The interruption becomes a visible decision, with its effect on the forecast, instead of a favour done quietly.

No monitoring, and the works council

There are no screenshots, keystroke logs or activity tracking in ShipSprint. On Business, scorecards come from delivered work and the hours developers log themselves; they are adjusted for approved leave and visible to the person they describe. If your company has a works council (Betriebsrat), software that could be used to monitor performance usually needs its agreement. Those facts make the discussion simpler, but the decision belongs to the works council.

Capacity planning on Team and up counts approved leave and public holidays. Christmas to New Year and Easter are the obvious gaps before a milestone. Public holidays and school summer holidays differ by state, so a Munich team on Bavaria's calendar and a supplier or test lab in another state may not be off on the same days. Put both into the plan before committing a date.

Using ShipSprint from Munich: before you connect GitHub

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

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

Billing. Per seat, in Indian rupees, through Razorpay; your bank converts to euros. How VAT applies to a service bought from outside the EU is for your accountant.

Data protection. Bug reports and logs pasted into tickets can contain personal data covered by the EU General Data Protection Regulation (GDPR). Read the sub-processor list and the security overview, then check them against your obligations and customer contracts. Two-factor authentication is available to every user, and every workspace is an isolated tenant.