What's new

Magalingbsa ENGLISH jan. Pa help naman po.

PHC - NoName

Eternal Poster
Joined
Sep 27, 2021
Posts
439
Reaction
78
Points
269
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
 
2. When we fail, we can't be satisfied like that. We need to get back on our feet immediately. Innovation must be continuous so that corrections can be made quickly. We need to have an end-to-end vision and stick with it.
 
8. Instead of sticking with traditional tools, we should also be open to the idea of utilizing modern development tools that can facilitate the development of our projects. Sure, the traditional way can still be applicable but maybe our work will be easier in the modern way. We must also consider that
 
4. It is undoubtedly that there are many features that consumers would like but they cannot be produced and released in one go, so it's much better if we prioritize what we think is the most important feature
 
7. It's human nature to make mistakes; errors cannot be avoided. But it is not to say we won't take care of it. What we should do is keep an eye out for such errors and fix them as soon as possible. It is effective to establish a vulnerability disclosure and bug bounty program in order to encourage häçkers in assessing the codes.
 
3. We must not jeopardize the quality of our work. It's OK to release them in stages according to the iterative model rather than releasing them all at once, which would reduce quality.
 
1. In terms of technology implementation, we should place a greater emphasis on value creation rather than simply the expense of technology.
 
5. Your project scope should be clear. If it's not, impact on business value might be overlooked. The process of delivering quality software would be easier if you know how to manage your project scope
 
6. Always check what methodology is the most relevant and what infrastructure is the most applicable in your project. Always consider those things because there's no such as "one size fits all"
 
3. Quality must never be compromised. It is acceptable to release one by one in accordance with the iterative model rather than one by one after quality has been compromised.
 

Similar threads

Back
Top