Orangescrum vs. SpiraPlan

This is a good thing for medium/large companies for inside the company and/or for interacting with remote employees/freelancers. As the program facilitates the interaction between employees and managers it speeds up the distribution of tasks and allows managers to identify possible problems on the fly. For indie developers - it's a little expensive.

Incentivized

We selected SpiraPlan because the workflow allows us to start simple without adopting an entire methodology. It suits small teams and single users really well.

• We tested the free version of the program. It improved communication within the team.
• Allowed to trace performance and time spent on tasks. Each team member was aware of the status of the tasks and could plan their work.
• Simplified interaction with managers, as it could present the results in the form of Gantt charts.

Incentivized

• Flexible requirements organisation structure. I'm able to group and sub-group requirements as I see fit.
• Competitive product pricing. Paying by active use instead of registered user was the winning point.
• UI is straightforward and easy to use.

• The program interface is overloaded. Especially when there is little time for a detailed description of the tasks.
• I would like a faster way to publish the result at the completion of the task.
• Projects and tasks are two different workspaces/pages. Personally, it would be more convenient to combine these things.

Incentivized

• Access from South East Asia is rather sluggish. Could be due to server location.
• Complimentary phone app to do simple tasks (e.g. create tasks, create requirements, add comments) offline would be beneficial because access to the internet can be an issue at the customer's environment.

Trello was excellent, but we did not choose it because of the price and relatively positive feedback from employees using Orangescrum who wanted the easiest and fastest way to create reports so as not to be distracted from work (as a two-click report).

Incentivized

Main differentiating factors: 1. Lightweight process 2. Plans based on active users instead of registered users.

• It accelerated the work of the team, but the mastering of the program interface was slow.
• The interface is not intuitive. It proved to be quite complicated.
• For managers, the program has facilitated reporting and streamlined team tracking.

Incentivized

• Allows us to manage simple IT requirements without major upfront costs. Allows us to expand our process complexity at our own pace.
• Slow UI response from a South East Asia country can make data entry a drag.