Project Management Software for Software Development Teams in Kuala Lumpur

Everything is "in progress", nothing is done

A common shape for a struggling sprint: every developer has started three things, the review column is full, and on the last day a handful of cards are merged in a rush while the rest roll over. Velocity looks erratic, and nobody can quite say why.

The cause is usually work in progress. Starting new tasks feels productive, but each one waits on a reviewer who is also busy starting new tasks. A board without limits hides this until the sprint ends.

ShipSprint lets you set a WIP limit on each column. When review is at its limit, the board shows it, and the sensible next move becomes reviewing someone else's pull request rather than opening a new branch. It's a small rule that tends to make sprint endings much calmer.

Velocity you can plan with

Once WIP is under control, velocity becomes something you can use. On Business, ShipSprint recalculates delivery forecasts from the velocity the team actually measures as sprints close. If the date for a release drifts, it shows up weeks ahead, not at the demo.

That forecast is only as good as the capacity behind it, and in Malaysia the weeks that most reduce it are Hari Raya Aidilfitri, Chinese New Year and Deepavali. On Team and up, capacity planning counts approved leave and out-of-office, so a sprint spanning Chinese New Year is planned for the developers who'll be at their desks. The working week is Monday to Friday in most states; if part of the team sits in a state with a different weekend, account for it when you schedule reviews and stand-ups.

Developers log time in about five seconds next to the task they just finished. Reminders go to the developer, not to the lead. There's no screen capture, keystroke logging or activity tracking, and on Business, scorecards are adjusted for leave and visible to the person they describe. Every assistant action is in the workspace audit log on Business.

Using ShipSprint from Kuala Lumpur: practical notes

Who you're buying from. ShipSprint is built by Quantuva Technologies Pvt. Ltd., Hyderabad, India. No office or local entity exists in Malaysia; support is by email and in-app chat.

Time zones. IST is 2 hours 30 minutes behind Kuala Lumpur year-round. If you're connecting GitHub or importing a backlog, do it in your afternoon, when the Indian working day is under way, and expect replies the same working day, Indian time.

Billing. Seats are charged per user in Indian rupees through Razorpay; your bank converts to ringgit. Whether Malaysian service tax applies to the subscription is a question for your accountant.

Data protection. Code stays in GitHub, but tickets, logs pasted into cards and wiki pages can contain personal data covered by the Personal Data Protection Act 2010. Read the sub-processor list and the security overview, and check both against your own obligations and any client contracts. Each workspace is an isolated tenant, and every user can turn on two-factor authentication.