Skip to content
Browse
BABOK Guide
BABOK Guide
10. Techniques
Introduction 10.1 Acceptance and Evaluation Criteria 10.2 Backlog Management 10.3 Balanced Scorecard 10.4 Benchmarking and Market Analysis 10.5 Brainstorming 10.6 Business Capability Analysis 10.7 Business Cases 10.8 Business Model Canvas 10.9 Business Rules Analysis 10.10 Collaborative Games 10.11 Concept Modelling 10.12 Data Dictionary 10.13 Data Flow Diagrams 10.14 Data Mining 10.15 Data Modelling 10.16 Decision Analysis 10.17 Decision Modelling 10.18 Document Analysis 10.19 Estimation 10.20 Financial Analysis 10.21 Focus Groups 10.22 Functional Decomposition 10.23 Glossary 10.24 Interface Analysis 10.25 Interviews 10.26 Item Tracking 10.27 Lessons Learned 10.28 Metrics and Key Performance Indicators (KPIs) 10.29 Mind Mapping 10.30 Non-Functional Requirements Analysis 10.31 Observation 10.32 Organizational Modelling 10.33 Prioritization 10.34 Process Analysis 10.35 Process Modelling 10.36 Prototyping 10.37 Reviews 10.38 Risk Analysis and Management 10.39 Roles and Permissions Matrix 10.40 Root Cause Analysis 10.41 Scope Modelling 10.42 Sequence Diagrams 10.43 Stakeholder List, Map, or Personas 10.44 State Modelling 10.45 Survey or Questionnaire 10.46 SWOT Analysis 10.47 Use Cases and Scenarios 10.48 User Stories 10.49 Vendor Assessment 10.50 Workshops

2. The Agile Mindset

2.2 The Agile Mindset, Methodologies, and Frameworks

Agile Extension to the BABOK® Guide

IIBA.org KnowledgeHub Agile Extension 2. The Agile Mindset 2.2 The Agile Mindset, Methodologies, and Frameworks

Agile is best described as a mindset because the values and subsequent principles explain ideas and attitudes with which people approach a situation, but do not prescribe exactly what they do in those situations.

Every situation is unique – there is no single “agile” approach. There are a variety of techniques, processes, and tools which can be applied in different combinations to different extents depending on the context. Agile teams are best served when they select a particular combination of techniques, processes, and tools that fit their context and help them work in agreement with their chosen mindset. This combination can be considered the team’s methodology.

There are a number of branded frameworks that fall under the broad banner of agile. These frameworks are collections of specific practices and ideas that have been proven useful in a specific context. These frameworks have some common characteristics:

  • respect for people and the importance of creativity in delivering value,
  • the importance of rapid delivery, feedback, and learning to ensure the product or service being produced meets real customer needs,
  • collaboration and communication among the team members and the stakeholder community in order to build shared understanding, and
  • break work into small slices of business value and deliver them incrementally and iteratively.

These frameworks include Scrum, Kanban, Extreme Programming, Adaptive Software Development, Lean Software Development, SAFe, LeSS, DAD, and many others.

It is important to understand that the context in which a framework worked at one time may not be the same as the context for a different initiative. There is no "one size fits all" in the agile mindset. The key to agility is to find what works in a particular context. Many teams find it helpful to combine techniques and practices from multiple frameworks to address the challenges of their context.