BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage News Mingle 1.0 Released: Reactions

Mingle 1.0 Released: Reactions

Mingle, agile project management software from ThoughtWorks Studios has been released.  It is available at no cost to communities, non-profit organizations, open-source projects or for commercial enterprise with five licenses or less.  For commercial use for the sixth and subsequent users, there is a subscription model on a per-user basis.  At the time of the project launch, the pricing model for each of these additional users was as follows:
  • three-month recurring subscription for $177 ($59 per month, $708 per year)
  • six-month recurring subscriptions are discounted 10% over the three-month price price, or $318.60 ($53.10 per month, $637.20 per year)
  • twelve-month recurring subscriptions are discounted 20%, or $566.40 ($47.20 per month, $566.40 per year)
Community reactions to the early access releases of Mingle have been mixed. 

Eleutian SpeakENG Development Blog's first impressions overview:
It's slick. It's flexible. It's... a little slow. ... That said, we're using it.
Silver Stripe Blog's reactions to a demo:
One of the things I expected was that the tool would be very agile specific. It turns out that because of the wa[y] properties can be defined, it’s a very generalised tool. I was talking to Mahesh Krshnan, the Project Manager for Mingle in Bangalore, and he was telling me how you can use it for tasks as varied as managing conference calls and bug tracking by creating appropriate custom properties. While this makes the tool very generalisable, it also means that its hard to take advantage of agile specific knowledge.
Kamal Fariz Mahyuddin on Accunote vs. Mingle:
My take on it: use Acunote to get you off the ground quickly but invest time in perfecting your ideal project management tool with Mingle's cards, transitions and MQL
On another front, Jordan of the Corkboard blog questions the use of JRuby:
What ThoughtWorks should have done is leverage their authority to make Ruby and Rails more accepted. Rather than wasting time with JRuby, which I feel has no long term value, they could have made the world’s greatest Rails deployment system.
For more information, read about Mingle's features and its use of JRuby, or visit the project's web page.

Rate this Article

Adoption
Style

BT