Learner Reviews & Feedback for Reviews & Metrics for Software Improvements by University of Alberta
About the Course
Top reviews
Does let you know practices that help in making the right product that is managed right and done right, with retrospective techniques that can be implemented after the project is completed.
In this course, I lean a lot of things based on review and metrics for software, such as sprint iteration, project iteration, daily scrum, project perspective, and many more.
101 - 125 of 168 Reviews for Reviews & Metrics for Software Improvements
By Vladimir F
•It works!!!
By Rahul S
•best course
By tunc b
•Very Good!
By Olusola K
•excellent
By Siva S
•Very Good
By Bhargav B
•I LOVE IT
By Winston M K
•Awesome!
By Predrag S
•Awesome!
By Natalia S
•Thanks!
By Kalynenko M
•perfect
By CHETAN N
•AMAZING
By Abdulrahman F
•thanks
By Muhammad Z H
•Thanks
By Dmitry
•nice!
By Shaswata G
•great
By Oleksandra S
•Good!
By Souhardya G
•Good
By KARMANYA D
•nice
By Rafael N
•Top!
By karan.j 1
•yes
By Reto W
•-
By Gokulnath R
•G
By Jason M
•T
By Orlando C
•I'm happy with the course, just some small issues: I know in the Capstone Projects the students will use the concepts learned throughout the specialization, but it would be great also to highlight some specific moments when the tools taught in this course are meant to be used. Theoretically is mentioned, but practical examples would help, like a 5 min video explaining a real-life project schedule - timeline and how the metrics and meetings were distributed along the life cycle. For example, now I am confused about what to do after a Sprint and a Release, when should I set up the retrospectives (the day after? the week after?), in which order, etc.
By Liudmila D
•Generally I like the course. However few areas might be improved in order to increase the value of it.
1) More specific metrics examples. Expected much more than I saw...
2) More up to date literature for reference (this is general concern on all Product Management specialization courses).
3) Link the advises in the course to budgets. There are a lot of advises that "good for the project", however reality has limited budgets and every "good practice" has a cost to pay. I would be happy to see more links to reality. Not in $$$ but in time. For example: this practice may will take full team 1 day, but it saves up to 5 days in the end.
Coursera Footer
