Project Management Software for Software Development Teams in Santiago

The card that says "in progress" for a week after the merge

Every developer has done it: finish a change, open the pull request, get it reviewed and merged, and move on without touching the card. Multiply that by a team and the board drifts away from the code. Standups become a round of corrections, and the sprint review opens with ten minutes of "let me check whether that's actually done".

A stale board is more than untidy. When the board is wrong, so is every number built on it, and the lead who plans the next sprint is planning from fiction.

On Team and up, ShipSprint takes card status from GitHub. A branch linked to a card moves it forward when work starts, and a merged pull request closes it. Nobody has to remember to drag anything, so the board reflects the repository and the review can start with the work itself.

Sprint planning through the summer holidays

Some months take far more people out of a Chilean team than others. January and February are the summer holiday months, and the Fiestas Patrias around 18 September remove days from that sprint too. A plan that assumes November's pace through February will slip.

On Team and up, out-of-office and approved leave are part of capacity planning, so the sprint you commit to in January accounts for who is away. On Business, delivery forecasts are recalculated from the team's measured velocity at the close of every sprint. After a summer sprint at reduced strength, the projected date moves with it, and you find out in January rather than in March.

Time logging on Team takes about five seconds next to the card you just closed, and reminders go to you, not to your lead. ShipSprint has no screenshots, keystroke logging or activity tracking. On Business, scorecards are leave-adjusted, so three weeks of approved leave don't count against anyone, and each developer can see their own.

Using ShipSprint from Santiago: what an engineering lead should know

Who you're buying from. Quantuva Technologies Pvt. Ltd. makes ShipSprint in Hyderabad, India. It has no office or local entity in Chile; support runs over email and in-app chat.

Time zones. IST is 8 hours 30 minutes ahead of Santiago in January, while Chile runs on summer time, and 9 hours 30 minutes ahead in July. Support replies normally come within the same Indian working day, which overlaps very little with yours. Write up a GitHub connection problem with the repository name and the error text so it can be solved in one reply.

Billing. Billing is per seat in Indian rupees through Razorpay, and your bank turns the charge into pesos. For how IVA applies to software bought from a foreign provider, ask your accountant.

Data protection. Law 19,628 is Chile's current personal data law, and Law 21,719 is on track to replace it. Code stays in GitHub, but issue text, logs and user reports pasted into cards can contain personal data. Read the sub-processor list and security overview and check them against your obligations and any client contracts.