InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

A Preview of Mingle 2.0

Posted by Ben Hughes on Apr 11, 2008

Sections
Process & Practices,
Development
Topics
Collaboration ,
Artifacts & Tools ,
Agile ,
JRuby ,
Agile in the Enterprise
Tags
Planning ,
Productivity ,
Mingle ,
Rails
On April 15th Thoughtworks will release Mingle 2.0, nine months after the initial release of Mingle. InfoQ got some time with product manager Adam Monago to talk through the new functionality provided by Mingle 2.0. Amongst a plethora of fixes and new functionality in the release the most notable are:
  • Card Trees - Mingle now uses the concept of card trees to display relationships between features, cards, defects and any other configurable entities in the system. Also it allows different views of the trees, for example a Planning view or a Developers view.
  • Cross-project reporting and one-click visibility at any level of detail - program, project, requirement or even team members can be reported on cross-project, allowing Mingle to be used as a program management tool. Charts & tables from Mingle project wikis can be securely used in the programme roll up view.
  • Calculation of key metrics across projects - Mingle 2.0 has the functionality to calcuate metrics from across the project using formulae, some examples of which are weighted estimate averages and average time to fix defects.
  • Aggregation of properties - Mingle 2.0 aggregates (or rolls up) key project metrics (including custom ones (see above)). For example task estimetes are rolled up into story estimates, which ultimately end up in release estimates.
  • Application Program Interfaces (APIs) and plug-ins to easily integrate Mingle with existing project infrastructure - Mingle now has a full set of Restful API's and a burgeoning community of developers, willing to share their experiences. such as Minglyn (due to be released on CodeHaus on the 15th.).
  • Promotion of almost any artefact to a Tab - to enable easy customisation and bookmarking of favourite pages.
  • Inclusion of more preconfigured Templates & Metrics - such as burndown/burnup charts and project templates.
Also in the mix, the Mingle team are releasing a Perforce connector and rearchitected some parts of Mingle to enable users to write their own plugins using the API.

Plans on the board for Mingle include promotion of an online Mingle community and greater user personlisation features. Pricing structure is also looking to change, with an Annual and Perpetual license supplementing the pay per seat monthly license.

Mingle 2.0 will be available from 15th April.
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

Memory usage by Richard Cowin Posted
Worth Taking Another Look at Now by Nicholas Cancelliere Posted
  1. Back to top

    Memory usage

    by Richard Cowin

    It will be interesting to see if they have reduced the memory footprint from 1GB RAM.

  2. Back to top

    Worth Taking Another Look at Now

    by Nicholas Cancelliere

    When Mingle first came out I was disappointed in a lot of ways, and especially felt it was not worth the per-user license fee they were charging. Mingle 2.0 might have me reconsider this product. I've always liked the philosophy behind the product, but didn't feel 1.0 was ready for prime-time. My team actually voted it down (we tried it out). The new features in 2.0 are huge improvements, and I think finally now it's "ready."

    I still do not agree with their pricing model.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.