1. Teamwork and communication
1.1. Communication across the team is not good enough in the beginning
1.1.1. why?
1.1.1.1. Team collaboration
1.1.1.1.1. How?
1.2. We have some conflict across the team (S/W, Data, ITops and Product)
1.2.1. why?
1.2.1.1. Role and responsibility is a bit unclear
1.2.1.1.1. How?
2. Resource
2.1. Qualification is not matched company expectation
2.1.1. Why?
2.1.1.1. Timezone
2.1.1.2. Language barrier
2.1.1.2.1. How?
2.1.1.3. Performance/Skilled resource
2.1.1.3.1. How?
2.2. Investment is not enough
2.2.1. Why?
2.2.1.1. Contractor doesn't suit long term work
2.2.1.1.1. How?
3. Development environment
3.1. Infrastructure Dev/UAT/Demo/QC
3.1.1. why?
3.1.1.1. Maintance and support more than one environment
3.1.1.1.1. What's impact?
3.1.1.2. Many team are working on the same repo, same time
3.1.1.2.1. What's impact?
3.2. Source code Branch strategy
3.2.1. why?
3.2.1.1. Code release into production is not correct (missing or include not finish code,...)
3.2.1.1.1. what's will impact?
3.3. Devops
3.3.1. why?
3.3.1.1. we don't have enough people, who has skill/experience to support setup good infrastructure.
3.3.1.1.1. what's will impact?
4. Product development strategy
4.1. Product vision not clear
4.1.1. why is not clear?
4.1.1.1. We just clone function by function from legacy into 2.0 (reverse engineering)
4.1.1.1.1. What's happened?
4.1.1.2. We don't have exactly what's need to be done as high level and no one 100% focusing on that (low priority), just focus on business need (unplan work)
4.1.1.2.1. What's impact?
4.1.1.3. Has plan, but noone help to drive and support from all stakeholder.
4.1.1.3.1. Why?
4.2. Priority of work is keep changing
4.2.1. what's will impact ?
4.2.1.1. Impact to timeline - delivery
4.2.1.1.1. why?
4.2.1.2. Product quality
4.2.1.2.1. why?
4.2.2. Peoples
4.2.2.1. how?
4.2.2.1.1. Demotivate
4.2.2.1.2. Productivity down
4.3. Peoples
4.3.1. why?
4.3.1.1. Less experience about Product development
4.3.1.1.1. Planing and execution is not good
4.3.1.1.2. Communication between Product and Engineering gap
5. Product knowledge
5.1. why?
5.1.1. No documentation
5.1.1.1. why?
5.1.1.1.1. No one in charge of this, just follow up what's need to do, rather than take time to review and update the document if any importance point
5.1.2. Transfer knowledge is not good
5.1.2.1. why?
5.1.2.1.1. Engineering handover product from outsourcing team without business knowledge - just review the function, read code
5.1.2.1.2. Not sure how it go with Product team about business knowledge transfer