FAST Process‎ > ‎


Product Director

The word director is used as in the director of a film as this is a good analogy of what the role entails. This role is somewhat similar to the Product Owner role in Scrum. Your responsibility as Product Director (PD) is to communicate and maintain : -
  • a product vision
  • a product road map (rough set of releases with key features and timeline)
  • a release plan (set of features)
  • a story map with the set of features for the release
The FAST Product Director is a key leadership role to making the whole process work. Developers will want to follow their vision and build their product. The FAST Product Director should be able to "rouse the troops", so to speak, at each iteration boundary.


These are people that are invested in the outcome of the product and have an interest in the feature set being delivered.

Developer (Dev)

The development tribe is made up of cross functional skills and T-shaped people. Your role name is "Developer" regardless of what your primary skill is. (This is the same as Scrum.) You are expected and encouraged to be excellent in your craft. If you are writing code, you are expected to be a Code Crafter and quality code is expected. You are also expected to be a coach and be coach-able. No holding on to knowledge or trying to creating silos. You should always be working on both aspects of your T-shape - generality and specialty.

Tribe Resource

If there is a skill that is needed in the tribe, and the person providing this skill is not interested or able to be on the tribe exclusively, that person is a Tribe Resource. An example might be a DBA. They have a very specialized skill and their day to work is sometimes directly adding support/effort to stories and sometimes supporting wider initiatives. Another example is a specialist that you bring in for a short period of time to help you solve a certain problem. If you are not 100% dedicated to working in the tribe on delivering the current release, your role title is a Tribe Resource.

As a Tribe Resource you might get pulled in by developers that need your help to complete their work and/or you can be proactive by attending the FAST meeting to see how you can help and maybe even be a story steward on occasion if you see it beneficial to the release.

Swarm Steward

There are no team leads or architect roles in FAST. (This is similar to Extreme Programming.) If you choose to stand up at the FAST meeting and suggest work for the Iteration Marketplace, your role for the period of that iteration is Swarm Steward.

Feature Steward

To ensure continued ownership of a feature until completion, and nothing falling through the gaps, a Feature Steward is one who agrees to stay with the feature across iterations. (They may hand the baton on to another if mutually agreeable.)

Next, read about the facilities requirements to made FAST work.