How do agile principles and methodologies influence modern business analysis practices?

Agile principles and methodologies significantly influence modern business analysis practices by fostering a mindset focused on delivering continuous business value, adapting to change, and promoting collaboration. This evolution moves business analysis beyond traditional software development into diverse business domains.

Here’s how agile principles and methodologies shape modern business analysis:

• What is Agile Business Analysis?
  • Agile business analysis is the practice of business analysis within an agile context, guided by an agile mindset. It aims to provide a competitive advantage in fast-paced and complex environments, extending beyond software development to any business domain where rapid change occurs.
  • It focuses on maximising business value, leading to better and more timely business outcomes.
  • A key element is inspecting and adapting, where feedback at one planning horizon influences decisions across all horizons, leading to changes in work.
• The Agile Mindset
  • Agile is fundamentally a mindset or way of thinking about work, rather than a specific set of practices or techniques.
  • This mindset is rooted in human values such as respect, courage, collaboration, continuous learning, customer focus, and value maximisation.
  • The main aspects of an agile mindset include:
    • Delivering value rapidly and consistently.
    • Collaborating courageously.
    • Iterating to learn.
    • Simplifying to avoid waste.
    • Considering context and adapting to realities.
    • Reflecting on feedback and adapting both product and process.
    • Producing the highest quality products.
  • The goal of applying an agile mindset is to maximise the outcome (value delivered) with minimum output, which translates to “do less and do the right things, right”.
• Influence of the Agile Manifesto
  • The Agile Manifesto, originally for software development, encapsulates a philosophy that underpins agile business analysis in any context. Key values that guide this philosophy are:
    • Individuals and interactions over processes and tools. In business analysis, this means working closely with stakeholders at every step, making people central to the work, as business analysis is a human-centric activity.
    • Working solutions over comprehensive documentation. Agile business analysis prioritises producing tangible results, gathering immediate feedback, and building shared understanding through conversations, with documentation serving to facilitate and support discussions.
    • Customer collaboration over contract negotiation. The focus is on continuously understanding and satisfying needs through ongoing collaboration with stakeholders and showing increments of solutions to elicit feedback.
    • Responding to change over following a plan. While agile approaches do plan (e.g., using a product roadmap), success is measured by how well solutions satisfy customer needs and deliver value. Continuous learning and feedback allow practitioners to refine understanding and adapt the solution rapidly.
• Principles of Agile Business Analysis
  • The Agile Extension defines seven principles that specifically guide agile business analysis practitioners:
    • See the Whole: Guides practitioners to analyse needs within the broader business context, focusing on why a change is necessary and how the solution delivers value to stakeholders.
    • Think as a Customer: Ensures solutions incorporate the customer’s voice and expected user experience, progressively detailing needs and continuously validating learning through feedback loops.
    • Analyze to Determine What is Valuable: Involves continuously assessing and prioritising work to maximise delivered value, avoiding waste by focusing on essential outcomes.
    • Get Real Using Examples: Builds shared understanding of needs and solutions through concrete, iterative examples, which can also be used to derive acceptance criteria and foundation for testing.
    • Understand What is Doable: Guides practitioners to understand how to deliver solutions within constraints (e.g., technology, team skills, time), continually analysing needs and solutions against these realities.
    • Stimulate Collaboration and Continuous Improvement: Fosters an environment where all stakeholders contribute value and processes are continuously improved through structured and unstructured feedback and retrospectives.
    • Avoid Waste: Identifies and eliminates activities that do not add value, such as producing unnecessary documentation or committing to work items that do not contribute to satisfying the need.
• Analysis at Multiple Horizons
  • The Agile Extension introduces a multi-level, rolling planning model using three horizons: Strategy, Initiative, and Delivery. This framework provides context and scope for planning and managing business analysis work.
    • Strategy Horizon: Focuses on decisions impacting the entire organisation, such as business goals, resource allocation, and identifying new initiatives. Analysis here has a broad scope, looking at customer expectations, external environment changes, internal organisational shifts, and learning from front-line initiatives.
    • Initiative Horizon: Concerned with defining and delivering a solution for a particular goal or initiative, including identifying solution options, features, and priorities. Decisions align with the Strategy Horizon and are informed by feedback from both Strategy and Delivery Horizons.
    • Delivery Horizon: Where the actual work happens, with implementation teams building discrete pieces of the product using iterative and incremental techniques from a prioritised list. Focuses on elaborating user stories, maintaining the backlog, and ensuring continuous learning and feedback in the immediate delivery cycles.
  • Continuous communication and collaboration across all horizons are essential for rapid feedback and effective decision-making.
• Planning Approaches in Agile
  • Agile business analysis primarily uses iterative and adaptive planning.
    • Iterative planning prioritises and refines work in short cycles to provide focus and increase feedback and learning from stakeholders.
    • Adaptive planning involves continuous change to long-term plans, with constant planning and analysis to prioritise and refine work for the highest value. This approach thrives on fast feedback and learning, allowing organisations to “sense and respond” to new information while maintaining long-term goals.
  • This contrasts with predictive planning, which involves detailed upfront analysis for the entire project duration, seeing deviations as risks and often suppressing feedback to maintain the original plan.
• Techniques in Agile Business Analysis
  • The Agile Extension also describes various techniques and concepts commonly used in agile approaches, such as Backlog Refinement, Behaviour Driven Development, Impact Mapping, Minimal Viable Product, Personas, Planning Workshops, Product Roadmaps, Real Options, Relative Estimation, Retrospectives, Reviews, Story Mapping, User Stories, Value Modelling, and Visioning. These techniques support specific activities at different horizons, from understanding customer needs to managing workflow and continuously improving processes.