Thread by @aleixmorgadas

1/ When you start doing project development, you find yourself with tight deadlines, a lot of tradeoffs in quality, and money spend.

You start feeling that you might be doing something wrongly. You feel that you're not delivering business value

Thread 🧵

2/ You learn about Agile, and why deliver working software as soon as possible. You adopt Scrum, but with a project mindset. So, it's a fake Scrum. It's more like a 2 weeks waterfall.

Yet you adopt a very important ceremony important, the Retrospective.

3/ Based on Retrospectives, you start questioning yourself how are you working. Why can we deliver value to the customer? Why aren't we customer-focused?

You start looking for alternatives.

PRODUCT! PRODUCT-MINDSET!

Just burn the Project Management! 🔥

4/ Product approach is the best. Everything makes sense now!

Customer-Centric. Agile. Empowered Teams.

We're Product Teams! No longer doing projects.

5/ After some time doing Product you start experimenting that you are not able to accomplish some things because they aren't strictly related to Product

6/

- How are we gonna improve our Deployment Infrastructure?
- How are we gonna approach this shared effort among several teams that require shared effort?
- How are we gonna <thing non-strictly related to product delivery>?

7/At this moment you realize the importance of _Project_ Management.

Project Management helps those things that have a Start and an End, instead of being continuously evolving for an End Client.

8/ I reflected about when to apply _Project_ and when _Product_, and how they co-live on all the Development Life-Cycle.

As Engineer, you need to have a good product understanding, but having project skills is way more relevant than I thought.

9/ We reached a moment that we all are learning about how to do _Product_ but assuming that we all already masters _Project_. Far from reality

We still need to learn a lot of Management approaches and how they help in different ways to impact our customers