Q: Resource allocation -> have changed to per mission, is it still relevan for engineering leads to participate ? It is ok for backend, but how about frontend & apps
A: Actually everyone will participate quarter meeting to define roadmap (and resource allocation) and reprioritization meeting. so everyone will be able to define his own "timeline". Mission engineer lead (most likely will be backend engineer) only act as mediator between the team and other stakeholders (PM, UX, Marketing, etc). Clear responsibility and expectation scope will be communicated separately by Deri.
Q: What's the difference between IxD and UX ?
A: Basically UX (Product Design) consists of IxD (interaction designer, responsible for designing program flow), UI Designer (responsible for designing interface), and Content (responsible to write the content). Feature design will be represented by IxD (will be UX contact person) and IxD will communicate with UI Designer and Content writer.
Q: What is product engineer lead ?
A: Mission engineer lead (most likely will be backend engineer) only act as mediator between the team and other stakeholders (PM, UX, Marketing, etc). Clear responsibility and expectation scope will be communicated separately by Deri.
Q: What is the job of PM ? -> PM is bussiness or product manager ? Why PM negotiate with other PM ?
A: PM will define product requirement, and as a feature owner PM will ensure that there are resource available to own the feature execution and there is slot to develop it. He will not define when a feature will be released, but he will discuss with IxD, backend engineer, frontend engineer, and mobile engineer to define timeline and scope (which are still negotiable). PM will negotiate with other PM if any change of scope will cause next feature
Q: Why cancel release if major bug found ? What is the definition of major bug ? (please consult with QA)
A: More like pending release actually. This is very unlikely to be happened. Backend example: pending release internationalization
Q: When feature lock be done ? (1 week before ? 3 days before ?)
A: 2 days before RC release. Only lock feature on release branch (bug fix only), develop branch can still be used
Q: Please explain release cycle timing
A: gantt chart created https://docs.google.com/spreadsheets/d/1F7o7j-GXDInmpySLMK4fYPCL2Uf_v-Djlzm_M1zPw1M/edit#gid=340941016
Q: Now there is usually time when the mobile release and should wait for the backend release ? What should be the ideal situation ? Should backend finished some weeks before mobile release ? What will happen if backend release delayed, should mobile release delayed ?
A: Ideally backend will be released first. Delaying mobile release because of delayed backend release will be decided through discussion between PM and mobile engineer.
Q: why the git management like that ? Feature should not be merged with master
A: sorry :( will be reviewed later
Q: there should be what planned, what achieved, and reason why its not achieved in post release
A: will be done during release meeting every 4W
Q: when is the time allocated to fix bug ? Assume no bug at all ?
A: bug fix will be done during 2D of sanity and regression test (if any bug found). if no bug, release as planned. if any bug found that cannot be solved in 2d, release delay/pending decision will be owned by release manager (after discussion with all related stakeholder)
Q: Resource allocation -> have changed to per mission, is it still relevan for engineering leads to participate ? It is ok for backend, but how about frontend & apps
A: Actually everyone will participate quarter meeting to define roadmap (and resource allocation) and reprioritization meeting. so everyone will be able to define his own "timeline". Mission engineer lead (most likely will be backend engineer) only act as mediator between the team and other stakeholders (PM, UX, Marketing, etc). Clear responsibility and expectation scope will be communicated separately by Deri.
Q: What's the difference between IxD and UX ?
A: Basically UX (Product Design) consists of IxD (interaction designer, responsible for designing program flow), UI Designer (responsible for designing interface), and Content (responsible to write the content). Feature design will be represented by IxD (will be UX contact person) and IxD will communicate with UI Designer and Content writer.
Q: What is product engineer lead ?
A: Mission engineer lead (most likely will be backend engineer) only act as mediator between the team and other stakeholders (PM, UX, Marketing, etc). Clear responsibility and expectation scope will be communicated separately by Deri.
Q: What is the job of PM ? -> PM is bussiness or product manager ? Why PM negotiate with other PM ?
A: PM will define product requirement, and as a feature owner PM will ensure that there are resource available to own the feature execution and there is slot to develop it. He will not define when a feature will be released, but he will discuss with IxD, backend engineer, frontend engineer, and mobile engineer to define timeline and scope (which are still negotiable). PM will negotiate with other PM if any change of scope will cause next feature
Q: Why cancel release if major bug found ? What is the definition of major bug ? (please consult with QA)
A: More like pending release actually. This is very unlikely to be happened. Backend example: pending release internationalization
Q: When feature lock be done ? (1 week before ? 3 days before ?)
A: 2 days before RC release. Only lock feature on release branch (bug fix only), develop branch can still be used
Q: Please explain release cycle timing
A: gantt chart created https://docs.google.com/spreadsheets/d/1F7o7j-GXDInmpySLMK4fYPCL2Uf_v-Djlzm_M1zPw1M/edit#gid=340941016
Q: Now there is usually time when the mobile release and should wait for the backend release ? What should be the ideal situation ? Should backend finished some weeks before mobile release ? What will happen if backend release delayed, should mobile release delayed ?
A: Ideally backend will be released first. Delaying mobile release because of delayed backend release will be decided through discussion between PM and mobile engineer.
Q: why the git management like that ? Feature should not be merged with master
A: sorry :( will be reviewed later
Q: there should be what planned, what achieved, and reason why its not achieved in post release
A: will be done during release meeting every 4W
Q: when is the time allocated to fix bug ? Assume no bug at all ?
A: bug fix will be done during 2D of sanity and regression test (if any bug found). if no bug, release as planned. if any bug found that cannot be solved in 2d, release delay/pending decision will be owned by release manager (after discussion with all related stakeholder)