- Why Agile?
by Mingle Team - February 27, 2013
Visibility is critical for the success of an Agile project. Particularly when dealing with multiple teams spread across multiple time zones. In this slideshare we analyze how effective rollups are in providing the such visibility while exploring other reporting metrics.
by Mingle Team - February 26, 2013
We offer a variety of ways for you to extend Mingle and integrate it with other products that you use, to create custom experiences, reports and features. We start off this blog series with one key way of extending Mingle: using RESTful APIs.
by Mingle Team - February 12, 2013
How do you measure progress on an Agile project? What is the best way to get much-needed visibility into the status of your projects and programs? Is the burndown the answer?
by Emily Luke - January 15, 2013
Here at ThoughtWorks, we are dedicated to teaching and learning. We recently conducted an internal workshop on design thinking and customer discovery for a group of our junior consultants. The workshop began with this assignment: "Go out into the world and find a problem. When you come back, we'll try to solve it." It was interesting to see the problems that were identified and explored and exciting to watch the groups use design thinking (a totally new topic for many) to try to solve those problems. Below are the key take-aways from our workshop--these are good general guidelines for anyone to follow when approaching problem solving. We hope these guidelines help you (or at least inspire you to conjure Vanilla Ice, "If there is a problem, yo...I'll solve it"). Feel free to comment on this post if you think we missed some!
by Barry O'Reilly - January 7, 2013
We are in one of the most interesting and disruptive eras of business change the world has known. The landscape and competitive environment is evolving at rates we have not seen before, and it’s only going to accelerate. The average life expectancy for an organisation is plummeting from 67 years in the 1920s to 15 years today, according to Professor Richard Foster from Yale University. At the current churn rate, 75% of the S&P 500 will be replaced by 2027.
by Melissa Doerken - December 22, 2012
With our 12.4 release, the Mingle team fleshed out its program management functionality by introducing a program backlog feature. This post is our story about how we designed this solution using problem interviews, principles and prototypes to arrive at a new program backlog.
by Melissa Doerken - December 20, 2012
On the Mingle team we believe continuous improvement is paramount to consistently delivering real value to our customers. We invest in it heavily to minimize waste and always look for opportunities--both large and small--to improve how we work. A recent example of how we’ve improved our process has been whittling and “WIP-ing” our wall. And it all began with a call to action by what had become our “weighted” wall.
by Melissa Doerken - December 17, 2012
As part of our efforts to embody lean and agile principles, we always try to limit how much we’re working on at any given time. Working in small batches and employing WIP limits not only focuses our attention on what’s already underway, but also helps us break down, prioritize and rank upcoming work.