Remove features
article thumbnail

Route to Enterprise Scale Agility

Digite

While the results we’ve seen globally are tangible and significant, a reality is that nearly all of these are scratching the surface, and are yet to fully achieve the essence of the method that we first implemented at Microsoft’s IT department in 2005. The first Kanban system at Microsoft in 2005 produced productivity gains of 230%.

Agile 94
article thumbnail

The Ultimate Guide to Kanban Methodology

Wrike

Anderson is often credited as being the first to implement Kanban in software development in 2005. Innovation and ideas for improvement should be promoted at all levels. Features to look out for in Kanban software. Other features to look for in Kanban software include: The ability to customize workflows and statuses.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Knowledgeline: Podcasting, the next big thing?:: by Tom Baldwin

Knowledgeline

Knowledgeline Thursday, November 17, 2005 Podcasting, the next big thing? Reed Smith intellectual property lawyer and popular blawger Denise Howells podcast features insightful talk about the ways in which advanced technology can help lawyers on the job. Like blogging, the barrier to entry for podcasting is minimal.

2005 40
article thumbnail

Knowledgeline: Desktop search gains momentum:: by Tom Baldwin

Knowledgeline

Knowledgeline Thursday, January 27, 2005 Desktop search gains momentum E-mail has become a most unwieldy tool. Lookouts newest version makes it easy to deploy in large environments and while it lacks some of the slick features of X1, if youre on a tight budget, this will be a huge leap forward for your users. A real pleasure to read!

article thumbnail

Next Generation Project Management Software

Rebel’s Guide to PM

This could be a reaction to old structured and inflexible systems but pushing an agenda of continuous innovation without a tangible, declared objective could be even worse. We are attracted to the latest cool application, with the potential to jeopardise the software environment.

article thumbnail

Agile Unplugged: EP01 | Mike Cottmeyer and Brian Sondergaard

Leading Agile

And in those days, so if this was 2004, 2005, something in that kind of range, in those days, then, you know, for the most part, Agile was still maybe one team of six, or eight, or 10. I mean, I don’t remember the size of that team exactly. It eventually became probably, you know, 200 people or 300 people, something like that.

Agile 79
article thumbnail

Software Estimating Resources

Herding Cats

Flint, School of Management, Working Paper Series, September 2005.”. Eva Regnier, DRMI Newsletter, Defense Resources Management Institute, Naval Postgraduate School, Issue 12, April 8, 2005. Evaluating Software Project Prediction Systems,” Martin Sheppard, 11th IEEE International Software Metrics Symposium (METRICS 2005).