What makes most sense to me is the following ( straw-man ):
- Products will generate and post for review user stories for a particular feature. The main utility here is that we consider user expectations divorced from the implementation. User stories should not come from PMs only but PMs will manage them and make sure they're in sync with reality.
- Developers should be able to express (in writing?) how they are going to proceed with implementing a feature, before they start. With the SDK this is a JEP, and we talked about asking Irakli to present at the work week on how JEPs fit in the Jetpack process, what they buy us in exchange for the time spent writing, posting, discussing and revising them.
Once we've got the problem statement ( a PRD of user stories ) and an implementation plan that solves the problem, all of the actual work will be tracked in Bugzilla: