I will continue watching the courses in the Specialization, hoping that maybe the next ones will be useful. But overall, I would say that they course is not really oriented at the real world. I appreciate the quality of the videos and the animations. But the purpose of the animations and the concept of the course are still not clear to me. Course seems to pay a lot of attention to the Agile without clearly explaining how Agile works. Seems to be almost a commercial to the Agile approach, without any good argument why should you use it.

I found quizzes, in-video questions and animations to be barely relatable to the course. Most of the things that are asked in the quizzes are not explicitly explained throughout the course, answers have to be rather guessed that learnt or extrapolated.

Also, in real world, SPM job requires not just the knowledge of the waterlike theory, but a lot of tech skills that are not mentioned in the course.

The course seems to be a course in Scrummerfall, i.e., a mixture of Scrum and Waterfall. After having briefly discussed the Agile Manifesto, which emphasizes things like "People over processes," what is the first thing that they dive into? Processes where they say things like "Requirements combined with processes are the backbone of any successful software project." I would disagree. Requirements and processes are important, but people and communications are the backbone of any successful software project.

I'm dropping this specialization and searching for another course that really follows Agile methodologies.

The instructors seem like they are reading from a teleprompter, and it feels like they are robots. Also very bad transition editing between scenes. All instructors should use more body language, and explain the info as if they where giving a life class, not some verbatim script. Other than that is fine.

Only the link agilemanifesto.org has real value in this course. The rest is self-PR and "water". I see no reason paying for the sertificate and I am not convinced further cources of this specialization will deliver greater value.

Dry principles without real life examples and exercises. You can passed the quiz by just reading online or have basic project management experience. Disappointed.

A little disappointed in this course, it would have been better suited for the first part to a larger course other than a week long introduction to th subject.

Informative, but I kind of knew a lot of the material. Was hoping to learn something concrete and useful. I'm hoping the next courses will be informative.

Very, very basic... more like fishing for customers to apply for the other courses. Yet, still quite the motivated and enthusiastic team.

Extremely basic. Spent more time introducing the tutors than telling us much about the topic.

Defiantly the worse MOOC I have taken. Does the specialisation need such a long introduction?

An extra long introduction and a lot of sales pitch. Quite a limited value for beginners.

Requesting to have in-depth of Agile working process with real time examples

The quizzes are about the course structure and not product management.

Not really about Product Management, but about Project Management

The Course could have been covered in a more interesting way

Small introduction. I was expecting some thing concrete.

Low on content. Lacks of specific actions

Too general without any specific skills

need more examples to be more specific

Could be more concise.

can be better

Fair course

This is a very old fashion way of looking at development and developers. Where developers are considered resources and minions that need to follow orders. Modern development techniques value developers and allow them to be much more active players. Product Manager is not a MANAGER but a facilitator. This course describes the view that developers are loose canons that need to be managed and that upfront planning and estimation are the right path. I do not agree at all with this view.

Should you happen to agree with this view, the Course is well explained and presented well.

Difference between a Software Project and a Software Product - of course it is defined by convention, but it is there and is pretty generally understood. Typical software projects are bespoke applications developed for the use of one organization and typically automates a business process. A S/w product, on the other hand, is built and sold to a range of users in the target group, who can be individuals to large organizations. This course does not seem to address any of the issues faced by a S/w Product Manager. I think this course completely misses the point.

Unfortunately, this course focuses on the role of an IT delivery manager / development team lead rather than looking at the business side a Product Owner or Product Manager will mostly care about. I cannot see the focus on the job a Product Owner / Manager (as in Scrum) will do. Therefore no value added for me. Apart from that, I miss the use of helpful graphics / slides in the videos and do not see a consistent use of references for the statements made.