Skip to content
Browse
BABOK Guide
BABOK Guide

6. Delivery Horizon

6.7 Techniques

Agile Extension to the BABOK® Guide

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

  • Real Options: used to understand the appropriate time for making decisions, and the value that each option represents.

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

  • Retrospectives: used as a means of explicitly discussing opportunities for continuous improvement.

  • Story Decomposition: used to decompose epics to stories, which represent incremental work one on solution components.

  • Story Mapping: used to elicit and model information about a solution, including notable features r 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 consistently at the Delivery Horizon; backlog management is a frequent if not constant activity.

  • Balanced Scorecard: used to provide structure to the learning process at this horizon.

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

  • Collaborative Games: used to help with team building and inspire collaboration with the working group.

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

  • Data Modelling: used to build a shared understanding of the relevant data in the problem and solution space, and as elements of the solution are constructed.

  • Functional Decomposition: used during the Delivery Horizon in the context of decomposing epics into stories, although the focus is on producing stories which have business value upon completion.

  • Glossary: used to maintain any terms or definitions that the team may develop or require over time.

  • Interface Analysis: used to describe a particular user or role using a feature, or how components of the solution will communicate with each other or to outside systems.

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

  • Metrics and Key Performance Indicators (KPIs): used to trace stories to metrics and the KPIs they are expected to affect.

  • Observation: used to understand how users perform a task or use the solution.

  • Prioritization: used to determine which features will and will not be delivered as part of the initiative and in what order. Revisited during the Delivery Horizon periodically or at an emergent need.

  • Process Modelling: used to represent processes and work that is being done to create or alter those processes.

  • Prototyping: used to create a working or non-working model of a possible solution.

  • Risk Analysis and Management: used to make decisions, especially which stories will affect which risks, and in what way.

  • Scope Modelling: used to build and maintain a shared understanding of the boundaries of the 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 implementation. Personas here can refer to stakeholders around the solution rather than roles, which are more commonly referred to in stories used in solution construction.