FAST Process‎ > ‎


Product Director

The word director is used as in the director of a film as I feel this is a good analogy of what the role entails. This role is somewhat similar to the Product Owner role in Scrum. Your responsibility 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 physical story map with the set of features for the release
It is recommended that the FAST Project Manager be characterized as a charismatic leader. Developers will believe in them, their vision and their product. The FAST Project Manager should be able to "rouse the troops", so to speak, at each iteration boundary.

Because a FAST tribe could grow to a theoretical size of 150 developers (Dunbar's number), it is questioned whether one person could handle Product Ownership with so many teams, developers and fast pace of development. The short answer is - I don't have an answer. I look forward to hearing/reading about the experiments that have been tried in the field and their outcomes. I'm sure FAST Product Ownership will emerge being as different to other models of product ownership as FAST is to other agile methodologies.

Fortunately, we don't need to have this answer immediately nor to start a FAST tribe. I'm not sure if I would recommending starting a tribe at 150 developers or a smaller seed team and then grow them into a tribe. Please experiment and leave feedback on what you tried.


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 Craftsman and quality code is expected. You are expected to be a coach and be coachable. No holding on to knowledge or trying to create silos!


If there is a skill that is needed, and the person providing this skill is not interested or able to be on the tribe exclusively, that person is a Resource to the tribe. 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 is Resource.

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

(I know that the agile world is trying hard to get rid of this term applied to people. The main cause of this problem stems from viewing developers as fungible assets to a project. As FAST has already dealt with this issue in it's principals, values and prerequisites, I have no problem using the term as a role name. I feel the word resource is a good descriptor to distinguish between those that have 100% skin in the game and those that do not but are still important to the delivery outcome. I'm open to other suggestions though if this term is still considered with discomfort) 

Story 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 a story/action for the Iteration Marketplace, your role for the period of that iteration is Story Steward.

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