Over the years, I have learned a lot about quality, product development, and leading and managing projects. Making sure quality assurance works is my current job, but the most fun I have had was as project manager. Especially in large EU-financed projects, where you meet so many different angles and viewpoints on the problem. Even if they rarely lead to a practical solution, because frankly they are more for education of the participants. I know, because I have been an evaluator too. Project management aiming to test a Minimum Viable Product is even more interesting, because now we are talking both invention and innovation. There is someone who will see a value in what you do (otherwise you would not do it). But they may not know what they want. Managing requirements is so basic regardless of the type of project management you do, because you need to understand how to solve the requirements and bring value to the receiver. Agile connected with Lean is superior in this regard. Maximizing the perceived value by maximizing understanding of requirements is what has informed my work as solution architect as well (yes, I can drive requirements management as well as solution design - and verification and validation as well. Usually, I can sketch out an implementable solution too). Requirements do not only come from the users (or customers). There are architectural requirements, security requirements, and standards from any direction. I have some experience of standardization so I know how it works. Right now I am trying to improve my understanding of the security requirements, because they have become more and more important. Just like documentation, so someone can deploy your system without asking you. But now I have been talking all this time. Is there anything you want to say to me? Feel free to comment on my posts where I am trying to figure out how and what to do when you implement something that brings value to people.