One project poster for each feature?

[Lars Böhnke]

Hey there! Just discovered the project poster and I think its awesome. Especially the problem space is definetely the thing we were missing a little bit whie we dove too fast into the solution space :)

But we have (yet) a small product and I wondered if you guys would create a project poster for each new feature? Then it would be more a feature poster. Does that make sense? :)

Also, du you then create a product requirements page (solution space) as a child page within the project poster?

Cheers, Lars

[Dominic Price]

Lars, thanks for the question. We've found our teams tend to start with the meta level Project Poster, with their high level vision, purpose and job to be done.

Project posters are most useful when:

• You are starting a project from the problem definition or envisioning phase
• The project spans multiple teams or more than a month in effort
• You are harvesting something from one use case to another (adopting a feature in different product, and therefore want to sense check value)

We havent prescribed at what level this should be done, but we suggest to our teams that a project poster should be used to build confidence, rather than justify something. They decide when they need them.

In our experience, our product teams then quickly dive into feature kick off, which is a collaborative exercise that also often occurs in Confluence so we can connect ideas from people all over the world.

https://www.atlassian.com/team-playbook/plays/feature-kick-off

Hope that helps. Let us know how you get on. We love hearing stories of how teams use this resource.

[Dominic Price]

Project Poster video

[Lars Böhnke]

@Dominic Price how does such a Feature Kick Off looks like in Confluence? The product requirements blueprint isn't really helpful when you are not desiging a feature from scratch or desigining multiple user stories at once. How das a single Confluence page dedicated to only one or two user stories looks like?