What is Agile?

Agile is a new approach to run projects.

E.g. Software, Products, Marketing Campaigns, Services, etc

It is a way to create complex things collaboratively.

The primary focus is always around People.

Instead of being focussed on process, plan, or documentation, the emphasis is on collaboration between teams, customers, stakeholders, and users.

Projects don’t produce products. People do!

Where did Agile come from?

Agile can be considered as a reaction to waterfall methodologies.

It was a reaction against focussing on Requirements Plan & Specification to the exclusion of all else.

It was a reaction against what the Contract or Statement of Work said instead of working with customers and delivering what they needed.

It was the reaction against the Rigidity of Waterfall (Stability) instead of being comfortable with change i.e being flexible.

The aforementioned conflicting points (bolded phrases) are not bad. However, they should not be the point of focus. So, what should be the point of focus?

About 20 software development visionaries got together and came up with the Agile Manifesto.

The manifesto is short and consists of 4 values and 12 principles.

Agile Values:

Individuals and interactions over process and tools. 

In this, we stress that people are more important than any process or tool.

Working software over comprehensive documentation.

In this, we stress that the product is more important than the documentation about the product.

As BAs, our work is modified in the agile environment. We must focus on product and people to drive the requirements through conversation than to just act as a scribe to note requirements. Documentation is heavily reduced, however, interaction is proportionately increased i.e BAs can now be more proactive with requirement gathering and they can effectively communicate the product vision to all.

Customer collaboration over contract negotiation.

Contacts are important as they make the business work. However, the focus should be on collaborating with customers to deliver what they need instead of arguing on line items and SOWs.

Responding to change over following a plan.

Businesses have become very dynamic and change can happen literally overnight. Hence, sticking to a concrete plan may not be the best option in the given environment and so the focus should be on being flexible and open to change.

Agile Principles

( we cover the ones that are more relevant to us as BAs. Rest of the principles.)

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

We will regularly deliver valuable products to our customers to keep them happy.

Welcome changing requirements, even late in development. Agile processes harness change to the customer’s competitive advantage. 

We welcome change instead of avoiding it.

Business people and developers must work together daily throughout the project.

Unlike in the waterfall method where there is a gap between business people and developers during the development phase, in Agile, business people are always involved in the project.

Agile processes promote sustainable development.The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

In Agile since we work in iterations there is room to breathe. Once we are done with an iteration we can start with a new one. This way we can work moreover longer periods. This is a healthy way to work compared to working for hours over weeks or months continuously to deliver a product.

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

We want to produce results and not just spend time working. Hence, the more busy work we can remove the more efficient and effective we can be.

Why use Agile?

To better align yourself with customers and make sure you are creating the best possible product that fits their needs.

To have flexibility to be able to handle requirements that change as the market changes.

To cut down on the non-value-added work and focus on work that produces real value to customers.

When should you use Agile?

Mike Cohn suggests to use Agile on projects that are complex and urgent enough i.e not to use it on projects that are very simple and non-urgent.

One of the agile methodologies the DSDM has a multi-question suitability filter based on the attributes of team, organization, and project to suggest if agile should be applicable to a project.

Important Points:

Agile is all about people. Where waterfall methods tend to focus on big plans, specifications, and designs, Agile focuses on the team members running the project and helping them to work together effectively and flexibly.

Agile does indeed have plans, and planning is valuable. It just isn’t as valued as responding to change.

Change happens quickly, so it is preferred to come up with lightweight, adaptive plans.

The Agile Principles often refer to “working” software, and the aim is to have our products be of high quality, but no product is ever “perfect,” and Agile doesn’t aspire to perfection.