Working with Mingle
- Share
-
- |
Read later
My Reading List
With the first release focusing primarily on collaboration, InfoQ spent some time with Jay Wallace from TW walking through the different areas of Mingle and its approach to agile project management and team collaboration.
Jay walked us through some of the key functions that are offered by Mingle, most notably:
Mingle is not methodology specific –it comes bundled with 3 templates (Scrum, XP & Agile Hybrid) which contain project properties specific to the type of methodology, however Mingle also offers the concept of user defined project Templates, allowing the user to tailor the tool to the idiosyncrasies of the approach they are using.
Everything’s a wiki – The fundamental units of Mingle are the story cards, which in themselves are small wiki pages. This means that the user can add images (finally - somewhere useful to put those cell phone pictures of drawings on white boards), links to other cards, links to pages on the project dashboard (also a wiki) and anything else a regular wiki has to offer.
Charts – Using its own wiki/SQL syntax MQL (pronounced Mee-Ql), the user can create statistical charts from just about anything that Mingle has stored in its database (including custom properties), displayed as bar charts, pie charts or pivot tables.
Grid View – Story cards a represented in a way that emulates their existence on a story wall or task board, with the ability to drag and drop cards between statuses, but with the benefit of numerous viewing angles, such as by priority, status, functional area and release to name a few, all using user editable colour coding.
History – Each entity in Mingle is version controlled, including cards, wiki pages extending to file revision changes in a linked Subversion repository. This enables tracking changes from requirements alterations right down to code modifications, all within the application. SVN integration includes a file viewer which highlights differences between file revisions. Furthermore, the application allows communication of changes in history via RSS or email, for example enabling the test team to be notified when a story becomes available for testing.
Transitions – a simple workflow engine that enables the transition of a Story Card from one state to another under certain criteria. For example automatically moving a card from ‘Analysis Complete’ to ‘Ready For Development’ – all customizable and user defined.
Tagging - Each card can be tagged with meta-data to enable further views, each of which can be saved and promoted to a project tab if so required.
Search – Mingle provides an all encompassing search engine, which will retrieve all instances of a search term from all entities, Wiki, Cards & Source Code.
Import & Export – Mingle provides the ability to import and export all data from and into Excel for further analysis, as well as the functionality to preview imported data before it is committed.
TW will be releasing the full version of the software for free for teams of 5 people or less and free to Open Source projects. Thereafter it’s paid for. Technologically, Mingle is the first enterprise Ruby On Rails application to run on jRuby, so it’ll run on anything – binary installers are provided for Windows, Mac and Linux. TW recommend a modern processor and 1.5GB of RAM for larger teams.
This is an early access release of Mingle, so the focus is primarily on enabling collaboration and teamwork. As the product matures into releases 2 & 3 (on a three monthly release cycle) it will shift focus to project management and finally team management.
You can register your interest (for joining the early access group), or wait for the full release which is scheduled for July 31st 2007.
- Sections
- Enterprise Architecture
- Process & Practices
- Architecture & Design
- Development
- Topics
- Agile in the Enterprise
- Open Source
- Enterprise Architecture
- Adaptive Leadership
- Ruby
- Project Management
- OSS
- Delivering Value
- Mingle
- ThoughtWorks
- Web 2.0
- Dynamic Languages
- Artifacts & Tools
- JVM Languages
- Productivity
- Teamwork
- Ruby on Rails
- Planning
- JRuby
- Leadership
- Software Craftsmanship
- Java
- Agile
- Collaboration
Can anyone compare with Acunote?
by
Guy Davis
Re: Can anyone compare with Acunote?
by
Simon Goldstein
Can't wait to see what's in the next few releases. I think Ruby gives them a nice edge in terms of pace of releases....
Re: Can anyone compare with Acunote?
by
Jason Carreira
Mingle's $29.50 / user / month seems a little excessive, especially compared to Acunote...
Re: Can anyone compare with Acunote?
by
Gleb Arshinov
Firstly, congratulations to the Mingle team on their launch. I think it's a great product. Mingle and Acunote share fundamental philosophy that Agile tools should be, well, agile. We are not your daddy, we are your tool vendor -- we are not here to tell you what to do, we are here to enable you to do what you do better. Chad Wathington from TW has a great post on this.
From the start of Acunote, we aimed to provide a small number of powerful primitives, enabling the user to model complex real-world behavior. For us that means hierarchical tasks where you don't have to commit and can model the hierarchy to your needs. (Acunote "task" is like Mingle "card"). This was challenging to implement, but leads to a superior user experience, so it was well worth it. Good luck to Mingle team on doing it for release 2 :-) Other features, like tags and task ordering also fall into this category. Advantage Acunote.
The other part of tool agility is configurability. If you want to estimate your tasks in bananas/parrots/Fibonacci numbers or call your time-boxes iterations/sprints/quests you should be able to. Not sure about parrots, but Mingle supports this while we have this planned in our backlog. Advantage Mingle.
We both agree that Agile project management is half about project management half about collaboration. Acunote made a conscious decision to start with PM features, while Mingle started out with collaboration. We are now turning our attention more toward collaboration, with comments, email notifications, etc. An astute observer would find MediaCloth an initial cut of our open-source MediaWiki language parser in Ruby. This is not yet part of Acunote, but we don't exactly plan to throw it away :-) We've also integrated with existing tools -- Bugzilla, Mantis, Trac, JIRA. Advantage -- it depends.
Source control integration -- Acunote integrates with Subversion and Perforce, both over network. We have a great code review functionality, I think this is an essential best practice and it takes tooling to actually do it effectively. Mingle has changeset-card linkage and related Trac's functionality. Advantage -- it depends.
Acunote is a hosted application. Mingle is pioneering JRuby-based product approach. We consider SaaS model an esential part of our offering, and we've partnered with Engine Yard for hosting, because our customers deserve the best. The efficiencies of hosted approach are one way we keep our costs down. This model also lets us roll-out new code frequently and in small increments, and provide high level of support. Which, of course, means nothing if your 5 person team wants to deploy the product behind the firewall. Advantage -- it depends.
Inteface -- the reality is that we are not each-other's biggest competition, Excel is. Time and time again we get feedback that a user should be able to enter 10 tasks without switching screens, clicking around and waiting. That's why we've built a powerful AJAX task list interface where you can create, estimate, decompose, edit, complete, reorder and filter tasks on a single page. You can edit task description, status, owner and estimate with 1 click. You can track analytics, completion estimates, work with tags all on the same page. Everything has a keybinding, and if you are used to Emacs/VI/Gmail you'll find yourself right at home. Bottom line -- you can enter and keep track of a full project plan with fewer actions than in Excel. Advantage Acunote.
There are more features to compare, and I'll leave it to others. As both tools evolve and compete functionality gaps on both sides will be filled-in, and new advances will be made. Customers will benefit and with both companies being Agile, also drive the innovation. That's a good thing.
Re: Can anyone compare with Acunote?
by
Hugo Palma
Re: Old hat
by
Jason Carreira
Yawn. redMine does it better... oh and it's free.
Thanks for the pointer to redmine... looks pretty slick, and you can't beat the price!
Re: Can anyone compare with Acunote?
by
Gleb Arshinov
Re: Old hat
by
Ben Hughes
TargetProcess vs Mingle
by
Nick Coyne
Re: Can anyone compare with Acunote?
by
Martin Bayly
Mingle project Management
by
matt tulum
Thanks to the Mingle team and please keep up the great work guys and gals.
Educational Content
.jpg)
Managing Build Jobs for Continuous Delivery
Martin Peston May 24, 2013
Clojure in the Field
Stuart Halloway May 23, 2013
Tuning the Size of Your Thread Pool
Kirk Pepperdine May 23, 2013
Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think