Re·quire·ment n. 1. Something that is required; a necessity. 2. Something obligatory; a prerequisite.¹ Among the twelve principles of Agile, that one that evokes a good amount of debate is changing requirements, even late in development. This contrasts from plan driven approaches to development that “freeze requirements” and lock those in through development and deployment. … [Read more…]
February 1, 2011 by David Kohrell
We make stuff happen! Adjust some capital letters and you get WEMSHA (pronounced Whim Shaw)! That’s been a working term for us at TAPUniversity the last several years. A WEMSHA mindset helps keep focus among competing methodologies, approaches and flavors of the month – Agile/SCRUM, FDD, Lean, SDLC, RUP, Iterative, Incremental, Change or Plan… [Read more…]
December 28, 2010 by David Kohrell
Synonymous term or a different term, that’s a common question we receive in our course delivery for secondary versus residual risks. Those two terms do sound quite a bit a like. Are they? They’re similar concepts but are different! Secondary risk occurs once a risk event triggers and the appropriate management response strategy deployed. The… [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 5, 2011 by David Kohrell
5