Algunas preguntas de las tareas (exámenes) no son claras, y algunas respuestas son confusas donde, para una única opción hay dos posibilidades de respuesta. También, el generarlo solo en ingles aún cuando tenga subtítulos no genera buen aprendizaje.

The content was good but sloppy. The material and the quizzes occasionally don't align. There are links to learning material that is behind a paywall. There are several typos. It doesn't feel very professional.

It is a good course but for someone who is new to this framework, the course is too brief. It felt like a who book of 200 pages was summarized in 2-3 sentence. But this is personal opinion.

the worksheets dint sow the live graph and the video can't be enlarged to full screen. when I went to enlarge it so i could read the graphs the audio still worked but the picture was black

El curso está bien, la pega está en que tanto los videos como la información adicional están en Ingles, pero los textos explicativos y los cuestionarios en español.

Some links go to wikipedia pages and this is a no reliable source of information.

not enough to leverage your scrum skillset in addition to there is no practice

it is very software specific

NA

Poorly written content with consistent grammatical errors, questions that often did not match the content given, or even conflicted between the videos and the given links. When the links still worked, that is. Additionally, the videos did not work on my iPad, only showing partially. I have taken many other Coursera courses with no issues. This course was enough to familiarize me with the terms, but that's all.

Hi! This course will not help you if you plan to be prepared for PSM exam. Choose another course.

This is not very good. The questions asked are a lot of times bad written or make no sense.

There were various inconsistencies, and the many typos indicated a certain sloppiness.

If I did not already know SCRUM methodology, this would be a useless training. As it is, it is barely a refresher on terminology. Also, many of the questions are bizarrely worded or even wrong. For example, why on earth is "Reprioritize the stories" the correct answer over "Evaluate the issue" when a team runs into an issue during a sprint? What if the issue has nothing to do with the user story that the team is trying to complete? Why is this issue suddenly deemed an insurmountable obstacle without evaluating the impact on the user stories? And if it is such an insurmountable obstacle, like the entire internet went belly-up and everyone's work is stored on the cloud, then reprioritizing users stories is a waste of time!

Graphs not presented properly. Mistakes. Not a good course material.

Not engagening & boring