What’s New in Mingle 3.3?
We allow teams to fully define their own processes be they Scrum, XP, DSDM, Lean, Waterfall or some hybrid and then we allow them to regularly reflect on their processes, improve and change.
Prince joined ThoughtWorks in 2005 as a consultant business analyst and has served ThoughtWorks and it’s global customers in India, the UK and the US. She has worked with a variety of platforms and technologies, consulting for insurance, financial services, and new media companies. Since joining the product division as a business analyst on the development team for Mingle, she has worked at ThoughtWorks Studios offices in Beijing and San Francisco where she recently transitioned into Product Management. She holds a first class BSc. in Biological Sciences and an MSc. in the Biodiversity and Taxonomy of Plants, both from the University of Edinburgh, Scotland.
ThoughtWorks’ Mingle Agile Project Management Tool recently reached version 3.3, and now integrates with ThoughtWorks Studios’ ‘Go’ tool. In this interview, JAXenter speaks to Suzie Prince, who is responsible for defining the future vision and roadmap for Mingle, on what’s new in the 3.3 release, and what we can expect from the future of this project…..
JAXenter: How has the user management improved in Mingle 3.3?
Suzie Prince: First of all we have an exciting new feature called User Groups. This feature allows administrators to create and manage project user groups, use these groups to manage workflow permissions within a project and share groups in project templates. We hope that this feature will further improve workflow creation whilst still allowing users to manage their team members in a way that makes sense to them.
In keeping with our theme to improve user management across the product we have also given administrators the ability to add users to one or more projects at once and assign a user’s project permissions when adding them to a project to allow for more efficient project membership management. The ability to see user last login information and the ability to filter out deactivated users has also been added aiding user management at the Mingle instance level.
JAXenter: What does the new integration with Agile release management solution ‘Go,’ add to the Mingle experience?
Suzie Prince: Mingle is just one part of our Agile ALM solution and Mingle 3.3 is strengthened by the integrations with our release management product, Go. The pipeline status gadget provides improved visibility into the health of software builds directly within Mingle. This means that teams as well as project stakeholders can quickly see a consolidated view of project health including burn-ups, burn-downs, defect counts and build status from a single location.
JAXenter: Mingle claims to be able to manage
any Agile method. How is this
Suzie Prince: We believe in true agility and process evolution and Mingle is firmly built on this belief. We allow teams to fully define their own processes be they Scrum, XP, DSDM, Lean, Waterfall or some hybrid and then we allow them to regularly reflect on their processes, improve and change. All our structures, fields, attributes, workflows, user groups and projects are fully customizable to allow teams to work the way they want. I’m not just talking about a few fields that a user can configure but complete flexibility to define the way you work.
Having said that to help customers who are new to Agile we offer a number of templates (Scrum, XP, Agile Hybrid, Story Tracker) available right in the project to act as a baseline for beginners to build on and change as they learn about what their own needs are.
JAXenter: What’s next for the Mingle Agile Project Management tool?
Suzie Prince: We are looking to further expand on our project and team beginnings to help organizations adopt Agile across their organizations and Enterprises. This includes more integrations with the rest of our product suite as well as extending support beyond the project to program management. At the same time we will continue to hold true to our roots meaning flexibility, visibility and collaboration will continue to be as important as ever.
Ultimately we want to help customers build and release valuable software. To us that means providing them with usable, best of breed tools that support the way our customers work and remove the shackles of prescriptive and heavy weight processes, leaving people free to build their own best of breed software.