Excellent! There is a lot of great practical info you can apply in real life. I would suggest instructors include some more info about SPM in the framework of startups (rather than client framework).
It is very good knowledge. But my English poor for that, was, sometimes. So was hard to understand and catch information. As a result 90% for grade. It is ok. But it is ok.\n\nViam supervadet vadens
por Baby J M•
por Ezaden S M•
por Sergio L T P•
por Aya K•
por Chanchal D•
por Boris S•
por MAYANK R•
por david w•
por Freek d B•
It's challenging to teach and learn product management through an online course. You can get an overview of the important topics and learn the theory, but this doesn't enable discussion, exchanging experiences, and forming balanced opinions. A product management does a lot of her/his work by talking (to many different people involved), which is very difficult to train online (it could be done with role playing assignments supported by video conferencing, but I think learning from experienced colleagues in practice is a much better way). The quizzes are often a good way to rehearse the topics that have been explained, but sometimes feel like an extremely simplified black-white view on very nuanced issues.
The best parts of the Software Product Management courses for me were the larger assignments you make that are reviewed by fellow students (getting feedback is very useful and it's also instructive to see what approach your peers took) and the interviews with experienced product managers which offer valuable insights in the complicated situations product managers often have to deal with.
I recommend this course to anyone that is new to software product management and quite new to software development. The course can be a good first step on your path to becoming a product manager, as long as you realize that you will also need a lot of skills that an online course cannot teach you.
por Gaurang R•
too much content in one lesson and and in one module
practical questions are time consuming and thus should be avoided
course duration is too much and there are too many videos to study
all items are covered in too much details which does not required for those who just want to know basics
there should be smile and joy while teaching us, but the instructor are just like a puppet
no body language, action is used while delivering lecture and thus i feel it is like mugged up lecture
drawing wireframe, writing user story, etc. should be avoided
por Gabriella H•
Not all supplementary resources are available. It appears they have expired, and course creators need to update this.
The video lessons often seem to be a regurgitation of the course notes, with not much additional value.
Just as correct answers in assignments and quizzes are explained, incorrect answers should also be explained, so you understand why a possible answer is NOT correct. In line with this, I did not value from any feedback received from the peer reviewed assignments.
Otherwise I throughly enjoyed this course.
por Richard J H•
I know a lot of work went into preparing this material. Although the Table of Contents serves this purpose in a more text-rich, visually complicated way - something I would find very useful is a step by step table or guide (to ensure no step is skipped) for the entire process, i.e.
Story Board development
User Story Development
Product Backlog Development
and so on. I hope this will be helpful.
por Zeeshan C•
It was a good course for general software requirement gathering. But I feel, it is more relevant when a project has already started. Most often, as a services provider, you need to collect information before signing a contract with the client, so you can prepare estimates and quote a price.
Most clients are not willing to invest much time sharing this information with you before an SOW has been formally signed.
por Kaspar G•
The introduction to client requirements was quite helpful. However, what was missing for me is what to do with those requirements, like breaking them down into smaller requirements and going more closer to the software. Therefore, for me it was a quite good introduction into user stories. But nothing more.
por G S R•
This course is good for foundations for requirement gathering. The documentation aspects are covered in detail. But still, the coursework on analysing, workflow and prioritization can be improved because this too plays an important role when dealing with Dev team.
por Dirk S•
The target group are students without any experience. The quiz's live are made to test your knowledge of the English language.
por German D H•
not as well put together as the previous ones - perhaps you should consider breaking it into smaller, manageable pieces.
por Sheldon D S•
The material / question sets does appear ambiguous with little context to answer questions confidently.
por Cecil R•
The exam questions could have been written more clearly.
por Neha P•
Questions in the last assesment were quite confusing
por Mikhail K•
Too high level course. Expected more from it.
por Néstor d J M G•
por Katherine P Z•
Incredibly frustrated by the peer grading system. I've been able to work on the course at relatively fast pace and have now completed all of the lectures, readings, quizzes and test but can't go on to the next course because not enough people have submitted the homework for me to grade. I understand the advantage of being able to "learn from others" but it doesn't outweigh the disadvantage of not being able to work at one's own pace .
por Lino J J•
I don't know how useful the ambiguous requirements exercise is when we only have one-way feedback. I also think that the ambiguous requirements exercise is the most important of the course, and the exercise missed the mark.
I would suggest you structure that exercise as a dialogue, where a PM is working with the customer to elicit requirements, and not give us a big long wish-list of functionality. Structured as a dialogue, you can show that a PM would ask, "You said that the game would make noise. When is the first time it makes noise? How often would game noises be made? Does it ever stop? What makes it stop? Why even have the game make noise in the first place? Are there different noises made during the course of game play/"
So, I can't recommend this particular course, and I'm concerned about what the capstone will look like if you give us an assignment where we're to make sense of functionality delivered as a block of text .