| Characteristics of Agile Reports | ||
| Bounded Chaos | Self Building | Broad Scope |
|
- Random actions inside of the boundary - Boundary determined by available data |
- Developer builds 90% - User checks options - Program finishes writing itself - Program creates report |
- Can replace millions of fixed reports - Requirements can be hazy up front |
| Project Management Characteristics | |
|
Agile Basis
|
Traditional Basis
|
|
Changing environments (driven by) - Philosophies, Personal relationships, Timing, Documentation - Methods based on Approach & Principles - Programming – low level practices for some methodologies |
Rigid, known environments (driven by) - Static processes - Structured Methods - Waterfall project management & clones |
|
Process Style: Adapts to Business Changes - Empirical process - Start with a plan - Change plan frequently - Use "Inspection & Adaptation" to control change |
Process Style: Discourages Changes - Defined the process - Plan what you expect – make predictions - Enforce the predictions - Use “Change Control” to manage change |
|
Management Style: Leadership & Collaboration - Bottom up control - Initiative encouraged - Large pool of ideas, creativity encouraged - Continuous contact with customer Dangers (management must spot & handle): - Lack of communication, losing sight of goals - Friction from clash of egos - High turnover of workers handling cyclical & routine processes |
Management Style: Command & Control - Top down control - Permission required - Rigid processes & chain of command - Little contact with customer, except by management Dangers (management must spot & handle): - Stagnation, analysis paralasys, bottlenecks, backlogs - Friction from stiffled ideas - High turnover of most creative people |
|
Most Useful: Volatile business environments, rapid changes, judgement needed, creativity required | Most Useful: Known processes such as vendor & hardware upgrades, no decisions, little creativity needed |
