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. 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.
Developer / Member
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.
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. It is like a team lead for an iteration.
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.