to your HTML Add class="sortable" to any table you'd like to make sortable Click on the headers to sort Thanks to many, many people for contributions and suggestions. Licenced as X11: http://www.kryogenix.org/code/browser/licence.html This basically means: do what you want with it. */ var stIsIE = /*@cc_on!@*/false; sorttable = { init: function() { // quit if this function has already been called if (arguments.callee.done) return; // flag this function so we don't do the same thing twice arguments.callee.done = true; // kill the timer if (_timer) clearInterval(_timer); if (!document.createElement || !document.getElementsByTagName) return; sorttable.DATE_RE = /^(\d\d?)[\/\.-](\d\d?)[\/\.-]((\d\d)?\d\d)$/; forEach(document.getElementsByTagName('table'), function(table) { if (table.className.search(/\bsortable\b/) != -1) { sorttable.makeSortable(table); } }); }, makeSortable: function(table) { if (table.getElementsByTagName('thead').length == 0) { // table doesn't have a tHead. Since it should have, create one and // put the first table row in it. the = document.createElement('thead'); the.appendChild(table.rows[0]); table.insertBefore(the,table.firstChild); } // Safari doesn't support table.tHead, sigh if (table.tHead == null) table.tHead = table.getElementsByTagName('thead')[0]; if (table.tHead.rows.length != 1) return; // can't cope with two header rows // Sorttable v1 put rows with a class of "sortbottom" at the bottom (as // "total" rows, for example). This is B&R, since what you're supposed // to do is put them in a tfoot. So, if there are sortbottom rows, // for backwards compatibility, move them to tfoot (creating it if needed). sortbottomrows = []; for (var i=0; i
When it comes to identifying projects in trouble, the key warning signs of personnel turnover, sponsor turnover and funding uncertainty are really late signals that confirm that the project is going off track. By and large, these things only happen after real problems have begun to entrench themselves.
So what causes a project to go off track?
ESI International's Jim Foreman lists the following:
More than anything else, these things indicate that the project is moving toward an "out-of-control" condition in the quality sense. Left unchecked, these things will result in a series of building issues with the project's stakeholders (team members, sponsors, and customers), that will ultimately destabilize the project and compromise its potential for success.
After a point, the project's stakeholders will simply vote with their feet and dollars and go elsewhere (the key warning signs that confirm the project is in trouble.)
It falls to the project manager to stay on top of developing issues during the course of the project. While it's not uncommon for there to be variance from a perfectly-controlled situation, the problems that can doom a project are best avoided before they reach an out-of-control condition.
In a nutshell, that's the real job of the project manager!
More information: The Long Island chapter of the Project Management Institute has incorporated portions of Jim Foreman's comments on identifying and dealing with problems in projects in their January 2007 minutes.
Labels: project management, quality
Welcome to the blogosphere's toolchest! Here, unlike other blogs dedicated to analyzing current events, we create easy-to-use, simple tools to do the math related to them so you can get in on the action too! If you would like to learn more about these tools, or if you would like to contribute ideas to develop for this blog, please e-mail us at:
ironman at politicalcalculations
Thanks in advance!
Closing values for previous trading day.
This site is primarily powered by:
The tools on this site are built using JavaScript. If you would like to learn more, one of the best free resources on the web is available at W3Schools.com.