Magic marker analogy
- 1. Project ManagementMethodologies explainedusing the Magic Marker Analogy. Thissimple explanationcanbe done usingthe toolsfoundinmostJAD rooms. The marker tip(left) couldbe usedtoindicate Requirements,The markerend(right) couldindicate testingandUAT. Waterfall  High Business Involvementat the beginning and end (Requirements & Testing)  High Business Analystinvolvement at the beginning  Variablestaffing within project Iterative Non-concurrentiterations  High Business Involvementat the beginningand end of each iteration. o (Requirements & Testing)  High Business Analystinvolvement at the beginning.  Variablestaffingwithin iterations/ within project.  Same personnel could be used for each iteration. Concurrent iterations  High Business Involvementat the beginning and end of each iteration. o (Requirements & Testing)  High Business Analystinvolvement at the beginning.  Variablestaffingwithin iterations/ within project.  There is a potential for Business involvementoverlap to more than 100% o The example here is QA for iteration 1 whilein Requirements for iteration 2  Dev and other teams have overlappingwork It is importantto note the overlaps which may increase. This method may cut down on time, but will requireadditional staffing. Agile  High Involvement in each Sprint o Product Owner (Business) o Development o BA’s o QA o Other  Quick turnaround of incremental product