Skip to content
Browse
BABOK Guide
BABOK Guide

5. Initiative Horizon

5.7 Techniques

Agile Extension to the BABOK® Guide

  • Kano Analysis: used to determine the features most relevant to satisfying the identified need and determine the best approach for delivering those features.

  • Personas: used to create a shared understanding of who the customer is; frequently a core item when Thinking as a Customer.

  • Planning Workshop: used to create a shared understanding of the approach to constructing the solution.

  • Purpose Alignment Model: used to determine the features most relevant to satisfying the identified need and determine the best approach for delivering those features.

  • Real Options: used to understand the appropriate time for making decisions.

  • Relative Estimation: used to make decisions about which features to deliver and in what order.

  • Retrospectives: used to provide teams a means of explicitly discussing opportunities for continuous improvement.

  • Story Decomposition: used to support decisions about which features to deliver, in what order, and how much of the feature needs to be delivered in order to reach the desired outcome.

  • Story Mapping: used to elicit and model information about a solution, including notable features or characteristics of that solution.

  • Value Stream Mapping: used to identify the portions of a problem or solution and identify what their ability is to alter the value of the affected item or process.
  • Backlog Management: used almost consistently in most agile approaches.

  • Balanced Scorecard: may provide measures of desired outcomes for the initiative. May be used for “scoring” different solution options or solution components for prioritization.

  • Brainstorming: used to create many options for a given problem; brainstorming is a technique well suited to agile.

  • Collaborative Games: used to identify potential solution options.

  • Concept Modelling: used to build a shared understanding of the need and potential solutions.

  • Data Dictionary: used to build a shared understanding of the relevant data in the problem and solution space.

  • Data Modelling: used to elicit information necessary for making the decisions identified in the Initiative Horizon.

  • Document Analysis: used to elicit information necessary for making the decisions identified in the Initiative Horizon.

  • Functional Decomposition: used to build and maintain a shared understanding of the desired solution.

  • Glossary: used to build a shared understanding of the problem and solution space.

  • Interface Analysis: used to elicit information necessary for making the decisions identified in the Initiative Horizon.

  • Interviews: used to elicit information necessary for making the decisions identified in the Initiative Horizon.

  • Metrics and Key Performance Indicators (KPIs): used to provide measures of desired outcomes for the solution.

  • Observation: used to elicit information necessary for making the decisions identified in the Initiative Horizon.

  • Prioritization: used to determine which features will and will not be delivered as part of the initiative and in what order.

  • Process Modelling: used to build and maintain a shared understanding of the desired solution.

  • Prototyping: used to create a working or non-working model of a possible solution. Often helps Getting Real With Examples.

  • Risk Analysis and Management: used to identify information necessary for making Initiative Horizon decisions, especially which features to deliver and in what order.

  • Scope Modelling: used to build and maintain a shared understanding of the boundaries of th desired solution.

  • Stakeholder List, Map, or Personas: used to build and maintain a shared understanding of the entities involved with or affected by the solution and its implementaton.

  • Vendor Assessment: used to provide input into decisions about which solution will satisfy the identified need.