PHC - NoName
Honorary Poster
- Joined
- Sep 27, 2021
- Posts
- 439
- Reaction
- 78
- Points
- 229
Pa english naman po nitong 2 to 8. Salamat po.
1. In terms of technology implementation, we should focus more on value creation as well hindi lang pwedeng yung cost lang ng technology titingnan natin.
2. When we fail, hindi pwedeng kuntento na tayo na gano'n. We need to get back on our feet agad. Dapat continuous ang innovation para mabilis din ang pagsagawa ng corrections. We need to have an end-to-end vision and stick with it.
3. Hindi dapat kino-compromise yung quality. Okay lang na paisa-isa ang pag-release according sa iterative model kesa isahan nga tapos na-compromise naman yung quality.
4. Paniguradong maraming features na gusto ang consumers pero s'yempre hindi naman kayang ma-release o produce lahat 'yon in one go so much better kung i-prioritize natin kung ano yung nakikita natin na pinakakailangan nilang features.
5. Dapat malinaw ang project scope sa inyo. Kasi kapag hindi malinaw, baka ma-overlook yung impact sa business value. Kung alam niyong i-manage yung project scope mas mapapadali ang process of delivering quality software.
6. Always check what methodology is most relevant and what infrastracture is most applicable sa project niyo. Kino-consider dapat yung mga bagay na 'yon kasi wala namang one size fits all.
7. Natural magkamali. Hindi naiiwasan ang errors. Hindi maaalis 'yan. Pero hindi ibig sabihin na hahayaan 'yon. What we should do is look out for those mistakes and correct them at once. Effective mag-establish ng vulnerability disclosure tsaka bug bounty program para mahikayat ang häçkers na i-assess ang codes.
8. Instead of sticking with traditional tools, dapat open din tayo sa idea of utilizing modern development tools na makakapagpadali ng development ng projects natin. Sure, pwedeng applicable pa rin yung traditional way pero baka naman mas mapadali yung gawain natin sa modern way. Dapat i-consider din natin 'yon
1. In terms of technology implementation, we should focus more on value creation as well hindi lang pwedeng yung cost lang ng technology titingnan natin.
2. When we fail, hindi pwedeng kuntento na tayo na gano'n. We need to get back on our feet agad. Dapat continuous ang innovation para mabilis din ang pagsagawa ng corrections. We need to have an end-to-end vision and stick with it.
3. Hindi dapat kino-compromise yung quality. Okay lang na paisa-isa ang pag-release according sa iterative model kesa isahan nga tapos na-compromise naman yung quality.
4. Paniguradong maraming features na gusto ang consumers pero s'yempre hindi naman kayang ma-release o produce lahat 'yon in one go so much better kung i-prioritize natin kung ano yung nakikita natin na pinakakailangan nilang features.
5. Dapat malinaw ang project scope sa inyo. Kasi kapag hindi malinaw, baka ma-overlook yung impact sa business value. Kung alam niyong i-manage yung project scope mas mapapadali ang process of delivering quality software.
6. Always check what methodology is most relevant and what infrastracture is most applicable sa project niyo. Kino-consider dapat yung mga bagay na 'yon kasi wala namang one size fits all.
7. Natural magkamali. Hindi naiiwasan ang errors. Hindi maaalis 'yan. Pero hindi ibig sabihin na hahayaan 'yon. What we should do is look out for those mistakes and correct them at once. Effective mag-establish ng vulnerability disclosure tsaka bug bounty program para mahikayat ang häçkers na i-assess ang codes.
8. Instead of sticking with traditional tools, dapat open din tayo sa idea of utilizing modern development tools na makakapagpadali ng development ng projects natin. Sure, pwedeng applicable pa rin yung traditional way pero baka naman mas mapadali yung gawain natin sa modern way. Dapat i-consider din natin 'yon