...
Idea with a product flavor comes to our attention [ANYONE]
Create a draft PRD based on the Confluence PRD template. [TPM]
Invite to the first review meeting [TPM, QA, Architects, BD and PM]
Review the objective.
Review the background.
Review existing user stories
Remote, add and modify
Identify and create requirements
Create Jira tickets for requirements [PM]
Make milestone roadmap [TPM]
Make engineering roadmap [PM]
Implementation [TLs, Engineers, TLs, others]
FAQ
Q: Should everything we do in Linaro use the PRD Process?
A: No, it should be used when it’s product related or whenever we believe it brings value to us.Q: No one has informed me of this, how can I get more information?
A: Reach out to <tpm@linaro.org> and we’ll give a walk-through.Q: Who is responsible for the PRD documents?
A: The TPM team is the owner and responsible that it gets the attention needed. The TPM team will invite people from other teams to review, contribute and give feedback.Q: Is it a document created once and then closed when everything has been completed?
A: No, it’s meant to be a living document that is continuously updated (relates to “3”).Q: The way we approach PRD seems to be a bit different to how other companies do PRD work?
A: Correct, Linaro is different to many other companies. We’re often bound to commitments by our members, hence we’ll have to tweak the PRD process to fit our needs.Q: Who can read the PRDs?
A: Right now, they’re only accessible to Linaro employees, i.e., not accessible to members, assignees etc. Perhaps this will change in the future.Q: I have an idea and I want to try use the PRD process for it, what should I do?
A: Reach out to <tpm@linaro.org> and we will guide you.Q: What is the cadence for PRD reviews?
A: Ad-hoc as needed.