Project Management: Beyond Gantt Charts

As a developer, I always thought project management was something "managers" did while I wrote code. This course made me understand that we're all project managers, especially when working in teams.

What impacted me most:

The difference between predictive methodologies (Waterfall) and agile ones (Scrum, Kanban). In the real world of software, requirements change constantly. Scrum taught me that it's better to deliver value incrementally and adapt to change than to plan everything upfront and discover it's no longer relevant.

A case we studied:

We analyzed the case of a government project that failed due to over-planning. They had been planning for 2 years, and when they finally started developing, the market had already changed. It's a perfect example of why agility matters.

How it changed my way of working:

Before this course, I was the typical developer who said "I just code." I now understand the importance of daily stand-ups, retrospectives, and constant communication with stakeholders. I started using Trello and then Jira to organize my personal tasks, and productivity improved significantly.

What I took for my career:

The Scrum Master role really interested me. It's not about telling people what to do, but about facilitating and removing obstacles. It's a leadership style that resonates with me and that I want to develop further.