How do you keep learning in SDLC?

A good way to begin is to understand the types and methodologies of SDLC. Two common approaches are Waterfall and Agile. There are hosts of methodologies within each.

Reading and learning the theory behind the multiple SDLC frameworks available is a fantastic place to start, setting you up for success with the right tools and guidelines that can be leveraged when needed. I believe that this should be seen as a first step in one's journey throughout the software projects execution lifecycle, and a good next step could be applying/validating this knowledge in real life scenarios. One example could be taking active/passive shadowing opportunities.

To ensure continuous learning in SDLC: Stay curious and embrace challenges. Enroll in courses, workshops, and training. Read blogs, articles, and whitepapers. Join tech communities and forums. Attend conferences and meetups. Collaborate with peers on projects. Seek mentorship and feedback. Experiment with new tools and frameworks. Pursue relevant certifications. Stay updated with industry news. Document lessons and experiences. Learn from mistakes and failures. Solicit user and colleague feedback. Apply agile principles to learning. Listen to podcasts and attend webinars. Contribute to open-source projects. Reflect on your learning journey regularly. Embrace a growth mindset for continuous improvement.

First knowing the objective of why you want to learn about SDLC, will help a lot on deciding what and where to learn. It depends on the purpose like interview or other SDLC practically differs in every scenario. Reading user experiences from various online websites like DZone, Medium, YouTube videos will help. Recently ChatGPT also offers very good ideas. Nowadays there are tools like Jira, TFS and others to help organize SDLC practices. Subscribing to newsletters, blogs, twitter(X) groups and podcasts will help to keep yourself updated.

Staying up-to-date with SDLC means learning relevant courses at regular intervals. Courses can be at beginner, intermediate, or advanced levels. One can choose depending on the level they prefer to start with. I personally would recommend LinkedIn Learning courses, as they garner courses and certifications for all levels and come with certificates that are automatically added to your LinkedIn profile. Learning about leading project management tools that are already on the market can be of great help as well. One should consider courses that benefit their career objectives.

Though I don’t like, some do by taking certifications like Certified ScrumMaster (CSM) or Project Management Professional (PMP) certifications. It's a great way to prove your knowledge.

I always believe in the power of first hand experience. Immersing and involving yourself to different frameworks, methodology, mindset or many other ways of working will give you that learning experience and allowing yourself to fail fast so you evolve and learn from those mistakes so that you can continue to improve and shape the best fit-to-purpose processes within your project(s). There is always will be nuances for every project that might not be applicable to another.

This one is key, somehow related to the other comments about learning by real world experience. Surrounding yourself with more experienced colleagues that can coach you in the right direction but also challenge you and give you the space to grow is a great way to learn and validate your knowledge and approaches. Forcing ourselves out of our comfort zone, with positive energy, open to learn and receive constructive feedback is a fantastic way to grow and get experience in a SDLC scenario.

True. Keep learning as new technologies evolve so new ways of adapting and keeping up with these changes emerge too. Staying relevant and in the know has never been so important in this very innovative era. Read articles, learn from your leaders, network are some of the many other ways to learn aside from formal and virtual trainings.

Learn from the wisdom and mistakes of others by researching both successful and failed projects. Government sponsored software development such as the history of the IETF can be an excellent place to start.