A user story is a feature request (or need) expressed from the point of view of a user with a description of the value it provides to that user.
The Daily Scrum was meant for Developers to give each other an idea of the work they had done the day before and their plans for the day in progress. It was never meant for Product Managers or Product Owners to be part of them unless they are taking part of the work in the actual product by working on Sprint Backlog Items.
The final users are the most important part of the information system because if the system does not solve their problems or does not do what they expect, they won’t use it. There is where we see the resistance to change from users when they don’t feel part of the information system planning, and when they feel that all decisions were made without considering their points of view.
Information systems need a strategy that helps the organization gain a competitive advantage, reduce costs, or help with productivity
If the requirements are not clear or unknown at first, an agile approach will help the team understand the needs of the users while delivering incremental updates and gathering feedback from the market.
The product vision needs to be created by the entire team because even though the product owner will be the person reminding the team about the vision and goals of the project, everybody needs to contribute and own the product vision.
Even though, the test is your knowledge is about being a Product Owner using the Scrum guide, in reality, the Scrum guide is not enough for you to pass it. Therefore, you are required to find other sources that might help you complement your knowledge for being a good Product Owner using the Scrum framework.
Time to market is essential and projects usually have budget constraints which means that they cannot be developed for a long period of time without producing value to the customers or the company. Therefore, it is necessary to pick what must be created first.
The roadmap informs all stakeholders of the status of the product and what they should expect in the next months in terms of releases. Of course, this is a living document, and feedback from the users or reacting to the market might change the product roadmap.
Most companies (and startups) have a small team for web design and development. Thus, you will be wearing different hats during the development or maintenance of a product.
I think of Pico as a cross between a CSS reset and a CSS framework