New design/development process article published on

10 Jun 2011 - 6:58am
1709 reads
Mike Myles

I coauthored an article on using a Knowledge / Importance Matrix that was published yesterday on (link to article)

It is a simple way to organize project tasks (or user stories in agile) that...
  • Communicates the overall state of a project at a glance
  • Informs teams on where best to focus resources
  • Acts to build team collaboration and consensus
  • Can be a portal into more details
If the article inspires anyone enough to try it out, I'd be very interested in hearing your experiences - what worked, what didn't, refinements, etc.


Syndicate content Get the feed