Matthew Venamore
Dynamics 365 Scrum Master
1. Content understanding and relevance
How well do you feel the course content met your learning objectives? - Were there any topics you found particularly relevant or irrelevant to your needs?
My learning objectives for the course were to further expand my understanding of best practices using the learning and experience of others. Mostly it was a re-iteration of the techniques I have (and still am) already been using. So, it was useful to confirm that understanding, but on the most part it wasn't much new for me - I have been doing software delivery for 30 years now, so that is a good thing. :D Where it was useful was to see your approach for how you pull together all the different elements into a singular framework, which is something I have been doing myself from my own perspective. So seeing your framework was very usefull to visualise something that has really just been in my head to date. A couple of nice tips alongs the way were also useful, but in particular how you applied your framework to different use cases was really helpful.
2. Course structure and organization
Is the course structure logical and easy to follow?- Would you suggest any improvements to the way the course is organised?
Yep, definitely fits in with my logical thinking so I appreciated that! :) As I mentioned the framework you built is the biggest element of use for me, especially as a scrum master/delivery lead.
3. Materials and templates
How useful do you find the templates provided as part of each module?- Are there additional templates or resources you wish had been included?
Yep, was really useful to be able to review those. Hopefully, I can add some of them into my toolbelt as well. :)
4. Challenges and difficulties
Are there any parts of the course you found particularly challenging or confusing?- How could these areas be improved in future iterations of the course?
Nothing that was too challenging or confusing, more so that there might be a few approaches that don't fit well with my personal empirical approach. For example, there doesn't seem to be a feedback cycle from the actual build and demonstration of the product. From my experience, even though wireframes, target designs and prototypes are useful starting points, the devil is in the detail (especially in larger product replacements), so using empiricism is critical to the value that gets delivered to the client. I think your framework could do with considering what is learnt from the actual build and delivery, as this will also change the understanding of the requirements and feasibility/validity. Anyway, happy to talk further about that if you wish. :)
5. Assignments
Have you done and applied some of the assignments on your projects?- Did you find some of the assignments more valuable than others?
To be frank, we just started a large project so we had already recently done all the elements you mentioned, so I didn't re-do them - I just revalidated against what we had done recently to find any areas of improvement.
