Being in R&D company always occupied my brain to thinking what will be in the future, with simplicity result and complexity ways to absorb overall requirement; necessary design thinking for software architecture is a must, well - I just want to share a bit about that...
Another common point of confusion is the distinction between design thinking and Agile methods of software development. The primary difference is that Agile offers a specific set of prescriptive processes while design thinking encapsulates a set of guidelines and general principles. Although not the same, the two approaches are highly complementary (even on the same project), because both recognize the benefits of using iterative work cycles to pursue customer-centric goals. Always remember that real people work on every project. The best methodologies are inherently people-centric and help participants anticipate likely causes of failure. Visualizing failure early in a project is an excellent means to prevent it from occurring. We’re all human and may make mistakes but certainly no one wants to fail. Finally, design thinking can make potential failure a learning tool and not a final outcome.
Next Question: in reality?
No comments:
Post a Comment