Vietnamese version translated from this famous slide
http://www.slideshare.net/nbykmatsui/ss-55961899?utm_content=buffer50ae1&utm_medium=social&utm_source=facebook.com&utm_campaign=buffer
Vietnamese version translated from this famous slide
http://www.slideshare.net/nbykmatsui/ss-55961899?utm_content=buffer50ae1&utm_medium=social&utm_source=facebook.com&utm_campaign=buffer
Reflective learning involves reflecting on experiences to improve learning outcomes. It requires reflecting on what was learned, what gaps in knowledge remain, and how to apply lessons to new situations. Various models provide frameworks for structured reflection, including identifying key events, responding emotionally and intellectually, relating content to prior knowledge, reasoning about broader implications, and reconstructing understanding. Regular reflection improves metacognition, motivation, and learning.
Education - in conjunction with many other fields - requires Agility, especially in a changing world with a high demand of adjustment and adaptation. Students are not the same as 1990¡¯s, markets are moving, organizations are changing, technologies are raising, and the classrooms also need reformation. The Industry Revolution 4.0 has emerging, educators are talking about Education 4.0. What can we do to not stay behind? This topic discusses about Agility, Industry 4.0, Education 4.0, Digital learning with reflections on a modern IT training solution.
6. Design is the key,
Planned Design is not ¡
? Takeuchi & Nonaka: overlapping is better than sequential
Not efficient:
? Time consuming
? No backward
? No ¡°better idea¡± on the go
L¨¤m th? n¨¤o ?? t? ch?c ki?u ¡°Overlapping¡± nh? th? n¨¤y?
13. Development Flow
Requirement
Analysis
UI Mocking
?Customer
discussion
Design Draft
?Design
Discussion
Code the
skeleton to
test the
design
Coding in
team
Refactoring
and
Refinement
Build the
increment
$
DevTeamPO
Collaboration:
Steps:
Artifacts:
As a super user,
I want to ¡
A
B
IDo
Interface IDo{
//TODO ¡
}
Class A{
//TODO ¡
}
Class B:IDo{
//TODO ¡
}
Interface IDo{
//TODO ¡
}
Class A{
method1(){
//Mr. A codes here
}
}
Class B:IDo{
method1(){
//Mrs. B codes here
}
}
Class C{
}
$
PO