yuu

Design Thinking could have really helped to understand the problem customers were facing (They were looking to to study new concepts, but moreover discuss ideas with their peers in class so interactive group learning).

Lean Startup would have helped to avoid the problem of building something people were not looking for (training without Powerpoint),

and Agile could have helped to cut the dev cycle with 50% by just building iteratively.

Gartner introduced a model in 2016 where they connected these three models.

Gartner: Combine Design Thinking, Lean Startup and Agile to Drive Digital Innovation

More information:

• https://www.productpizza.com/combining-design-thinking-with-lean-startup-and-agile/
• https://www.gartner.com/en/documents/3941917 (2019)
• https://www.gartner.com/en/documents/3200917 (2016)

Expand your horizons by trying out 12 different programming languages in 2023.

Go old-school with COBOL, cutting edge with Unison or esoteric with Prolog. Explore low-level code with Assembly, expressions with a Lisp or functional with Haskell!

More information:

• https://exercism.org/challenges/12in23
• https://forum.exercism.org/t/the-12in23-challenge/2213

Stakeholders’ buy-in and support is an integral component of success for any UX project, as they translate into resources, bandwidth, and approval. However, navigating stakeholder dynamics requires a thoughtful mix of listening, collaboration, communication, influence, and negotiation. This balancing act leads to stakeholder engagement and ultimately creates successful, long-term relationships.

Continuous communication with stakeholders is important for any UX project — first, because it helps them understand and appreciate what UX does and, second, because it helps UX learn about other essential aspects of the business. Despite this duality, the burden of communication usually falls on UX — because stakeholders are inherently busy and possibly focused on many other things besides UX.

DevSecOps is an engineering practice that promotes collaboration among development, security, and operations. When implemented, it creates a socio-technical system that uses automation for flexible, rapid, frequent delivery of secure infrastructure and software to production. Software development organizations must tailor each DevSecOps pipeline to the people, processes, and technology needed to provide a product or service. Until recently, there was no consistent basis for managing software-intensive development, cybersecurity, and operations in distributed systems.

Then in May, the SEI released version 1.0 of the DevSecOps PIM, a reusable reference architecture for DevSecOps pipelines. Software development organizations can use the online, interactive PIM as a reference architecture or assessment tool for their own DevSecOps pipelines.

More information:

• https://cmu-sei.github.io/DevSecOps-Model/
• https://insights.sei.cmu.edu/news/devsecops-platform-independent-model-receives-major-update/