: Looks beyond initial purchase price to calculate long-term operational, maintenance, and upgrade costs.
Linking requirements to project goals. Affinity Diagrams: Organizing large sets of ideas. 5. Evaluation and Implementation Ensuring the chosen solution works. Fishbone Diagram (Ishikawa): Root cause analysis. Mind Maps: Brainstorming and structuring information. Cost-Benefit Analysis: Determining financial viability.
: Parsing historic transactional logs to understand what occurred within the business over a specific timeline.
A shallow, rapid test to ensure critical features work before deep testing begins. : Looks beyond initial purchase price to calculate
A structured meeting format to identify what the team should start doing, stop doing, and continue doing.
: Validating that historical workflows still run correctly after new features or patches are implemented.
How does the work actually get done? These techniques visualize workflow and identify bottlenecks. Mind Maps: Brainstorming and structuring information
: Guided group voting methods to reconcile conflicting requirements from different business units.
Shows the life cycle of a single entity (e.g., "Order" states: New, Paid, Shipped, Closed).
Joint Application Development sessions bringing stakeholders together for intensive, facilitated requirements gathering. "Order" states: New
Data means nothing if you can’t get people to agree. These are the "techniques" of human interaction.
: High-level structural maps defining the exact boundaries of a system and its external interactions.