The Agile/Adaptive Analyst

This course is designed to enable traditional business analysts to gain self-confidence in their ability to perform analysis in an agile environment, thus allowing themselves to become 'agile' in the truest sense of the word. 

Agile Overview

Agile was a standalone word before it ever became known as a software methodology.  Agile implies agility, flexibility, the ability to be nimble....adaptive.  These very attributes are why it was chosen as a methodology.

Definitions of Agile

Definitions of Agile

When we talk about the first term, let’s substitute ‘Ruth is an agile analyst’.  What does that statement imply?

  • Agile is a standalone adjective.
  • Describing someone or something as agile implies agility: the ability to be nimble, flexible, quick-footed…, and adaptable.
  • Chosen specifically for its attributes to describe a software development method.

Manifesto for Agile Software Development

Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping others do it.

Through this work we have come to value:

Individuals and interactions  over     processes and tools
Working software                       over    comprehensive documentation
Customer collaboration          over     contract negotiation
Responding to change             over     following a plan

Agile Manifesto Explained

Individuals & Interactions vs Tools & Processes

Agile believes that emphasis should be placed on the main actors (people who undertake, participate and implement) belonging to a project and their interactions with one another – not with tools and processes.

Working software vs Comprehensive Documentation

Agile teams focus on collecting and recording viable descriptions of deliverables that focus on quality and quantity of the value to be delivered to the customer throughout the product lifecycle.

Customer Collaboration vs Contract Negotiations

Agile relies on the concept of shared value where the customers are considered collaborators working with the team to develop the product. In contract based situations customers typically appear at the beginning and end of a project.

Agile Manifesto Explained

Responding to Change vs Following a Plan

Agile embraces change by enabling incorporation of fast product lifecycles rather than following formal plans that could potentially contain outdated data.

12 Agile Principles

  1. Customer satisfaction. 
  2. Welcome changing requirements, even late in development. 
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 
  4. Shared value approach means that the business and developers must work together throughout the project. 
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 
  6. Face-to-face conversation and communications are preferred.

7.   Working software is the primary measure of progress = value. 

8.   Maintain a constant pace indefinitely to improve quality. 

9.   Continuous attention to technical excellence and good design enhances agility. 

10.  Simplicity--the art of maximizing the amount of work not done--is essential. 

11.  The best architectures, requirements, and designs emerge from self-organizing teams. 

12.  At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Agile Methods Framework: Scrum

Scrum 

  • Agile software development with Scrum is often perceived as a methodology but is actually a framework for managing a process/project 
  • Scrum is an agile way to manage a software project
  • Adaptive, iterative, fast, flexible and effective
  • Ensures transparency in communication 
  • Creates an environment of collective accountability, progress and trust
  • Supports all kinds of projects from products to services in all types of industries regardless of complexity

Scrum Advantages


  • Adaptability 
  • Customer-centric 
  • Continuous delivery 
  • Continuous feedback 
  • Transparency 
  • Continuous improvement 
  • Sustainable pace


  • Effective development process
  • Motivational
  • Faster problem resolution
  • Effective deliverables
  • Collective ownership
  • High velocity
  • Innovative environment

Agile has more than one definition

  • Agile is a software development methodology only.

Agile Manifesto - individual and interactions - fill in the blanks question

The agile manifesto states that we value individuals and interactions over 

Agile Manifesto - working software - fill in the blanks question

The Agile Manifesto states that we value working software over