🔑Introduction to the Agile Handbook

Welcome to "Fail Fast" world. This is the Agile Handbook for Tech Fleet.

Video Version

Credit: Tech Fleet https://youtu.be/GMZRdXYCqzw

Get Ready for Your World To Change

In school you are taught to produce a perfect result. You do it in phases. You take your time. You deal with minor constraints. You may work without clients.

To "succeed" in industry environments you have to re-learn and un-learn the ways you have been trained in your education.

Agencies and in-house company teams in the industry operate in completely different ways:

1. Their processes are non-linear.

2. They do UX and development work in parallel.

3. They collaborate across different functions.

4. They don't gather all of the requirements up front.

5. They change plans as they work.

6. They operate in uncertainty.

7. They ship products iteratively.

Changing Your Mindset

You have to develop an Agile mindset to succeed in the industry.

When you learn Agile, your ways of working will change.

As a UX researcher, UX designer, product person, project management person, or developer, you will be expected to change the way you work.

Your mindset will shift in how you should be bringing yourself to teams.

Your perspective will grow and change over time.

Companies may expect employees to already have experience working in Agile. You will likely be asked to speak to your Agile philosophies when interviewing.

It's crucial to build your Agile mindset in UX, product, and development fields.

Tech Fleet can help. We are an Agile Coaching organization, and all of the community work embeds Agile in its day-to-day processes.

TL;DR: What's Agile? Why Should I Care?

Agile is a philosophy and a way of approaching UX work.

Agile teams deliver incremental value as they go.

They do not work in sequential order or phases. They deliver small chunks of usable, valuable functionality to users continuously instead of delivering the full result all at once.

This picture that shows the "incremental value" of Agile vs. the "all-at-once value" delivered in Waterfall:

Picture of a sequence of releases while building with Agile philosophies. Credit: https://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp

Waterfall teams (AKA the way you have probably been trained) build nothing but the car they agreed to in the beginning. They build the parts in sequential order. They put the entire car together before they deliver to users or clients. No one sees anything being built until it's launched. No one validates their direction while they are building.

Agile teams take the opposite approach. Instead of building a car in parts, Agile teams build usable things they can test along the way. They deliver value to users in chunks that increasingly solves more problems.

Incremental Value with Agile

Agile delivers value throughout a project, while Waterfall delivers value at the end of a project:

Waterfall processes deliver value all the way at the end of the project. Agile processes deliver value continuously, and incrementally. Credit: https://www.scrum.org/resources/blog/agile-principles-early-value-delivery

Agile, as such, is less risky than Waterfall. Agile teams verify their direction as they deliver value and change if they need to.

The Agile releases in the "Car" example solve incremental problems and bring incremental value:

1. A skateboard meets basic needs of transportation.

2. A scooter is more valuable than the skateboard because it offers more stability while traveling.

3. A bike is more valuable than the scooter because it lets you travel further and more efficiently.

4. A motorcycle is more valuable than the bike because it goes fast, travels far, and is safer.

5. A car is more valuable than the motorcycle because it is safer, fast, holds more travelers, and offers more cargo space.

If, and only if, the Agile team has validated that these results bring incremental value, they will start building towards the next release.

If they learned after delivering something that it doesn't deliver needs, they change their plans.

These are two very different ways of performing work.

Agile teams, because they deliver incremental value, deliver stronger results in the end.

This Handbook Teaches a Foundational Agile Mindset

Welcome to the "Fail Fast" life. This is the new and improved Agile Handbook for Tech Fleet.

This handbook offers introduction to the Agile ways of work. It covers:

1. Agile philosophies

2. Traits of strong Agile teams

3. Living daily Agile life

4. Deliverables for Agile team success

Tech Fleet is an Agile coaching organization and all teams are expected to operate in Agile ways of work.

All Tech Fleet members should read this handbook to prepare for the Agile mindset before they apply to project training.