The last principle of the Agile Manifesto provides for learning and adjustment by the team. This adjustment allows for continuous process improvement. Teams don’t allow themselves to become stagnant or stale – they change and become better. The manifesto doesn’t proscribe how often and allows some leeway. The definition of “at regular intervals” provides sufficient… [Read more…]
February 13, 2011 by David Kohrell
The tenth principle of the Agile manifesto may be my favorite one – simplicity, the art of maximizing the amount of work NOT done. Too often methodologies, frameworks and process improvements get mired down in heavy process and documentation. It’s a balancing act. It’s important to be neither too much, nor too little – just… [Read more…]
February 10, 2011 by David Kohrell
The seventh principle of the Agile Manifesto is the simplest and shortest one. Working software is the primary measure of progress. That simplicity belies a profound philosophy and modus operandi That is the outcome trumps the process. This philosophy grates and goes against the grain of conventional wisdom. Have a problem, add process.… [Read more…]
 | Ade on Conflict of Interest–The… |
| Wideband Delphi « TA… on Wideband Delphi | |
 | fahadusmani on To-Complete Performance I… |
 | John on If Santa Thinks Chimneys Quali… |
 | DD on Organizational Process As… |
 | Olu Olufowobi on Make-or-Buy Analysis |
 | Arun on Organizational Process As… |
February 15, 2011 by David Kohrell
1