Thanks for the kind comment.

Hi Thanks for the kind words. I'm happy you enjoyed it. The video was initially made with the purpose of giving an introduction to Scrum and the Scrum Guide. Happy that it still works within that context.

yES I AGREE WITH YOU

Great that you liked it.

Hi Adam, You are totally right! The Product Backlog Refinement as well as the Sprint cancellation are Best Practices and NOT Scrum Events as I'm stating in the video. Thank you for pointing this out, and taking your time to post your comment.

Hi Partha, Thanks so much for the kind word! I do hope you will have great experiences in your continued Scrum journey. /Per

Thanks for the kind words. Happy that you enjoyed it.

Thanks a lot!

Hi Malcolm, Thanks! It's based on the Scrum Guide 2013 version. And Since I've made it - 4 years ago I've noticed a few errors: The PBL Refinement and The Sprint Cancellations are Best Practices and not Events. But beside that - I agree: The first 12 min. gives a good overview of Scrum (quick intro for everyone new to SCrum and Agile). And the remaining are a good listing of a lot of the facts for the CSM Certification and also for the Scrum.org PSM I Assessment. Thanks for you taking the time to comment! Brgds Per

scrumguides.org/scrum-guide.html agilemanifesto.org/

Hi, Thanks for adding the reference to the actual book: The Scrum Guide: scrumguides.org/scrum-guide.html

Thanks a lot!

I've been told it's used by some CSM and PSM Trainers as an introduction for their students for Scrum.org PSM I Professional Scrum Master Assessment and the CSM Scrum Master Certification. I also use it myself for prepping the students of my Scrum Master Classes for the Scrum.org PSM I Assessment.

scrumguides.org/scrum-guide.html agilemanifesto.org/

Gmh918283731 Ach675848 I

It's the development team that is accountable for the estimates. They are definitely allowed to consult the Product Owner on details. As mentioned there is no tester role in Scrum by the book.

Well, I agree with the concept of 'self organization' and some organizations perhaps authorize developers for estimation. I'm new to JIRA and have been following Agile (Scrum) as opposed to Agile (Kanban) for the last last 30+ months and in many projects. In our organization, estimation is a democratic process (highest votes for each estimation gets approved) to decide either Story Point or Hours for each Sprint. I'm still not sure how Scrum process works without tester! As far as I know from my 6+ years experiences in software testing, Developers DO NOT test except Unit testing, let alone being known as Testers.

I have been in contact with many teams, where the tester title is not existing. Its typically due to really high maturity - both in regards to the Agile mindset and the Teams Maturity (teams are definitely in the Performing state - with reference to Tuckmans model). In Jira - you are totally correct - there are 2 templates that can be used for working agile: The Scrum setup/Template and the Scrum setup/Template. The video is a visualisation of whats included in the Scrum Guide. So it's not a "Scrum as implemented in Jira" or "Scrum as implemented in my company". Important is probably also to state that Scrum is a framework - not a process. When you implement all the elements of scrum - and decide how you and your team will adhere to the elements - then you have a process. I hope that clarifies even more.

Thanks for watching that much. The video is as mentioned with set off in Scrum by the book. So no Tester role. The impediments are raised by the development team. If not when they are encountered, then at the latest at the daily scrum. You can find all the details in the Scrum Guide - by Kenneth Schwaber and Jeff Sutherland: scrumguides.org/scrum-guide.html Jira is (as you probably already know) a software tool - and the process in there can be customized any way you want. So It's not necessarily following Scrum by the book. And in real life a lot of organisations have a specific role for the Quality Assurance part of systems/product development. In my experience - with the teams with the highest level of Agile and Team Maturity: moving away from specific titles makes work a lot better flowing. It's not easy to get there. And sometimes personal agendas needs to be broken down and some I highly recommend the book "Joy .Inc" by Richard Sheridan (menloinnovations.com/joyinc/) for some great ideas on how working in pairs could help moving teams and companies into that direction. It's OK that your being a little sarcastic. I'm sure that in your world a tester is needed. And don't misunderstand me: Testing or quality Assurance is important - also in Scrum. But no specific role is titled for that. In the Same way there is no title for Architects, Usability Experts, User Interface designers, Business Analysts, Test Managers etc. etc. Thanks for your comments! I hope I was able to give a bit more details to why there is no tester in Scrum by the book. /Per

Please do not get me wrong. I'm not a rolecentric person. Your concept and presentation in premise of SDLC under Agile framework is much more resourceful than many others' on KZfaq. Except that in your Scrum, no role or contribution of testers is acknowledged!

Hi, Thanks for this clarification, with a clear link to the content of the Scrum Guide. /Per

Hi Mokter Ahmed, Thanks for your comment. The video is related to Scrum with emphasis on "by the book". And Neither Acceptance criteria nor Tester role is part of Scrum. Scrum specifically states that all people in the Development Team have titles of developers - no matter what kind of work they are performing. This supports the selforganizing element of the development team - and fuels the cross-functionality.

Hi, Sorry that you didn't like my video. We all learn differently. The great thing about the internet is that you can always find something else that will fit your preferences. /Per