Hi,
Does your book cover Scrum from scratch ?
Can I please get a clear understanding of the Scrum workflow ? I have a tutor at my university who teaches Scrum in a weird fashion which I have been unable to google as well so far. What I've been taught is that - I have a product backlog which contains my epic level user stories which are further broken down into feature level epic level user stories (this is what she calls them in the assignment spec as well - we did a make belief Scrum based assignment). Following this, I groom my product backlog (she means arrange them in order of priority and not add-on more information/ provide clarity on certain user stories) and pick the top most user stories, lets say the top 10, and break them into technical level user stories and place them into the Sprint backlog. Sometimes she says that we maintain another backlog for the feature level epic level user stories, and sometimes they go in the product backlog which is a bit confusing - although as per Mountain Goats website, a product backlog has features as well.
The technical level user stories has multiple acceptance conditions which are then placed on the TODO lane of your kanban board (maybe broken into low level tasks - this is not taught to us nor answered properly). I have found some links in Mountain Goat as well as the Scrum Alliance but the rest of the terminologies seem quite new to me (and also Google apparently) which does not put me in a good place as this seems somewhat different to the literature out there.
Also, in the Sprint Retrospective - I have been told that we do not bring in the product owner, however, Mountain Goat's website states that the Product Owner also attends this which is contradictory to what was taught to us. Can you please provide some clarity on these ? Any and all help would be much appreciated.
Thanks!