title
🔥Certified Scrum Master Full Course | Scrum Master Training | Scrum Master Course | Simplilearn

description
🔥Certified ScrumMaster® (CSM) Certification Training Course: https://www.simplilearn.com/agile-and-scrum/csm-certification-training?utm_campaign=CertifiedScrumMasterFullCourse17feb2023&utm_medium=Descriptionff&utm_source=youtube In this Scrum Master full course, we will explain the most important concepts of the Scrum Methodology. We'll tell you about what is scrum, the components of the scrum process, the role of a scrum master, the scrum methodology, how scrum meetings work, how scrum and kanban are different from one another, interview questions, and much more! Below are the topics we will cover in this video: 00:00:00 What is Scrum 00:34:39 Agile Scrum Master Training 01:58:26 Scrum Master Role and methodology 02:20:40 Scrum Meeting 02:30:09 Scrum Vs. kanban 02:41:50 Scrum Interview Questions 🔥Free ASM Course: https://www.simplilearn.com/agile-scrum-master-basics-skillup?utm_campaign=CertifiedScrumMasterFullCourse17feb2023&utm_medium=Description&utm_source=youtube ✅Subscribe to our Channel to learn more about the top Technologies: https://bit.ly/2VT4WtH ⏩ Check out the Agile Scrum training videos: https://bit.ly/3f9kzF3 #ScrumMasterCourse #CertifiedScrumMasterFullCourse #ScrumMasterertificationTraining #ScrumMasterTutorial #ScrumMasterTraining #ScrumMasterCertification #BecomeCertifiedScrumMaster #AgileScrumTraining #Simplilearn ➡️ Certified ScrumMaster® (CSM) Certification Training Course This CSM certification course is focused on providing an improved understanding of Scrum methodologies and their implementation. It helps you become a Certified ScrumMaster®, a designation offered by Scrum Alliance to practitioners who have successfully completed a CSM certification course & demonstrate their understanding by passing the exam. ✅ Key Features - 2 Days of Online Virtual Class - CSM® exam fee included - Get trained by globally acclaimed Certified Scrum Trainers (CSTs) with Free Exam Retake - 20 PDUs and 16 SEUs - Two-year membership in Scrum Alliance - Complimentary access to 15 courses* worth INR 25,000 ✅ Skills Covered - Scrum and Agile methodologies - Importance of Agile - Scrum lifecycle - Scrum terminologies - Daily scrum and review - Roles involved in Scrum - Distributed Scrum 👉Learn More at: https://www.simplilearn.com/agile-and-scrum/csm-certification-training?utm_campaign=CertifiedScrumMasterFullCourse17feb2023&utm_medium=Description&utm_source=youtube 🔥🔥 Interested in Attending Live Classes? Call Us: IN - 18002127688 / US - +18445327688

detail
{'title': '🔥Certified Scrum Master Full Course | Scrum Master Training | Scrum Master Course | Simplilearn', 'heatmap': [], 'summary': 'This scrum master full course covers key concepts related to scrum, agile methodologies, scrum framework, devops, user stories, agile velocity, scrum essentials, agile team, scrum and kanban in agile, and user stories in mobile app development, offering insights into methodologies, challenges, and practical applications.', 'chapters': [{'end': 60.289, 'segs': [{'end': 60.289, 'src': 'embed', 'start': 16.107, 'weight': 0, 'content': [{'end': 19.889, 'text': 'Hey guys, welcome to Scrum Master full course video by Simply Learn.', 'start': 16.107, 'duration': 3.782}, {'end': 24.572, 'text': "In this video, we'll cover some of the most important concepts related to Scrum.", 'start': 20.61, 'duration': 3.962}, {'end': 34.438, 'text': "We'll talk about what exactly Scrum is, the components of Scrum process, the role of a Scrum Master, the Scrum methodology, how Scrum meetings work,", 'start': 24.912, 'duration': 9.526}, {'end': 38.62, 'text': 'how Scrum and Kanban are different from one another and, finally,', 'start': 34.438, 'duration': 4.182}, {'end': 42.663, 'text': "we'll cover some important interview questions that will help you ace your interview.", 'start': 38.62, 'duration': 4.043}, {'end': 48.265, 'text': 'Our instructors, Jeff and Chandra, will help you understand the topics with ease.', 'start': 43.323, 'duration': 4.942}, {'end': 53.807, 'text': "Before we begin, don't forget to subscribe and click that bell icon to never miss an update from us.", 'start': 48.645, 'duration': 5.162}, {'end': 56.348, 'text': "Now, let's jump right in.", 'start': 54.667, 'duration': 1.681}, {'end': 60.289, 'text': 'Hi, welcome to Scrum Tutorial from Simply Learn.', 'start': 56.888, 'duration': 3.401}], 'summary': 'Scrum master full course covering key concepts, methodology, and interview questions by simply learn.', 'duration': 44.182, 'max_score': 16.107, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw16107.jpg'}], 'start': 16.107, 'title': 'Scrum master full course', 'summary': 'Covers key concepts related to scrum, including its components, the role of a scrum master, methodology, differences from kanban, and important interview questions.', 'chapters': [{'end': 60.289, 'start': 16.107, 'title': 'Scrum master full course', 'summary': 'Covers the key concepts related to scrum, such as its components, the role of a scrum master, methodology, differences from kanban, and important interview questions.', 'duration': 44.182, 'highlights': ['The chapter covers the key concepts related to Scrum, such as its components, the role of a Scrum Master, methodology, differences from Kanban, and important interview questions.', 'The video will cover some of the most important concepts related to Scrum, providing a comprehensive understanding of the topic.', 'The instructors, Jeff and Chandra, will help you understand the topics with ease, ensuring effective learning.', 'The video will cover important interview questions that will help you ace your interview, providing valuable insights for career advancement.', 'The role of a Scrum Master and how Scrum meetings work will also be explained, aiding in understanding the practical aspects of Scrum implementation.']}], 'duration': 44.182, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw16107.jpg', 'highlights': ['The video will cover important interview questions that will help you ace your interview, providing valuable insights for career advancement.', 'The chapter covers the key concepts related to Scrum, such as its components, the role of a Scrum Master, methodology, differences from Kanban, and important interview questions.', 'The video will cover some of the most important concepts related to Scrum, providing a comprehensive understanding of the topic.', 'The role of a Scrum Master and how Scrum meetings work will also be explained, aiding in understanding the practical aspects of Scrum implementation.', 'The instructors, Jeff and Chandra, will help you understand the topics with ease, ensuring effective learning.']}, {'end': 757.502, 'segs': [{'end': 254.769, 'src': 'embed', 'start': 227.865, 'weight': 0, 'content': [{'end': 233.91, 'text': 'So agile means moving faster, being flexible, responding to the changes.', 'start': 227.865, 'duration': 6.045}, {'end': 239.375, 'text': 'Now agile is a set of methods and practices that focuses on iterative development.', 'start': 234.851, 'duration': 4.524}, {'end': 240.676, 'text': 'Why iterative?', 'start': 239.936, 'duration': 0.74}, {'end': 243.059, 'text': 'In each iterations,', 'start': 241.077, 'duration': 1.982}, {'end': 251.026, 'text': 'agile methodologies helps us to create a working piece of the software product which will help us to make quick corrections to those software piece.', 'start': 243.059, 'duration': 7.967}, {'end': 254.769, 'text': 'This is not a whole product, it is part of that bigger product.', 'start': 251.426, 'duration': 3.343}], 'summary': 'Agile enables faster, iterative software development for quick corrections and flexibility.', 'duration': 26.904, 'max_score': 227.865, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw227865.jpg'}, {'end': 422.411, 'src': 'embed', 'start': 380.215, 'weight': 2, 'content': [{'end': 387.584, 'text': 'So scrum in specific have something called daily scrum where 15 minutes meeting where entire scrum team should come in.', 'start': 380.215, 'duration': 7.369}, {'end': 389.685, 'text': 'Sit together.', 'start': 388.284, 'duration': 1.401}, {'end': 393.428, 'text': 'Self-organizing team, as well as all that agile team, has to come together,', 'start': 389.685, 'duration': 3.743}, {'end': 398.331, 'text': 'Express what they have completed before the last daily scrum meeting and what is pending?', 'start': 393.428, 'duration': 4.903}, {'end': 402.034, 'text': 'Why is it pending and what is that they are going to do before the next meeting?', 'start': 398.512, 'duration': 3.522}, {'end': 403.815, 'text': 'so all these are expressed.', 'start': 402.534, 'duration': 1.281}, {'end': 410.38, 'text': 'this will help the team, as well as the scrum master, as well as the product owner, the visibility into what is complete,', 'start': 403.815, 'duration': 6.565}, {'end': 422.411, 'text': 'what needs to be completed and and this will help project manager or scrum master to provide the necessary inputs better visibility to the customers and stakeholders as well.', 'start': 410.38, 'duration': 12.031}], 'summary': 'Daily scrum meetings allow scrum teams to discuss completed tasks, pending work, and plans, providing better visibility and input for project managers and stakeholders.', 'duration': 42.196, 'max_score': 380.215, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw380215.jpg'}, {'end': 478.228, 'src': 'embed', 'start': 444.076, 'weight': 1, 'content': [{'end': 446.518, 'text': "and this doesn't happen only with the project team.", 'start': 444.076, 'duration': 2.442}, {'end': 453.543, 'text': 'it also happens with customers and every stakeholders who are involved in the project.', 'start': 446.518, 'duration': 7.025}, {'end': 461.128, 'text': 'so next, high quality development, testing and collaboration is ensured, since the project is broken down.', 'start': 453.543, 'duration': 7.585}, {'end': 468.645, 'text': 'so now each iterations, each module, each piece of software which is being created are tested regularly.', 'start': 461.128, 'duration': 7.517}, {'end': 470.645, 'text': 'feedbacks are obtained from the user as well.', 'start': 468.645, 'duration': 2}, {'end': 478.228, 'text': 'active involvement of user are ensured so that they are acknowledging it, so the what customer needs are given.', 'start': 470.645, 'duration': 7.583}], 'summary': 'Project involves all stakeholders, ensuring high-quality development, testing, and collaboration with regular testing of each module and obtaining user feedback for customer needs.', 'duration': 34.152, 'max_score': 444.076, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw444076.jpg'}, {'end': 602.451, 'src': 'embed', 'start': 577.564, 'weight': 4, 'content': [{'end': 584.926, 'text': "So that's what the more and more discussion which is happening, which requires closer collaboration with consumers and their feedbacks,", 'start': 577.564, 'duration': 7.362}, {'end': 588.226, 'text': 'their experiences with the products or services which are being used by them.', 'start': 584.926, 'duration': 3.3}, {'end': 590.187, 'text': 'It is very essential to understand.', 'start': 588.747, 'duration': 1.44}, {'end': 594.728, 'text': 'so then, various different methodologies, what we have in agile.', 'start': 591.727, 'duration': 3.001}, {'end': 602.451, 'text': 'we can speak about scrum, kanban, extreme programming, that is, xp, lean methodologies, the crystal.', 'start': 594.728, 'duration': 7.723}], 'summary': 'Closer collaboration with consumers to understand agile methodologies like scrum, kanban, xp, lean, and crystal.', 'duration': 24.887, 'max_score': 577.564, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw577564.jpg'}], 'start': 61.709, 'title': 'Agile methodologies and scrum', 'summary': 'Discusses the challenges of traditional waterfall model, the benefits of agile methodologies including improved accountability, predictability, flexibility, and value realization, and the history and evolution of the scrum methodology from 1986 to 2010.', 'chapters': [{'end': 251.026, 'start': 61.709, 'title': 'Understanding agile and scrum basics', 'summary': 'Discusses the challenges of traditional waterfall model, highlights the need for agile methodologies like scrum to enable quick changes and emphasizes the iterative and flexible nature of agile for faster and customer-centric software development.', 'duration': 189.317, 'highlights': ['Agile methodologies like Scrum enable quick and efficient changes in software development, reducing time and cost implications, making it acceptable to both project organization and customer. Scrum facilitates quick and efficient changes in software development, reducing time and cost implications, making it acceptable to both project organization and customer.', "The limitations of the traditional waterfall model are outlined, emphasizing its inability to accommodate changes quickly, leading to time-consuming efforts and increased costs. The traditional waterfall model's limitations are outlined, emphasizing its inability to accommodate changes quickly, leading to time-consuming efforts and increased costs.", 'Agile is defined as a set of methods and practices focused on iterative development, allowing for quick corrections and flexible responses to changes in software development. Agile is defined as a set of methods and practices focused on iterative development, allowing for quick corrections and flexible responses to changes in software development.']}, {'end': 757.502, 'start': 251.426, 'title': 'Benefits of agile methodologies', 'summary': 'Discusses the advantages of using agile methodologies, such as improved accountability, predictability, flexibility, and value realization, as well as the history and evolution of the scrum methodology from 1986 to 2010.', 'duration': 506.076, 'highlights': ['The active involvement of customer has to be ensured so they are actively involved, providing feedbacks every now and then to avoid surprises at the end, which used to happen during waterfall approaches. Active customer involvement ensures feedback at every stage, avoiding end surprises, a contrast to waterfall approaches.', 'Agile emphasizes on having collaboration, such as through daily scrum meetings, where the team provides visibility into what is complete and pending, improving accountability and visibility to the customers and stakeholders. Agile promotes collaboration through daily scrum meetings, enhancing visibility and accountability to customers and stakeholders.', 'The ability to predict and the visibility into the project increases as discussions and brainstorming progress, allowing easier prediction and improved visibility for the project team, customers, and stakeholders. Increased discussions and brainstorming improve project predictability and visibility for the team, customers, and stakeholders.', 'The need for agile methodologies has become more important due to changes in market conditions, increased competition, and the need to respond to consumer and market variations, highlighting the importance of organizations and service providers to understand and respond quickly to dynamic scenarios. The importance of agile methodologies has grown due to changing market conditions and the need for quick responses to dynamic scenarios.']}], 'duration': 695.793, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw61709.jpg', 'highlights': ['Agile methodologies enable quick and efficient changes, reducing time and cost implications.', 'Active customer involvement ensures feedback at every stage, avoiding end surprises.', 'Increased discussions and brainstorming improve project predictability and visibility.', 'Agile promotes collaboration through daily scrum meetings, enhancing visibility and accountability.', 'The importance of agile methodologies has grown due to changing market conditions and the need for quick responses.']}, {'end': 1654.214, 'segs': [{'end': 785.621, 'src': 'embed', 'start': 757.502, 'weight': 1, 'content': [{'end': 764.366, 'text': "so that's where the adoption of agile, the benefit of adopting agile, were realized and scrum become popular.", 'start': 757.502, 'duration': 6.864}, {'end': 766.668, 'text': 'So what is Scrum??', 'start': 765.747, 'duration': 0.921}, {'end': 768.289, 'text': 'So let us look at that.', 'start': 767.308, 'duration': 0.981}, {'end': 774.153, 'text': 'So now Scrum is a framework that enables teams to work together.', 'start': 769.41, 'duration': 4.743}, {'end': 777.675, 'text': 'Means collaboration is very important while we become agile.', 'start': 774.993, 'duration': 2.682}, {'end': 783.119, 'text': 'So with Scrum team one can look, I mean see and experience.', 'start': 778.516, 'duration': 4.603}, {'end': 785.621, 'text': 'So learning from experiences happens.', 'start': 783.859, 'duration': 1.762}], 'summary': "Agile adoption led to scrum's popularity, enabling collaboration and learning from experiences.", 'duration': 28.119, 'max_score': 757.502, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw757502.jpg'}, {'end': 836.038, 'src': 'embed', 'start': 812.064, 'weight': 0, 'content': [{'end': 820.348, 'text': 'and then some of the benefits using scrum would look like steam can provide project deliverables, and in an efficient manner.', 'start': 812.064, 'duration': 8.284}, {'end': 824.07, 'text': 'so in time we are completing all the features and functionality.', 'start': 820.348, 'duration': 3.722}, {'end': 828.872, 'text': 'so the the entire model, the methodology, what is there which helps in accomplishing those?', 'start': 824.07, 'duration': 4.802}, {'end': 833.176, 'text': 'Then further time and money are used efficiently.', 'start': 830.194, 'duration': 2.982}, {'end': 836.038, 'text': 'So time is very important.', 'start': 833.937, 'duration': 2.101}], 'summary': 'Using scrum can provide project deliverables efficiently, completing all features and functionality on time and utilizing time and money efficiently.', 'duration': 23.974, 'max_score': 812.064, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw812064.jpg'}, {'end': 1015.802, 'src': 'embed', 'start': 970.81, 'weight': 3, 'content': [{'end': 976.734, 'text': 'deviations which occurs further, maybe, scrum master, sit with them separately to understand that in detail.', 'start': 970.81, 'duration': 5.924}, {'end': 983.859, 'text': 'So daily scrum meetings give the quick insights, so that it increases the visibility, what is happening on ground.', 'start': 977.274, 'duration': 6.585}, {'end': 988.606, 'text': 'Constantly involves feedback from clients and customers.', 'start': 985.484, 'duration': 3.122}, {'end': 994.529, 'text': 'As I mentioned earlier while discussing about agile, active involvement of customer is very essential.', 'start': 989.146, 'duration': 5.383}, {'end': 1000.252, 'text': 'So customer should give the feedbacks whenever that working piece of the application or a product is given.', 'start': 995.209, 'duration': 5.043}, {'end': 1001.933, 'text': 'So only then,', 'start': 1000.732, 'duration': 1.201}, {'end': 1009.817, 'text': 'whether the product or that module what is created is having that features and functionality which helps in providing necessary requirement fulfillment.', 'start': 1001.933, 'duration': 7.884}, {'end': 1010.738, 'text': 'Is that happening or not?', 'start': 1009.857, 'duration': 0.881}, {'end': 1015.802, 'text': 'Then making changes based on feedback are very easy,', 'start': 1012.518, 'duration': 3.284}], 'summary': 'Active customer involvement in agile development enables quick feedback and ensures feature fulfillment.', 'duration': 44.992, 'max_score': 970.81, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw970810.jpg'}, {'end': 1130.326, 'src': 'embed', 'start': 1102.666, 'weight': 2, 'content': [{'end': 1111.868, 'text': 'Now when it comes to product owner, so the product owner is primarily responsible for maximizing the ROI by determining the product features.', 'start': 1102.666, 'duration': 9.202}, {'end': 1121.099, 'text': 'prioritizing it into a list what needs to be focused on for the next sprint and constantly re-prioritizing and refining it.', 'start': 1112.873, 'duration': 8.226}, {'end': 1122, 'text': 'so the key points.', 'start': 1121.099, 'duration': 0.901}, {'end': 1130.326, 'text': 'what we need to see here is so one is determining the product features, maximizing the roi, the second one,', 'start': 1122, 'duration': 8.326}], 'summary': 'Product owner maximizes roi by determining product features and constantly re-prioritizing.', 'duration': 27.66, 'max_score': 1102.666, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw1102666.jpg'}, {'end': 1350.941, 'src': 'embed', 'start': 1323.879, 'weight': 4, 'content': [{'end': 1330.198, 'text': 'the direction should be clear to the team, So there are certain artifacts to look at when it comes to scrum.', 'start': 1323.879, 'duration': 6.319}, {'end': 1331.758, 'text': 'So let us look at that.', 'start': 1330.538, 'duration': 1.22}, {'end': 1342.08, 'text': 'So now we speak about the artifacts which are the components of the scrum process that can improve transparency and understanding of the work.', 'start': 1332.638, 'duration': 9.442}, {'end': 1350.941, 'text': 'So there are three artifacts mainly which we call it as product backlog, sprint backlog, then product increment.', 'start': 1342.66, 'duration': 8.281}], 'summary': 'Scrum process includes three main artifacts: product backlog, sprint backlog, and product increment.', 'duration': 27.062, 'max_score': 1323.879, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw1323879.jpg'}], 'start': 757.502, 'title': 'Scrum framework, roles, and artifacts', 'summary': 'Covers the benefits of scrum framework including collaboration, self-organization, efficient project deliverables, time and money utilization, quick feedback, and visibility. it also explains the roles of product owner and scrum master, emphasizing their responsibilities, and details the three key artifacts of scrum - product backlog, sprint backlog, and product increment.', 'chapters': [{'end': 1015.802, 'start': 757.502, 'title': 'Understanding scrum framework', 'summary': 'Explains the benefits of adopting the scrum framework, emphasizing collaboration, self-organization, efficient project deliverables, time and money utilization, quick feedback, and visibility from daily scrum meetings, aiming to improve project efficiency and product fulfillment.', 'duration': 258.3, 'highlights': ['The Scrum framework emphasizes collaboration and self-organizing teams to learn from experiences and work on problems, leading to quick wins and necessary corrections. The Scrum framework focuses on collaboration, self-organizing teams, learning from experiences, and making necessary corrections for efficient problem-solving and quick wins.', 'Using Scrum leads to efficient project deliverables, completion of features and functionality in time, and effective utilization of time and money. Scrum leads to efficient project deliverables, timely completion of features and functionality, and effective utilization of time and money.', "Daily scrum meetings provide visibility and quick insights into the team's progress, involving constant feedback from clients and customers. Daily scrum meetings offer visibility and quick insights into the team's progress, along with constant feedback from clients and customers.", 'Active involvement of customers in providing feedback on the working pieces of the application or product is essential for fulfilling necessary requirements and making easy changes based on the feedback. Active customer involvement in providing feedback on the working pieces is essential for fulfilling requirements and making necessary changes based on the feedback.']}, {'end': 1654.214, 'start': 1015.802, 'title': 'Understanding scrum roles and artifacts', 'summary': 'Explains the roles of product owner and scrum master, emphasizing the responsibilities and objectives of each role, and details the three key artifacts of scrum - product backlog, sprint backlog, and product increment.', 'duration': 638.412, 'highlights': ['The responsibilities and objectives of product owner and scrum master are detailed, emphasizing the importance of maximizing ROI, prioritizing and refining the product backlog, and removing impediments to obtain business value. Maximizing ROI, prioritizing and refining product backlog, removing impediments to obtain business value', 'The three key artifacts of scrum - product backlog, sprint backlog, and product increment - are explained, highlighting their functions in improving transparency and understanding of the work and their respective roles in delivering the requirements of the stakeholders. Functions of product backlog, sprint backlog, and product increment in improving transparency and understanding of work']}], 'duration': 896.712, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw757502.jpg', 'highlights': ['Using Scrum leads to efficient project deliverables, timely completion of features and functionality, and effective utilization of time and money.', 'The Scrum framework emphasizes collaboration and self-organizing teams to learn from experiences and work on problems, leading to quick wins and necessary corrections.', 'The responsibilities and objectives of product owner and scrum master are detailed, emphasizing the importance of maximizing ROI, prioritizing and refining the product backlog, and removing impediments to obtain business value.', "Daily scrum meetings offer visibility and quick insights into the team's progress, along with constant feedback from clients and customers.", 'The three key artifacts of scrum - product backlog, sprint backlog, and product increment - are explained, highlighting their functions in improving transparency and understanding of the work and their respective roles in delivering the requirements of the stakeholders.', 'Active customer involvement in providing feedback on the working pieces is essential for fulfilling requirements and making necessary changes based on the feedback.']}, {'end': 2839.957, 'segs': [{'end': 1684.164, 'src': 'embed', 'start': 1654.695, 'weight': 0, 'content': [{'end': 1658.056, 'text': "That's why when we speak about DevOps, we keep speaking about CI-CD.", 'start': 1654.695, 'duration': 3.361}, {'end': 1664.559, 'text': 'In CI-CD, we speak about continuous integration, continuous delivery and continuous deployment.', 'start': 1658.176, 'duration': 6.383}, {'end': 1667.66, 'text': "So in continuous delivery, we're speaking about release basically.", 'start': 1664.599, 'duration': 3.061}, {'end': 1670.561, 'text': 'So once it is released, it becomes usable.', 'start': 1668.16, 'duration': 2.401}, {'end': 1675.403, 'text': 'So once it is deployed, it is available for user to use.', 'start': 1671.141, 'duration': 4.262}, {'end': 1679.102, 'text': "and that's about the scrum artifacts.", 'start': 1676.5, 'duration': 2.602}, {'end': 1684.164, 'text': 'now let us look at scrum framework, how that scrum framework looks like in entirety.', 'start': 1679.102, 'duration': 5.062}], 'summary': 'Devops emphasizes ci-cd for continuous integration, delivery, and deployment, ensuring usability and availability for users, while also involving scrum framework.', 'duration': 29.469, 'max_score': 1654.695, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw1654695.jpg'}, {'end': 1726.157, 'src': 'embed', 'start': 1698.992, 'weight': 1, 'content': [{'end': 1702.174, 'text': 'now, where do we see all of this when we look at the scrum framework?', 'start': 1698.992, 'duration': 3.182}, {'end': 1703.535, 'text': 'so that picture let us see.', 'start': 1702.174, 'duration': 1.361}, {'end': 1708.814, 'text': 'So, when we say scrum framework already we spoke about the product backlog.', 'start': 1704.873, 'duration': 3.941}, {'end': 1711.774, 'text': 'We can see that it is in the left side in the beginning.', 'start': 1709.514, 'duration': 2.26}, {'end': 1713.635, 'text': 'We have a sprint planning.', 'start': 1712.575, 'duration': 1.06}, {'end': 1716.295, 'text': 'So we spoke about sprint, the time box iterations.', 'start': 1713.735, 'duration': 2.56}, {'end': 1726.157, 'text': 'And from the product backlog, the items which is moving towards sprint, to a specific sprint, what needs to be delivered, which become sprint backlog.', 'start': 1716.955, 'duration': 9.202}], 'summary': 'The scrum framework involves product backlog, sprint planning, and sprint backlog.', 'duration': 27.165, 'max_score': 1698.992, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw1698992.jpg'}, {'end': 1808.443, 'src': 'embed', 'start': 1778.954, 'weight': 5, 'content': [{'end': 1779.595, 'text': 'what is required.', 'start': 1778.954, 'duration': 0.641}, {'end': 1788.817, 'text': 'so product backlog is the first step of scrum framework, is a set of list of tasks to have successfully achieve the goals of the stakeholders.', 'start': 1780.675, 'duration': 8.142}, {'end': 1791.738, 'text': "we'll discuss that while discussing on product backlog.", 'start': 1788.817, 'duration': 2.921}, {'end': 1802.421, 'text': 'so further sprint planning happens where the team determines the tasks from the product catalog they will work on and aim to deliver during the sprint.', 'start': 1791.738, 'duration': 10.683}, {'end': 1808.443, 'text': 'now this is negotiated, understood, agreed and then most towards sprint to get delivered.', 'start': 1802.421, 'duration': 6.022}], 'summary': 'Product backlog is the first step of scrum framework, consisting of tasks to achieve stakeholder goals; sprint planning involves determining tasks and aiming for delivery during the sprint.', 'duration': 29.489, 'max_score': 1778.954, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw1778954.jpg'}, {'end': 1858.331, 'src': 'embed', 'start': 1826.733, 'weight': 4, 'content': [{'end': 1832.177, 'text': 'now scrum team, the scrum team, which is actually self-organizing team, as we mentioned,', 'start': 1826.733, 'duration': 5.444}, {'end': 1837.801, 'text': 'maybe five to ten nine members of team working on the task in the sprint backlog,', 'start': 1832.177, 'duration': 5.624}, {'end': 1844.768, 'text': 'and they will also have a daily scrums where the team also discusses for 15 minutes on the events,', 'start': 1837.801, 'duration': 6.967}, {'end': 1850.47, 'text': 'where the team member synchronizes activities and plan what they aim to achieve in next 24 hours,', 'start': 1844.768, 'duration': 5.702}, {'end': 1858.331, 'text': 'what is accomplished against what is discussed in previous daily scrum and then, if at all any further discussions need to be done,', 'start': 1850.47, 'duration': 7.861}], 'summary': 'A self-organizing scrum team of 5-10 members holds daily 15-minute scrums to synchronize activities and plan for the next 24 hours.', 'duration': 31.598, 'max_score': 1826.733, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw1826733.jpg'}, {'end': 1903.209, 'src': 'embed', 'start': 1873.152, 'weight': 2, 'content': [{'end': 1878.213, 'text': 'Then the sprint review happens where, once the sprint is complete.', 'start': 1873.152, 'duration': 5.061}, {'end': 1881.354, 'text': 'so sprint review happens, which involves the team,', 'start': 1878.213, 'duration': 3.141}, {'end': 1888.256, 'text': 'the scrum master and product owner and stakeholders to understand what is being agreed upon and what is being delivered or reviewed.', 'start': 1881.354, 'duration': 6.902}, {'end': 1891.217, 'text': 'Is that fulfilled in the entirety? That is discussed.', 'start': 1888.816, 'duration': 2.401}, {'end': 1897.101, 'text': 'and then during this meeting, the team shows what they accomplished during the sprint.', 'start': 1891.974, 'duration': 5.127}, {'end': 1903.209, 'text': 'it allows time to ask questions, make observations, give feedback and provide suggestions.', 'start': 1897.101, 'duration': 6.108}], 'summary': 'Sprint review involves team, scrum master, and stakeholders to review accomplishments and gather feedback.', 'duration': 30.057, 'max_score': 1873.152, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw1873152.jpg'}, {'end': 1949.384, 'src': 'embed', 'start': 1919.305, 'weight': 3, 'content': [{'end': 1925.11, 'text': 'so the product owner has to speak with the stakeholders so that there is a good understanding, good handshake,', 'start': 1919.305, 'duration': 5.805}, {'end': 1930.094, 'text': 'that what needs to be delivered and what is the priority in the given list.', 'start': 1925.11, 'duration': 4.984}, {'end': 1932.456, 'text': 'then sprint retrospective happens.', 'start': 1930.094, 'duration': 2.362}, {'end': 1935.656, 'text': 'so after the sprint review, Sprint retrospective happens.', 'start': 1932.456, 'duration': 3.2}, {'end': 1942.18, 'text': 'So during this meeting, what went well, like past mistakes, potential issues?', 'start': 1936.196, 'duration': 5.984}, {'end': 1949.384, 'text': 'What are the new ways to handle them, which are required to be done correctly in the next? iterations or next prints needs to be identified,', 'start': 1942.18, 'duration': 7.204}], 'summary': 'Product owner communicates with stakeholders for clear understanding and prioritization. sprint retrospective assesses past performance and identifies improvements for next iterations.', 'duration': 30.079, 'max_score': 1919.305, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw1919305.jpg'}, {'end': 2029.407, 'src': 'embed', 'start': 2002.444, 'weight': 6, 'content': [{'end': 2006.287, 'text': 'So let us look at what is a scrum board which is used during the scrum practice.', 'start': 2002.444, 'duration': 3.843}, {'end': 2013.733, 'text': 'So scrum board is a physical or virtual tool that helps team to visualize items in the sprint backlog.', 'start': 2006.847, 'duration': 6.886}, {'end': 2019.117, 'text': 'So it helps in tracking what is being delivered, what is in progress and what needs to be delivered for the.', 'start': 2013.753, 'duration': 5.364}, {'end': 2029.407, 'text': 'so it shows all action items during the daily scrum, helping keeping the team focused on tasks that need to be completion and the priorities of those.', 'start': 2019.861, 'duration': 9.546}], 'summary': 'A scrum board visualizes sprint backlog items, tracks progress and priorities.', 'duration': 26.963, 'max_score': 2002.444, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw2002444.jpg'}, {'end': 2430.838, 'src': 'embed', 'start': 2399.874, 'weight': 8, 'content': [{'end': 2408.929, 'text': 'And the team says, well, the only thing is is that we have to do some development work before we can actually do user story two.', 'start': 2399.874, 'duration': 9.055}, {'end': 2418.573, 'text': 'And so what we really need to do is insert that before the second priority user story.', 'start': 2409.649, 'duration': 8.924}, {'end': 2424.615, 'text': 'And so the priority of the user stories in the product backlog.', 'start': 2419.333, 'duration': 5.282}, {'end': 2430.838, 'text': 'while it might start with just being simple, functional user stories coming from the product owner,', 'start': 2424.615, 'duration': 6.223}], 'summary': 'Development work needed before user story two, impacting product backlog priorities.', 'duration': 30.964, 'max_score': 2399.874, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw2399874.jpg'}, {'end': 2641.687, 'src': 'embed', 'start': 2612.409, 'weight': 7, 'content': [{'end': 2618.412, 'text': 'that might be multiple user stories in order to support that use case.', 'start': 2612.409, 'duration': 6.003}, {'end': 2620.093, 'text': 'And so, of course,', 'start': 2618.912, 'duration': 1.181}, {'end': 2628.098, 'text': 'we would want to be able to connect the dots and see where all the user stories fit in into the overall goal of the project or release.', 'start': 2621.274, 'duration': 6.824}, {'end': 2641.687, 'text': 'And the stories are grouped to form an epic or higher level story, so epic or theme.', 'start': 2628.919, 'duration': 12.768}], 'summary': 'Multiple user stories are grouped into epics or themes to support use cases and project goals.', 'duration': 29.278, 'max_score': 2612.409, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw2612409.jpg'}, {'end': 2719.367, 'src': 'embed', 'start': 2686.158, 'weight': 9, 'content': [{'end': 2691.319, 'text': 'Well a user story has to be small enough to be completed within a single sprint.', 'start': 2686.158, 'duration': 5.161}, {'end': 2697.481, 'text': 'So a sprint can contain more than one user story but a user story cannot span sprints.', 'start': 2692.299, 'duration': 5.182}, {'end': 2704.679, 'text': 'So that feature or function that was in the question was probably more like an epic.', 'start': 2698.221, 'duration': 6.458}, {'end': 2710.882, 'text': 'It was something that would need to be disaggregated into smaller user stories,', 'start': 2704.759, 'duration': 6.123}, {'end': 2719.367, 'text': 'or perhaps it was more of a use case that would need more than one user story in order to actually deliver the overall use case.', 'start': 2710.882, 'duration': 8.485}], 'summary': 'User stories should be small enough to complete in a single sprint, while larger features may need to be disaggregated into smaller stories or use cases.', 'duration': 33.209, 'max_score': 2686.158, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw2686158.jpg'}], 'start': 1654.695, 'title': 'Devops, scrum, and agile planning', 'summary': 'Provides an overview of devops and the scrum framework, emphasizing the significance of ci-cd, and detailing the key elements of the scrum framework. it also discusses user stories in agile planning, covering themes, epics, prioritization, estimation, and practical aspects.', 'chapters': [{'end': 1778.954, 'start': 1654.695, 'title': 'Devops and scrum framework overview', 'summary': 'Discusses the significance of ci-cd in devops, emphasizing continuous integration, delivery, and deployment. it also provides insights into the components and flow of the scrum framework, including the product backlog, sprint planning, sprint backlog, daily scrum meetings, sprint review, and retrospective.', 'duration': 124.259, 'highlights': ['The significance of CI-CD in DevOps, emphasizing continuous integration, delivery, and deployment. The chapter emphasizes the importance of CI-CD in DevOps, focusing on continuous integration, continuous delivery, and continuous deployment.', 'Insights into the components and flow of the scrum framework, including the product backlog, sprint planning, sprint backlog, daily scrum meetings, sprint review, and retrospective. The transcript provides insights into the components and flow of the scrum framework, covering the product backlog, sprint planning, sprint backlog, daily scrum meetings, sprint review, and retrospective.']}, {'end': 2093.217, 'start': 1778.954, 'title': 'Scrum framework overview', 'summary': 'Provides an overview of the scrum framework, detailing the key elements such as product backlog, sprint planning, daily scrums, sprint review, sprint retrospective, increment, and scrum board.', 'duration': 314.263, 'highlights': ['The sprint review involves the team, scrum master, product owner, and stakeholders to understand and review the deliverables, with a focus on what was agreed upon and what was accomplished.', 'The sprint retrospective is a meeting to identify past mistakes, potential issues, and new ways to handle them, incorporating the lessons learned when planning the new sprint.', 'The daily scrums are 15-minute events where team members synchronize activities, discuss what they aim to achieve in the next 24 hours, and review what was accomplished against previous discussions.', "The product backlog is the first step of the Scrum framework, comprising a set list of tasks to successfully achieve the stakeholders' goals, and is further discussed during sprint planning.", 'The scrum board, a visual tool used during the Scrum practice, helps the team visualize items in the sprint backlog, track progress, and maintain focus on tasks and priorities.']}, {'end': 2839.957, 'start': 2094.177, 'title': 'User stories and agile planning', 'summary': 'Discusses the concept of themes, epics, and user stories in agile planning, emphasizing the hierarchy, prioritization, estimation, and breakdown of user stories, as well as the significance of investing in user stories and the practical aspects of taking the exam.', 'duration': 745.78, 'highlights': ['The chapter explains the concept of themes, epics, and user stories, emphasizing that themes group together epics and user stories for planning purposes, with epics being large, low-priority user stories that eventually need to be disaggregated into smaller user stories.', 'It highlights the significance of prioritizing user stories in the product backlog, which evolves to include various considerations such as successor relationships, dependencies, and non-functional requirements, impacting the planning and prioritization process.', 'The chapter emphasizes the need for user stories to be small enough to be completed within a single sprint, with the recommendation to invest in understanding and memorizing the concepts and practical aspects for agile planning and exam preparation.', 'The section provides practical advice for exam preparation, suggesting the importance of being able to write out the concepts within a limited time frame and discussing alternative options for taking the exam, such as paper-based or proctored tests, and the use of monitoring software for online exams.']}], 'duration': 1185.262, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw1654695.jpg', 'highlights': ['The significance of CI-CD in DevOps, focusing on continuous integration, delivery, and deployment', 'Insights into the components and flow of the scrum framework, covering product backlog, sprint planning, and more', 'The sprint review involves the team, scrum master, product owner, and stakeholders to review deliverables', 'The sprint retrospective identifies past mistakes and new ways to handle them for planning the new sprint', "The daily scrums synchronize activities, discuss next 24 hours' goals, and review accomplishments", "The product backlog comprises a set list of tasks to achieve stakeholders' goals", 'The scrum board helps visualize sprint backlog items, track progress, and maintain focus', 'Themes group together epics and user stories for planning purposes', 'The significance of prioritizing user stories in the product backlog, considering various dependencies', 'User stories need to be small enough to be completed within a single sprint']}, {'end': 4008.168, 'segs': [{'end': 2922.554, 'src': 'embed', 'start': 2865.642, 'weight': 0, 'content': [{'end': 2869.544, 'text': "and I had it memorized well enough that I could kind of recall it in my mind's eye.", 'start': 2865.642, 'duration': 3.902}, {'end': 2877.703, 'text': "Okay, so we're talking about user stories and you have to invest in your user stories.", 'start': 2870.64, 'duration': 7.063}, {'end': 2878.604, 'text': 'You know,', 'start': 2878.204, 'duration': 0.4}, {'end': 2889.969, 'text': "I like memorizing things by creating these charts that have the first letter of the word or phrase that you're memorizing in a separate column,", 'start': 2878.604, 'duration': 11.365}, {'end': 2892.29, 'text': 'and then I make up a story.', 'start': 2889.969, 'duration': 2.321}, {'end': 2897.885, 'text': "you know that reminds me that I've got to have I-N-V-E-S-T.", 'start': 2892.29, 'duration': 5.595}, {'end': 2901.867, 'text': 'This one is pretty easy, probably just invest works.', 'start': 2898.185, 'duration': 3.682}, {'end': 2904.588, 'text': "So let's go over that.", 'start': 2903.587, 'duration': 1.001}, {'end': 2906.968, 'text': 'I stands for independent.', 'start': 2904.968, 'duration': 2}, {'end': 2913.391, 'text': 'Independent meaning that each user story stands on its own.', 'start': 2908.829, 'duration': 4.562}, {'end': 2922.554, 'text': "You don't have, when we're doing Scrum, you don't do a user story that won't result in working software.", 'start': 2914.571, 'duration': 7.983}], 'summary': 'Invest in user stories: i-n-v-e-s-t - independent, negotiable, valuable, estimable, small, testable', 'duration': 56.912, 'max_score': 2865.642, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw2865642.jpg'}, {'end': 3114.57, 'src': 'embed', 'start': 3074.207, 'weight': 2, 'content': [{'end': 3078.469, 'text': "And so let's add that to our list of things to memorize.", 'start': 3074.207, 'duration': 4.262}, {'end': 3087.594, 'text': 'Invest And then the next one we have here is the three Cs of a user story.', 'start': 3079.549, 'duration': 8.045}, {'end': 3091.656, 'text': 'So the first C team is card.', 'start': 3089.094, 'duration': 2.562}, {'end': 3094.137, 'text': 'So user stories.', 'start': 3093.016, 'duration': 1.121}, {'end': 3106.884, 'text': 'should be able to be written on a four by six inch index card or some media similar to that card.', 'start': 3094.975, 'duration': 11.909}, {'end': 3114.57, 'text': 'The second C is conversation.', 'start': 3111.607, 'duration': 2.963}], 'summary': 'Remember to memorize, 3 cs of user story: card, conversation.', 'duration': 40.363, 'max_score': 3074.207, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw3074207.jpg'}, {'end': 3282.72, 'src': 'embed', 'start': 3248.719, 'weight': 3, 'content': [{'end': 3252.34, 'text': 'And then there would be acceptance criteria or tests.', 'start': 3248.719, 'duration': 3.621}, {'end': 3258.082, 'text': 'Sometimes these get included on the back of the card, but the point is that they are on the card.', 'start': 3252.84, 'duration': 5.242}, {'end': 3263.772, 'text': 'Then there will be an estimate of size.', 'start': 3260.191, 'duration': 3.581}, {'end': 3268.294, 'text': 'It could be ideal days or story points.', 'start': 3264.773, 'duration': 3.521}, {'end': 3271.856, 'text': 'As I mentioned, most teams do story points.', 'start': 3268.534, 'duration': 3.322}, {'end': 3282.72, 'text': "That's more likely what you'll be tested on as opposed to ideal days, but we'll cover both so you understand the differences.", 'start': 3272.376, 'duration': 10.344}], 'summary': 'Transcript covers acceptance criteria, estimates of size (ideal days or story points), and differences between them.', 'duration': 34.001, 'max_score': 3248.719, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw3248719.jpg'}, {'end': 3683.205, 'src': 'embed', 'start': 3656.109, 'weight': 4, 'content': [{'end': 3663.473, 'text': 'Now, when it comes to determining value for user stories, this is primarily owned by the product owner, right?', 'start': 3656.109, 'duration': 7.364}, {'end': 3666.735, 'text': 'And it always comes back to money.', 'start': 3664.434, 'duration': 2.301}, {'end': 3672.058, 'text': 'but money, you know, the value can be looked at from different points of view.', 'start': 3666.735, 'duration': 5.323}, {'end': 3677.702, 'text': 'So new revenue, obviously, you know, getting new customers and having them buy stuff.', 'start': 3672.819, 'duration': 4.883}, {'end': 3683.205, 'text': "Well, below that, there's another consideration, incremental revenue.", 'start': 3679.423, 'duration': 3.782}], 'summary': 'Product owner determines user story value, focusing on revenue and new customers.', 'duration': 27.096, 'max_score': 3656.109, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw3656109.jpg'}, {'end': 3777.643, 'src': 'embed', 'start': 3744.547, 'weight': 5, 'content': [{'end': 3753.551, 'text': 'recognizing that there are some priority concerns that come from both the customer domain as well as the technical domain.', 'start': 3744.547, 'duration': 9.004}, {'end': 3759.954, 'text': 'And there are some prioritization models.', 'start': 3756.853, 'duration': 3.101}, {'end': 3771.381, 'text': 'If we look right here, there is value-based prioritization, and the hierarchy of that would be high value followed by high risk,', 'start': 3760.814, 'duration': 10.567}, {'end': 3777.643, 'text': 'followed by high value, and then low risk followed by low value and then low risk.', 'start': 3771.381, 'duration': 6.262}], 'summary': 'Priority concerns from customer and technical domains, using value-based prioritization model with high and low value and risk.', 'duration': 33.096, 'max_score': 3744.547, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw3744547.jpg'}, {'end': 3836.851, 'src': 'embed', 'start': 3800.001, 'weight': 6, 'content': [{'end': 3807.683, 'text': "And so you'd probably want to persuade the product owner to take care of high-risk stuff first,", 'start': 3800.001, 'duration': 7.682}, {'end': 3816.826, 'text': 'because that would have an impact on the future things that need to be done.', 'start': 3807.683, 'duration': 9.143}, {'end': 3830.409, 'text': "There's the CATO model, which looks at each of the user stories and classifies them as being mandatory, linear, or exciters.", 'start': 3818.447, 'duration': 11.962}, {'end': 3836.851, 'text': 'And the mandatory items are those user stories that are musts.', 'start': 3831.87, 'duration': 4.981}], 'summary': 'Persuade product owner to prioritize high-risk items for impact on future tasks.', 'duration': 36.85, 'max_score': 3800.001, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw3800001.jpg'}], 'start': 2840.629, 'title': 'User story essentials', 'summary': 'Covers the importance of memorizing user stories, emphasizing the invest criteria and the three cs, essential components of a user story card, and user story estimation in a scrum project, including value-based prioritization and different models for prioritizing user stories based on impact and value.', 'chapters': [{'end': 3248.059, 'start': 2840.629, 'title': 'Memorizing user stories and three cs', 'summary': 'Discusses the importance of memorizing user stories, emphasizing the invest criteria and the three cs of a user story, which includes creating valuable, estimable, small, testable, and negotiable user stories, as well as the three cs - card, conversation, and confirmation.', 'duration': 407.43, 'highlights': ['The INVEST criteria for user stories, including independent, negotiable, valuable, estimable, small, and testable aspects, ensuring that each user story stands on its own and creates value for the customer or end user. The INVEST criteria emphasizes the importance of user stories being independent, negotiable, valuable, estimable, small, and testable, ensuring that they create value for the customer or end user.', 'The importance of memorizing user stories, using mnemonic devices and charts to recall the key aspects, such as the INVEST criteria and the three Cs of a user story. Emphasizing the significance of memorizing user stories using mnemonic devices and charts to recall key aspects like the INVEST criteria and the three Cs of a user story.', 'The three Cs of a user story - card, conversation, and confirmation, emphasizing the use of a four by six inch index card for writing user stories, engaging in conversations between the team and the product owner, and including acceptance tests for confirmation. Explaining the three Cs of a user story - card, conversation, and confirmation, highlighting the use of a four by six inch index card, engaging in conversations, and including acceptance tests for confirmation.']}, {'end': 3592.906, 'start': 3248.719, 'title': 'User story card essentials', 'summary': 'Explains the essential components of a user story card, including acceptance criteria, estimation methods, value points assignment, indication of story origin, and methods for handling large user stories, with emphasis on the process of subdivision.', 'duration': 344.187, 'highlights': ['User story card components like acceptance criteria, estimation methods, value points assignment, story origin indication, and handling large user stories are explained. The chapter provides an explanation of the essential components of a user story card, including acceptance criteria, estimation methods, value points assignment, indication of story origin, and methods for handling large user stories.', 'Estimation methods such as ideal days or story points are discussed, with emphasis on the prevalence of story points in most teams. The chapter discusses estimation methods, highlighting the prevalence of story points over ideal days in most teams.', 'The process of subdividing large user stories is detailed, with three proposed approaches based on operational boundaries, exceptions, and cross-cutting concerns. The chapter details the process of subdividing large user stories, proposing three approaches based on operational boundaries, exceptions, and cross-cutting concerns.']}, {'end': 4008.168, 'start': 3593.546, 'title': 'User story estimation and prioritization', 'summary': "Discusses user story estimation in a scrum project, emphasizing the need for value-based prioritization and different models like cato, kano, wieger's relative weighting, and moscow for prioritizing user stories based on their impact and value.", 'duration': 414.622, 'highlights': ['Value-based prioritization is primarily owned by the product owner, focusing on new revenue, incremental revenue, retained value, and operational efficiency. Product owner owns value-based prioritization, focusing on new revenue, incremental revenue, retained value, and operational efficiency.', "Different prioritization models like CATO, Kano, Wieger's relative weighting, and Moscow are discussed, emphasizing the importance of classifying user stories into mandatory, linear, and exciters for effective prioritization. Different prioritization models like CATO, Kano, Wieger's relative weighting, and Moscow are discussed, emphasizing the classification of user stories into mandatory, linear, and exciters.", "The CATO model classifies user stories into mandatory, linear, and exciters, while Wieger's method uses numbers to calculate the benefit, penalty, cost, and risk to determine the priority of user stories. The CATO model classifies user stories into mandatory, linear, and exciters, while Wieger's method uses numbers to calculate the benefit, penalty, cost, and risk for prioritization.", "The Moscow prioritization model categorizes user stories into must, should, could, and won't, providing a framework for prioritizing user stories based on their importance and impact. The Moscow prioritization model categorizes user stories into must, should, could, and won't, providing a framework for prioritizing user stories based on their importance and impact."]}], 'duration': 1167.539, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw2840629.jpg', 'highlights': ['The INVEST criteria for user stories, ensuring value creation and independence.', 'The importance of memorizing user stories using mnemonic devices and charts.', 'The three Cs of a user story - card, conversation, and confirmation.', 'Estimation methods, emphasizing the prevalence of story points in most teams.', 'Value-based prioritization focusing on new revenue, incremental revenue, retained value, and operational efficiency.', "Different prioritization models like CATO, Kano, Wieger's relative weighting, and Moscow.", "The Moscow prioritization model categorizes user stories into must, should, could, and won't."]}, {'end': 5181.368, 'segs': [{'end': 4051.57, 'src': 'embed', 'start': 4009.149, 'weight': 0, 'content': [{'end': 4011.21, 'text': "Okay, so now let's talk about velocity.", 'start': 4009.149, 'duration': 2.061}, {'end': 4014.933, 'text': 'Priyanka, that is exactly right.', 'start': 4013.312, 'duration': 1.621}, {'end': 4029.453, 'text': 'So velocity is the capacity of the team to complete work in a single iteration.', 'start': 4018.896, 'duration': 10.557}, {'end': 4040.041, 'text': 'So the team has estimated the user stories for size or ideal days.', 'start': 4034.377, 'duration': 5.664}, {'end': 4045.866, 'text': 'And the sprints are going to be three weeks in duration.', 'start': 4040.902, 'duration': 4.964}, {'end': 4051.57, 'text': 'Obviously, not all user stories can be completed in a single sprint and be done with the project.', 'start': 4046.506, 'duration': 5.064}], 'summary': "Velocity measures team's capacity to complete work in a 3-week sprint.", 'duration': 42.421, 'max_score': 4009.149, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw4009149.jpg'}, {'end': 4141.069, 'src': 'embed', 'start': 4103.468, 'weight': 1, 'content': [{'end': 4124.305, 'text': 'If we look over to box number two here Velocity is used to deal with determining how many user stories we are going to include in a given sprint and also how many sprints are we going to need to create a release or a set of user stories.', 'start': 4103.468, 'duration': 20.837}, {'end': 4126.345, 'text': "And here's an example.", 'start': 4125.245, 'duration': 1.1}, {'end': 4141.069, 'text': 'In box number three, a team completed five user stories that were sized five, three, eight, 13 and 2.', 'start': 4129.126, 'duration': 11.943}], 'summary': 'Velocity determines sprint capacity and release planning. example: team completed 5 user stories of varying sizes.', 'duration': 37.601, 'max_score': 4103.468, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw4103468.jpg'}, {'end': 4348.921, 'src': 'embed', 'start': 4319.598, 'weight': 2, 'content': [{'end': 4327.564, 'text': 'And then the sprints are populated by the individual user stories, which are then disaggregated into tasks.', 'start': 4319.598, 'duration': 7.966}, {'end': 4336.772, 'text': 'And we do the daily scrum, which is the daily level of planning and coordination.', 'start': 4328.725, 'duration': 8.047}, {'end': 4339.231, 'text': 'So we call that the planning onion.', 'start': 4337.369, 'duration': 1.862}, {'end': 4346.959, 'text': 'We already kind of talked about the release and roadmap, um, concept here.', 'start': 4341.553, 'duration': 5.406}, {'end': 4348.921, 'text': "So let's just review this quickly.", 'start': 4347.419, 'duration': 1.502}], 'summary': 'Sprints populated with user stories, disaggregated into tasks. daily scrum for planning and coordination. review of release and roadmap concept.', 'duration': 29.323, 'max_score': 4319.598, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw4319598.jpg'}, {'end': 4398.347, 'src': 'embed', 'start': 4369.009, 'weight': 3, 'content': [{'end': 4372.031, 'text': 'For each release, you want to estimate the target stories.', 'start': 4369.009, 'duration': 3.022}, {'end': 4376.856, 'text': 'Repeat until the target stories are assigned an iteration length.', 'start': 4373.112, 'duration': 3.744}, {'end': 4383.341, 'text': "It's blending some things here.", 'start': 4381.94, 'duration': 1.401}, {'end': 4388.486, 'text': 'Be able to estimate velocity and then assign stories to the sprints.', 'start': 4384.202, 'duration': 4.284}, {'end': 4395.285, 'text': 'So we keep estimating the user stories and we keep organizing that until we can do that.', 'start': 4389.201, 'duration': 6.084}, {'end': 4398.347, 'text': 'We can come up with an iteration length, a sprint length,', 'start': 4395.345, 'duration': 3.002}], 'summary': 'Estimate target stories for releases and assign iteration length to achieve sprint goals.', 'duration': 29.338, 'max_score': 4369.009, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw4369009.jpg'}, {'end': 4565.569, 'src': 'embed', 'start': 4534.99, 'weight': 4, 'content': [{'end': 4544.296, 'text': 'Understand the cone of uncertainty, which is an estimate or best guess to begin with, and then progressively becomes more accurate.', 'start': 4534.99, 'duration': 9.306}, {'end': 4548.459, 'text': "In fact, let's just take a break and look at the cone of uncertainty.", 'start': 4544.937, 'duration': 3.522}, {'end': 4553.622, 'text': "So at the very beginning of a project, there's going to be a high level of uncertainty.", 'start': 4549.179, 'duration': 4.443}, {'end': 4560.567, 'text': 'If I were to draw this chart, I would make it a little bit more like.', 'start': 4555.023, 'duration': 5.544}, {'end': 4565.569, 'text': 'this so clearly.', 'start': 4562.948, 'duration': 2.621}], 'summary': 'The cone of uncertainty starts with high uncertainty and progressively becomes more accurate.', 'duration': 30.579, 'max_score': 4534.99, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw4534990.jpg'}, {'end': 4685.85, 'src': 'embed', 'start': 4656.775, 'weight': 5, 'content': [{'end': 4663.018, 'text': 'then that would be discussed during the retrospective and then we would do something different going forward,', 'start': 4656.775, 'duration': 6.243}, {'end': 4665.099, 'text': 'which might include doing some re-estimating.', 'start': 4663.018, 'duration': 2.081}, {'end': 4670.739, 'text': 'Scrum estimating is not necessarily more difficult.', 'start': 4667.597, 'duration': 3.142}, {'end': 4674.602, 'text': 'However, Scrum exposes bad estimates sooner, which is a good thing.', 'start': 4670.819, 'duration': 3.783}, {'end': 4685.85, 'text': "When we were doing our planning poker, you could see that the first time as a team, you know, we didn't know each other.", 'start': 4675.142, 'duration': 10.708}], 'summary': 'Scrum exposes bad estimates sooner, leading to improved planning and re-estimation.', 'duration': 29.075, 'max_score': 4656.775, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw4656775.jpg'}, {'end': 4752.105, 'src': 'embed', 'start': 4717.385, 'weight': 6, 'content': [{'end': 4728.317, 'text': "Let's see, is there a question here? Can velocity be increased over a period of time for the project? Yes, it can.", 'start': 4717.385, 'duration': 10.932}, {'end': 4730.458, 'text': "Now, it's not that it can't.", 'start': 4728.798, 'duration': 1.66}, {'end': 4735.34, 'text': 'It will increase if the team is learning how to work together better and better.', 'start': 4730.858, 'duration': 4.482}, {'end': 4749.084, 'text': 'You would expect that, if I can just use my mouse here, if we were tracking velocity, so this would be points completed over here.', 'start': 4735.94, 'duration': 13.144}, {'end': 4752.105, 'text': 'Let me just do PTS for points.', 'start': 4750.185, 'duration': 1.92}], 'summary': 'Velocity can increase over time as team learns to work together better, leading to more points completed.', 'duration': 34.72, 'max_score': 4717.385, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw4717385.jpg'}, {'end': 4879.6, 'src': 'embed', 'start': 4838.482, 'weight': 7, 'content': [{'end': 4843.486, 'text': 'When we do estimating for tasks, we do it in ideal time, which means hours.', 'start': 4838.482, 'duration': 5.004}, {'end': 4846.35, 'text': "I think that's on the whiteboard or it was on the whiteboard.", 'start': 4844.028, 'duration': 2.322}, {'end': 4847.55, 'text': 'Oh, it was on it.', 'start': 4846.37, 'duration': 1.18}, {'end': 4856.376, 'text': 'So, ideal time is the amount of time it takes to complete a piece of work.', 'start': 4849.492, 'duration': 6.884}, {'end': 4879.6, 'text': "But that's based on the notion that the team member or members are available to do just the work with no distractions or anything at all.", 'start': 4863.261, 'duration': 16.339}], 'summary': 'Estimating tasks in ideal time, based on hours, without distractions.', 'duration': 41.118, 'max_score': 4838.482, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw4838482.jpg'}, {'end': 5083.585, 'src': 'embed', 'start': 5054.229, 'weight': 9, 'content': [{'end': 5063.817, 'text': "For example, when we did our planning project this morning, or this morning for me, rather, at the beginning, Oh, that's not it.", 'start': 5054.229, 'duration': 9.588}, {'end': 5065.858, 'text': 'That is the daily stand-up.', 'start': 5064.137, 'duration': 1.721}, {'end': 5067.218, 'text': 'Here it is.', 'start': 5066.798, 'duration': 0.42}, {'end': 5076.302, 'text': 'If I had said, team, I want you to pick a small user story, a medium user story, and a large user story.', 'start': 5069.259, 'duration': 7.043}, {'end': 5083.585, 'text': 'And then we would then compare other stories to those three, and so we would kind of triangulate on it.', 'start': 5077.822, 'duration': 5.763}], 'summary': 'During the planning project, the team selected small, medium, and large user stories for comparison and triangulation.', 'duration': 29.356, 'max_score': 5054.229, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw5054229.jpg'}, {'end': 5148.445, 'src': 'embed', 'start': 5113.421, 'weight': 8, 'content': [{'end': 5121.106, 'text': "And so let's say, you know, we had apples at five and grapes at two, then we would say an orange is probably going to be three.", 'start': 5113.421, 'duration': 7.685}, {'end': 5132.3, 'text': 'And the values, you know, now I used in our example the modified Fibonacci series.', 'start': 5125.798, 'duration': 6.502}, {'end': 5142.123, 'text': "What we do in Scrum and Agile, if we're using story points, we're going to use a non-linear scale for the values.", 'start': 5133.3, 'duration': 8.823}, {'end': 5148.445, 'text': "So down at the bottom here, there's the modified Fibonacci sequence.", 'start': 5142.583, 'duration': 5.862}], 'summary': 'Using a non-linear scale for values in scrum and agile, based on modified fibonacci sequence.', 'duration': 35.024, 'max_score': 5113.421, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw5113421.jpg'}], 'start': 4009.149, 'title': 'Agile velocity and planning onion', 'summary': "Explains the concept of velocity in agile methodology, emphasizing its role in determining the team's capacity to complete work in a given sprint. it also delves into release planning, estimation, and the use of story points for effort estimation in scrum and agile projects.", 'chapters': [{'end': 4367.868, 'start': 4009.149, 'title': 'Understanding velocity and planning onion', 'summary': "Explains the concept of velocity in agile methodology, emphasizing its role in determining the team's capacity to complete work in a given sprint. it also delves into the planning onion, outlining the hierarchical levels of planning in agile project management.", 'duration': 358.719, 'highlights': ["Velocity is the team's capacity to complete work in a given sprint and is calculated as an observation based on the average of previous sprints, disregarding any outliers. Velocity is an observation-based metric representing the team's ability to complete work in a given sprint, calculated as an average of previous sprints, with outliers disregarded.", 'Velocity is used to determine how many user stories to include in a sprint and how many sprints are needed to create a release or set of user stories. Velocity plays a crucial role in deciding the number of user stories to include in a sprint and the overall sprints required for creating a release or set of user stories.', 'The planning onion encompasses vision level, product roadmap, releases, and sprints, with each level serving specific planning and coordination purposes. The planning onion framework includes hierarchical levels such as vision, product roadmap, releases, and sprints, each serving distinct planning and coordination functions within agile project management.']}, {'end': 4807.597, 'start': 4369.009, 'title': 'Release planning and estimation in scrum', 'summary': 'Discusses release planning, including estimating target stories, iteration length, and velocity, and it emphasizes the importance of iterative planning and addressing overestimation and underestimation in scrum. it also covers the principles behind estimation and how velocity can increase over time in a project.', 'duration': 438.588, 'highlights': ['The chapter discusses the importance of iterative planning, including estimating target stories, iteration length, and velocity, and emphasizes the need to iterate until user stories and release date meet conditions of satisfaction. It covers the iterative process of estimating target stories, iteration length, and velocity, and emphasizes the need to iterate until user stories and release date meet conditions of satisfaction.', "It also covers the principles behind estimation, including understanding the cone of uncertainty and the only estimate that matters being the one given by the team, supported by the comment that 'nothing is impossible for the one who doesn't have to do it,' highlighting the importance of team input in estimation. It explains the principles behind estimation, including understanding the cone of uncertainty and the importance of the estimate given by the team. It also emphasizes the importance of team input in estimation.", 'The chapter discusses overestimation and underestimation as common issues in Scrum, with a focus on identifying underestimation through velocity and addressing it during retrospectives, potentially leading to re-estimation, and highlights that Scrum exposes bad estimates sooner. It addresses overestimation and underestimation as common issues in Scrum, focusing on identifying underestimation through velocity, addressing it during retrospectives, and potentially leading to re-estimation. It also emphasizes that Scrum exposes bad estimates sooner.', 'It explains how velocity can increase over time in a project as the team learns to work together better, leading to a steep learning curve in the initial sprints, followed by a flattening out and a slow rise as the team becomes a high-performing team, emphasizing the improvement in cross-functional behavior and accuracy of estimates. It explains how velocity can increase over time in a project as the team learns to work together better, leading to a steep learning curve in the initial sprints, followed by a flattening out and a slow rise as the team becomes a high-performing team. It emphasizes the improvement in cross-functional behavior and accuracy of estimates.']}, {'end': 5181.368, 'start': 4808.257, 'title': 'Scrum and agile: ideal time and story points', 'summary': 'Discusses the concept of ideal time and elapsed time in scrum and agile, emphasizing the conversion of ideal time into elapsed time at the task level, and the use of story points for effort estimation using a modified fibonacci sequence.', 'duration': 373.111, 'highlights': ["Ideal time is the amount of time it takes to complete a piece of work without any distractions, but it needs to be converted into elapsed time to account for distractions, with team members' average availability used for the conversion. Ideal time is the duration of uninterrupted work, and it needs to be converted into elapsed time by considering team members' average availability to account for distractions, ensuring more accurate time estimates.", 'Story points in Scrum and Agile are utilized for effort estimation, utilizing a non-linear scale based on a modified Fibonacci sequence, with values determined relative to each other to reflect the size and effort required for different user stories. Story points are used for relative effort estimation, employing a non-linear scale based on a modified Fibonacci sequence to assign values to user stories, allowing for a more flexible and accurate estimation of effort and size.', 'Comparing user stories to a baseline and triangulating between different-sized stories enables the assignment of story point values, providing a method for estimating the effort and size of user stories in relation to each other. Comparing user stories to a baseline and triangulating between different-sized stories allows for the assignment of story point values, enabling a method for estimating the effort and size of user stories in relation to each other, facilitating better planning and prioritization.']}], 'duration': 1172.219, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw4009149.jpg', 'highlights': ["Velocity is the team's capacity to complete work in a given sprint, calculated as an average of previous sprints, disregarding outliers.", 'Velocity plays a crucial role in deciding the number of user stories to include in a sprint and the overall sprints required for creating a release or set of user stories.', 'The planning onion framework includes hierarchical levels such as vision, product roadmap, releases, and sprints, each serving distinct planning and coordination functions within agile project management.', 'The chapter discusses the importance of iterative planning, including estimating target stories, iteration length, and velocity, and emphasizes the need to iterate until user stories and release date meet conditions of satisfaction.', 'It explains the principles behind estimation, including understanding the cone of uncertainty and the importance of the estimate given by the team. It also emphasizes the importance of team input in estimation.', 'Scrum exposes bad estimates sooner, addressing underestimation through velocity, potentially leading to re-estimation during retrospectives.', 'Velocity can increase over time in a project as the team learns to work together better, leading to a steep learning curve in the initial sprints, followed by a flattening out and a slow rise as the team becomes a high-performing team.', "Ideal time is the duration of uninterrupted work, converted into elapsed time by considering team members' average availability to account for distractions, ensuring more accurate time estimates.", 'Story points are used for relative effort estimation, employing a non-linear scale based on a modified Fibonacci sequence to assign values to user stories, allowing for a more flexible and accurate estimation of effort and size.', 'Comparing user stories to a baseline and triangulating between different-sized stories allows for the assignment of story point values, enabling a method for estimating the effort and size of user stories in relation to each other, facilitating better planning and prioritization.']}, {'end': 6746.782, 'segs': [{'end': 5282.019, 'src': 'embed', 'start': 5256.638, 'weight': 4, 'content': [{'end': 5261.402, 'text': "you're typically available to be doing your project work, five out of those eight hours.", 'start': 5256.638, 'duration': 4.764}, {'end': 5271.916, 'text': 'So when we are converting ideal time to elapsed time, You know, we will be building in extra time based on distractions and interruptions.', 'start': 5262.263, 'duration': 9.653}, {'end': 5275.257, 'text': "We would not call it a buffer, but that's essentially what we're doing.", 'start': 5271.976, 'duration': 3.281}, {'end': 5282.019, 'text': "Now, when it comes to user stories that we're using story points, it is different.", 'start': 5275.857, 'duration': 6.162}], 'summary': 'Project work available 5 out of 8 hours, extra time for distractions, different for user stories', 'duration': 25.381, 'max_score': 5256.638, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw5256638.jpg'}, {'end': 5505.913, 'src': 'embed', 'start': 5477.046, 'weight': 1, 'content': [{'end': 5484.132, 'text': 'if there were outliers, they were discussed and the reasons for that, those variances,', 'start': 5477.046, 'duration': 7.086}, {'end': 5489.607, 'text': 'those outliers were then part of the discussion and then we did another round of voting.', 'start': 5484.132, 'duration': 5.475}, {'end': 5495.99, 'text': 'And we would keep doing that until we had our estimates converge or we reached consensus on them.', 'start': 5490.288, 'duration': 5.702}, {'end': 5501.652, 'text': 'Okay, so advantages of planning poker.', 'start': 5498.731, 'duration': 2.921}, {'end': 5505.913, 'text': "it's fun, it's quick, it gets the whole team involved.", 'start': 5501.652, 'duration': 4.261}], 'summary': 'Using planning poker helped the team converge estimates through discussion and multiple rounds of voting, involving the entire team.', 'duration': 28.867, 'max_score': 5477.046, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw5477046.jpg'}, {'end': 6442.33, 'src': 'embed', 'start': 6420.115, 'weight': 3, 'content': [{'end': 6428.941, 'text': "It's attended by the team, the product owner and the scrum master, and there are two approaches to deciding what's going to be included in the sprint.", 'start': 6420.115, 'duration': 8.826}, {'end': 6435.144, 'text': 'It can be based on commitment and it can also be based on velocity.', 'start': 6429.68, 'duration': 5.464}, {'end': 6442.33, 'text': 'And the goal here is to get team buy-in.', 'start': 6437.406, 'duration': 4.924}], 'summary': 'Sprint planning involves team, product owner, scrum master, and two approaches: commitment and velocity to achieve team buy-in.', 'duration': 22.215, 'max_score': 6420.115, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw6420115.jpg'}, {'end': 6507.025, 'src': 'embed', 'start': 6481.785, 'weight': 0, 'content': [{'end': 6490.443, 'text': "and it might be what would the scrum master do if you had a dominant product owner that's trying to persuade the team to do more than the team thinks it can do?", 'start': 6481.785, 'duration': 8.658}, {'end': 6495.023, 'text': "And that's where the scrum master comes in.", 'start': 6493.302, 'duration': 1.721}, {'end': 6504.345, 'text': 'The scrum master plays the role of the mentor, the coach, and assisting in the resolution of those kinds of issues without deciding.', 'start': 6495.123, 'duration': 9.222}, {'end': 6507.025, 'text': 'The scrum master is not a decider.', 'start': 6504.805, 'duration': 2.22}], 'summary': 'The scrum master mentors and coaches, resolving issues without deciding.', 'duration': 25.24, 'max_score': 6481.785, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw6481785.jpg'}, {'end': 6632.625, 'src': 'embed', 'start': 6603.096, 'weight': 2, 'content': [{'end': 6609.282, 'text': 'So if you did a four-week sprint, you would plan on the review being a maximum of four hours in duration.', 'start': 6603.096, 'duration': 6.186}, {'end': 6620.972, 'text': 'The agenda is to demo the completed software, get feedback, and then see where we are when it comes to the release plan.', 'start': 6609.922, 'duration': 11.05}, {'end': 6625.098, 'text': "The retrospective, who is there? It's attended by the team.", 'start': 6621.835, 'duration': 3.263}, {'end': 6632.625, 'text': 'And I would modify this slightly, and I would say this is the mandatory group that needs to be there.', 'start': 6625.699, 'duration': 6.926}], 'summary': 'A four-week sprint review should last a maximum of four hours and includes a demo of completed software, feedback gathering, and a mandatory team retrospective.', 'duration': 29.529, 'max_score': 6603.096, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw6603096.jpg'}], 'start': 5181.368, 'title': 'Agile in scrum', 'summary': "Discusses estimating with ideal time and story points, modified fibonacci and doubling scales in planning poker, distinction between ideal time and story points estimation, advantages of planning poker, scrum values, lifecycle overview, sprint planning and execution, and the scrum master's role in agile.", 'chapters': [{'end': 5550.118, 'start': 5181.368, 'title': 'Estimating with ideal time and story points', 'summary': 'Discusses the use of modified fibonacci and doubling scales in planning poker, the distinction between ideal time and story points estimation, and the advantages of planning poker in getting the whole team involved and reaching consensus on estimates.', 'duration': 368.75, 'highlights': ["The chapter explains the use of modified Fibonacci and doubling scales in planning poker, with values like 1, 2, 3, 5, 8, 13, 20 and 1, 2, 4, 8, 16, and the importance of not going too far to the left with the values to avoid being too granular or having overly large stories. In planning poker, values like 1, 2, 3, 5, 8, 13, 20 and 1, 2, 4, 8, 16 are used, and it's emphasized not to go too far to the left with the values to avoid being too granular or having overly large stories.", 'The chapter distinguishes between estimating in ideal time, where distractions and interruptions are implicitly accounted for without adding a specific buffer, and estimating in story points, where extra time for uncertainty in user stories is discussed and included in estimates. Estimating in ideal time implicitly accounts for distractions and interruptions without adding a specific buffer, while estimating in story points includes extra time for uncertainty in user stories.', 'The chapter compares the ease of explaining ideal time using hours and days to outsiders versus the difficulty of explaining story points, and highlights the advantages of story points in achieving consensus and speed in estimation, despite not being comparable across teams. Ideal time using hours and days is easier to explain outside the team, while story points are harder to explain but lead to faster consensus within the team, despite not being comparable across teams.', 'The chapter discusses the advantages of planning poker in terms of team involvement, quick estimation, gaining clarity in direction and approach, and reaching consensus on estimates. Planning poker is highlighted as fun, quick, involving the whole team, and providing clarity in direction and approach, leading to consensus on estimates.']}, {'end': 6232.695, 'start': 5551.559, 'title': 'Scrum values and lifecycle overview', 'summary': 'Covers the five values of scrum (c-f-o-r-c) including commitment, focus, openness, respect, and courage, as well as the scrum lifecycle, including the product backlog, sprint planning meeting, daily scrum, sprint review, and sprint retrospective.', 'duration': 681.136, 'highlights': ["The five values of Scrum are commitment, focus, openness, respect, and courage, with commitment being the team's commitment to deliver value to the customer, and courage being the courage to make commitments even in an uncertain environment.", 'The Scrum lifecycle includes the product backlog, sprint planning meeting, daily scrum, sprint review, and sprint retrospective, with the sprint planning meeting being a time-boxed event, and the sprint review focused on showcasing and demoing the software, and getting feedback from relevant stakeholders.', 'The duration of sprints is influenced by factors such as the stability of the product backlog and the cost of iterating, with shorter sprints offering more control in the face of uncertainty, and the goal of sprints being working software that is near releasable or potentially shippable.']}, {'end': 6481.785, 'start': 6232.755, 'title': 'Scrum sprint planning and execution', 'summary': 'Discusses the importance of sticking to the sprint duration and deliverables in scrum, the necessity of separate planning and retrospective ceremonies, and the involvement of the product owner in decision making for the sprint.', 'duration': 249.03, 'highlights': ['The sprint duration and deliverables do not change once the team has committed, and the sprint begins with planning and ends with review and a retrospective. The duration of the sprint does not change once the team has committed, and the sprint includes planning, review, and retrospective ceremonies.', 'Separate agendas for retrospective and planning meetings, with the product owner being the main driver of the planning meeting, making hard decisions based on constraints from the team. Retrospective and planning meetings have separate agendas. The product owner is the main driver of the planning meeting and makes hard decisions based on team constraints.', "Two approaches to deciding what's included in the sprint: commitment-based and velocity-based, aiming for team buy-in and realistic, achievable goals. There are two approaches to deciding sprint content: commitment-based and velocity-based, with the goal of achieving team buy-in and realistic goals."]}, {'end': 6746.782, 'start': 6481.785, 'title': "Scrum master's role in agile", 'summary': 'Discusses the role of the scrum master in addressing conflicts between the product owner and the team, the significance and attendees of scrum meetings, the duration and agenda of sprint reviews, and the purpose and attendees of retrospectives, emphasizing the importance of continuous improvement and the use of tools and techniques for effective facilitation.', 'duration': 264.997, 'highlights': ['The Scrum Master plays the role of the mentor, the coach, and assists in the resolution of conflicts between the product owner and the team, without deciding. The Scrum Master acts as a mentor and coach, helping to resolve conflicts between the product owner and the team without making decisions.', "The team decides on 'how' and the product owner decides on 'what' when it comes to the project. The team is responsible for deciding 'how' to execute the project, while the product owner decides 'what' needs to be done.", 'The significance of the sprint review is emphasized, with the duration being one hour per week of the sprint and the agenda focusing on demoing completed software, gathering feedback, and reviewing the release plan. The sprint review is crucial, with the duration being one hour per week of the sprint and the agenda involving demoing completed software, collecting feedback, and reviewing the release plan.', 'The mandatory attendees for the retrospective are the team, potentially the Scrum Master, and an external facilitator, with an emphasis on using tools and techniques like control charts, Ishikawa diagrams, and five whys for effective facilitation. The mandatory attendees for the retrospective are the team, potentially the Scrum Master, and an external facilitator, with an emphasis on using tools and techniques like control charts, Ishikawa diagrams, and five whys for effective facilitation.', 'The retrospective aims to identify what worked well, what did not go well, and what needs to be done differently, utilizing tools and techniques such as control charts, Ishikawa diagrams, and five whys for continuous improvement. The retrospective aims to identify what worked well, what did not go well, and what needs to be done differently, utilizing tools and techniques such as control charts, Ishikawa diagrams, and five whys for continuous improvement.']}], 'duration': 1565.414, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw5181368.jpg', 'highlights': ['The Scrum Master acts as a mentor and coach, helping to resolve conflicts between the product owner and the team without making decisions.', 'Planning poker is highlighted as fun, quick, involving the whole team, and providing clarity in direction and approach, leading to consensus on estimates.', 'The sprint review is crucial, with the duration being one hour per week of the sprint and the agenda involving demoing completed software, collecting feedback, and reviewing the release plan.', 'There are two approaches to deciding sprint content: commitment-based and velocity-based, with the goal of achieving team buy-in and realistic goals.', 'The chapter distinguishes between estimating in ideal time, where distractions and interruptions are implicitly accounted for without adding a specific buffer, and estimating in story points, where extra time for uncertainty in user stories is discussed and included in estimates.']}, {'end': 7704.374, 'segs': [{'end': 6784.489, 'src': 'embed', 'start': 6746.842, 'weight': 0, 'content': [{'end': 6749.484, 'text': 'You do a retrospective after every sprint.', 'start': 6746.842, 'duration': 2.642}, {'end': 6757.268, 'text': "If you don't, then there's no improvement.", 'start': 6750.724, 'duration': 6.544}, {'end': 6759.749, 'text': 'Things just stay static.', 'start': 6758.648, 'duration': 1.101}, {'end': 6767.562, 'text': 'Okay, so we talked about the four main ceremonies, right, in a Scrum project.', 'start': 6761.059, 'duration': 6.503}, {'end': 6778.306, 'text': 'Sprint planning, are you with me? Daily stand-up, the sprint review, and then the sprint retrospective.', 'start': 6768.502, 'duration': 9.804}, {'end': 6784.489, 'text': 'All considered mandatory for effectively doing Scrum.', 'start': 6780.747, 'duration': 3.742}], 'summary': 'Retrospective after every sprint is vital for improvement in scrum projects.', 'duration': 37.647, 'max_score': 6746.842, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw6746842.jpg'}, {'end': 6911.181, 'src': 'embed', 'start': 6878.202, 'weight': 1, 'content': [{'end': 6882.784, 'text': 'The product backlog might look something like this.', 'start': 6878.202, 'duration': 4.582}, {'end': 6892.928, 'text': "It's a list of user stories that are written by the product owner and are going to be developed by the team members.", 'start': 6883.024, 'duration': 9.904}, {'end': 6904.212, 'text': "And didn't we have, we had a product backlog for the thing that we did this morning, right? So here's another example of a product backlog.", 'start': 6894.328, 'duration': 9.884}, {'end': 6908.517, 'text': 'This is more of a list.', 'start': 6906.355, 'duration': 2.162}, {'end': 6911.181, 'text': 'It just has the title.', 'start': 6909.899, 'duration': 1.282}], 'summary': 'Product backlog is a list of user stories written by the product owner for development by the team.', 'duration': 32.979, 'max_score': 6878.202, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw6878202.jpg'}, {'end': 7089.262, 'src': 'embed', 'start': 7056.214, 'weight': 2, 'content': [{'end': 7064.598, 'text': 'Absolutely, because the product owner is involved in defining the story and what a fully implemented story looks like.', 'start': 7056.214, 'duration': 8.384}, {'end': 7071.512, 'text': "So here's a list, a short list of what a definition of done could look like.", 'start': 7065.308, 'duration': 6.204}, {'end': 7077.755, 'text': 'The story has been fully implemented or the code completed as described.', 'start': 7072.672, 'duration': 5.083}, {'end': 7084.64, 'text': 'Automated unit tests have been developed with at least 80% code coverage.', 'start': 7079.496, 'duration': 5.144}, {'end': 7086.861, 'text': 'It could be more than that.', 'start': 7085.92, 'duration': 0.941}, {'end': 7089.262, 'text': 'This is just an example.', 'start': 7087.941, 'duration': 1.321}], 'summary': 'Product owner defines story, code completed, 80% code coverage for unit tests.', 'duration': 33.048, 'max_score': 7056.214, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw7056214.jpg'}, {'end': 7173.215, 'src': 'embed', 'start': 7120.161, 'weight': 3, 'content': [{'end': 7123.945, 'text': 'The Scrum Master, the Product Owner, and the Development Team.', 'start': 7120.161, 'duration': 3.784}, {'end': 7128.67, 'text': 'The Scrum Master assists both the Development Team and the Product Owner.', 'start': 7124.426, 'duration': 4.244}, {'end': 7133.314, 'text': 'The Scrum Master works with the Product Owner to maximize return on investment.', 'start': 7129.13, 'duration': 4.184}, {'end': 7143.078, 'text': 'The Scrum Master empowers the development team by fostering creativity, removing impediments, and coaching and mentoring as appropriate.', 'start': 7134.575, 'duration': 8.503}, {'end': 7151.121, 'text': 'The Product Owner is responsible for project success by defining the project vision, requirements, and priorities.', 'start': 7143.918, 'duration': 7.203}, {'end': 7159.264, 'text': 'The Product Owner has to resist the temptation to manage the team or add more important work after a sprint has begun.', 'start': 7152.201, 'duration': 7.063}, {'end': 7165.271, 'text': 'The product owner has to be willing to make the hard choices during sprint planning.', 'start': 7160.788, 'duration': 4.483}, {'end': 7173.215, 'text': 'The development team is comprised of five to nine members with a mix of roles,', 'start': 7167.372, 'duration': 5.843}], 'summary': 'Scrum master empowers team, product owner ensures project success, 5-9 member development team', 'duration': 53.054, 'max_score': 7120.161, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw7120161.jpg'}, {'end': 7331.864, 'src': 'embed', 'start': 7299.828, 'weight': 5, 'content': [{'end': 7301.408, 'text': 'They are committed to the team cause.', 'start': 7299.828, 'duration': 1.58}, {'end': 7309.11, 'text': "Even if being a Scrum Master is a part-time task for them, they will give the highest priority to the team's needs.", 'start': 7302.289, 'duration': 6.821}, {'end': 7317.215, 'text': "Hence, the Scrum Master's work allocation, especially if they are part-time, needs to take this into consideration.", 'start': 7309.91, 'duration': 7.305}, {'end': 7319.797, 'text': 'They are able to influence.', 'start': 7318.436, 'duration': 1.361}, {'end': 7326.481, 'text': 'They are naturally good communicators and able to convince others to adopt different approaches.', 'start': 7320.677, 'duration': 5.804}, {'end': 7331.864, 'text': 'They apply various techniques to mobilize organizational resources when required.', 'start': 7327.061, 'duration': 4.803}], 'summary': 'Part-time scrum masters prioritize team needs, influence, and mobilize resources.', 'duration': 32.036, 'max_score': 7299.828, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw7299828.jpg'}, {'end': 7503.482, 'src': 'embed', 'start': 7474.335, 'weight': 6, 'content': [{'end': 7478.336, 'text': 'They ensure that the team stays true to the principles of agile development.', 'start': 7474.335, 'duration': 4.001}, {'end': 7480.837, 'text': 'Scrum master roles, Scrum teams.', 'start': 7478.616, 'duration': 2.221}, {'end': 7489.979, 'text': "Before we discuss the role of a developer on a Scrum team, let's talk about the desirable characteristics of Scrum teams.", 'start': 7481.937, 'duration': 8.042}, {'end': 7492.599, 'text': 'They should be small and nimble.', 'start': 7490.939, 'duration': 1.66}, {'end': 7497.28, 'text': 'Team size should be no less than three and no more than nine.', 'start': 7493.179, 'duration': 4.101}, {'end': 7500.261, 'text': 'So that would be six plus or minus three.', 'start': 7497.901, 'duration': 2.36}, {'end': 7503.482, 'text': 'Exceptions are possible, but uncommon.', 'start': 7501.181, 'duration': 2.301}], 'summary': 'Scrum teams should be small, with 3-9 members, to maintain agility.', 'duration': 29.147, 'max_score': 7474.335, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw7474335.jpg'}], 'start': 6746.842, 'title': 'Scrum essentials', 'summary': 'Covers scrum ceremonies, artifacts, master and product owner roles, and team characteristics, highlighting mandatory ceremonies, artifacts, and role responsibilities for effective scrum implementation, with examples and insights provided for each aspect.', 'chapters': [{'end': 6964.438, 'start': 6746.842, 'title': 'Scrum ceremonies and artifacts', 'summary': 'Discusses the importance of scrum ceremonies such as sprint planning, daily stand-up, sprint review, and sprint retrospective, emphasizing their mandatory nature for effective scrum implementation, along with insights on scrum artifacts including product backlog, sprint backlog, and release backlog, with an example of how user stories are grouped into releases based on a product roadmap.', 'duration': 217.596, 'highlights': ['The chapter discusses the importance of Scrum ceremonies such as sprint planning, daily stand-up, sprint review, and sprint retrospective, emphasizing their mandatory nature for effective Scrum implementation. The four main ceremonies in a Scrum project are sprint planning, daily stand-up, sprint review, and sprint retrospective, all considered mandatory for effectively doing Scrum.', 'Insights on Scrum artifacts including product backlog, sprint backlog, and release backlog, with an example of how user stories are grouped into releases based on a product roadmap. Depending on the size of the project, it might be advisable to group user stories into releases aligned with a product roadmap, with the release backlog being a subset of the product backlog and the sprint backlog being a subset of the release backlog.', "The product backlog is a list of user stories that are written by the product owner and are going to be developed by the team members, and it can be added or removed based on the product owner's preferences. The product backlog is a list of user stories written by the product owner, prioritized and subject to additions or removals based on the product owner's preferences."]}, {'end': 7299.288, 'start': 6965.299, 'title': 'Scrum master and product owner roles', 'summary': "Emphasizes the roles and responsibilities of the scrum master, product owner, and development team in scrum, including the definition of done and key attributes of a scrum master, with examples such as the team's autonomy and the scrum master's facilitation duties.", 'duration': 333.989, 'highlights': ['The definition of done is primarily a checklist that forms the agreement between the product owner and the team, including examples such as fully implemented stories, code completion, and automated unit tests with at least 80% code coverage. The definition of done serves as an agreement between the product owner and the team, encompassing aspects such as fully implemented stories, code completion, and the development of automated unit tests with a minimum code coverage threshold of 80%.', "The Scrum Master's role is to empower the development team, facilitate Scrum ceremonies, and remove obstacles, while emphasizing that the Scrum Master should not make decisions for the team or infringe on its autonomy. The Scrum Master's responsibilities include empowering the development team, facilitating Scrum ceremonies, and removing obstacles, with a clear emphasis on not making decisions for the team or undermining its autonomy.", 'The Product Owner is responsible for defining the project vision, requirements, and priorities, and is cautioned against managing the team or introducing additional work after a sprint has started. The Product Owner bears the responsibility of defining the project vision, requirements, and priorities, while being advised against managing the team or introducing additional work once a sprint has commenced.']}, {'end': 7704.374, 'start': 7299.828, 'title': "Scrum master's role and team characteristics", 'summary': "Highlights the crucial role of a scrum master in prioritizing the team's needs, their ability to influence, knowledge requirements, tasks, and responsibilities, along with the desirable characteristics of scrum teams, emphasizing small, self-sufficient, cross-functional, autonomous, and self-organizing teams.", 'duration': 404.546, 'highlights': ["Scrum Masters prioritize the team's needs and are committed to the team cause, even if it is a part-time task, influencing and mobilizing resources to assist the team. The Scrum Master's commitment to the team's cause, even when serving part-time, and their ability to influence and mobilize resources to assist the team.", 'Scrum Masters are expected to be knowledgeable enough to have productive conversations about the project being done by the team and be experts in the Scrum method, serving as process coaches for the team. The knowledge requirements and responsibilities of Scrum Masters, including being knowledgeable about the project and serving as process coaches for the team.', 'Desirable characteristics of Scrum teams, such as being small, nimble, self-sufficient, cross-functional, autonomous, and self-organizing, with a focus on feature teams over component teams and assembling the right mix of people for the team. The desirable characteristics of Scrum teams, including being small, self-sufficient, cross-functional, autonomous, and self-organizing, along with the importance of assembling the right mix of people for the team.']}], 'duration': 957.532, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw6746842.jpg', 'highlights': ['The four main mandatory Scrum ceremonies are sprint planning, daily stand-up, sprint review, and sprint retrospective.', 'The product backlog is a prioritized list of user stories written by the product owner, subject to additions or removals.', 'The definition of done includes fully implemented stories, code completion, and automated unit tests with at least 80% code coverage.', "The Scrum Master's responsibilities include empowering the development team, facilitating Scrum ceremonies, and removing obstacles.", 'The Product Owner is responsible for defining the project vision, requirements, and priorities, cautioned against managing the team or introducing additional work after a sprint has started.', "The Scrum Master's commitment to the team's cause, even when serving part-time, and their ability to influence and mobilize resources to assist the team.", 'Desirable characteristics of Scrum teams include being small, nimble, self-sufficient, cross-functional, autonomous, and self-organizing.']}, {'end': 8983.659, 'segs': [{'end': 7781.692, 'src': 'embed', 'start': 7705.194, 'weight': 0, 'content': [{'end': 7712.478, 'text': "Once a team has been formed, it's best to preserve and assign whole teams rather than individuals to projects.", 'start': 7705.194, 'duration': 7.284}, {'end': 7718.112, 'text': "It's best to avoid assigning team members to multiple projects at the same time.", 'start': 7713.729, 'duration': 4.383}, {'end': 7720.213, 'text': 'Distributed team.', 'start': 7719.473, 'duration': 0.74}, {'end': 7723.395, 'text': 'A distributed team may be unavoidable.', 'start': 7721.134, 'duration': 2.261}, {'end': 7730.28, 'text': 'Those based at the same geographical location should be co-located in the same team room.', 'start': 7724.516, 'duration': 5.764}, {'end': 7740.166, 'text': 'And technology processes and ground rules should be put in place to overcome the disadvantages of all team members not being co-located.', 'start': 7731.361, 'duration': 8.805}, {'end': 7746.131, 'text': 'Plotting team size and productivity will likely result in an S-curve.', 'start': 7741.127, 'duration': 5.004}, {'end': 7751.435, 'text': 'You can see here that a team can actually be too small or too large.', 'start': 7746.731, 'duration': 4.704}, {'end': 7757.554, 'text': 'Remember the sweet spot is 6 plus or minus 3.', 'start': 7751.615, 'duration': 5.939}, {'end': 7768.443, 'text': 'Think of Scrum as a lightweight framework that utilizes principles and practices that assist teams in delivering working software in short cycles to the customer,', 'start': 7757.554, 'duration': 10.889}, {'end': 7773.628, 'text': 'enabling rapid feedback, continuous improvement and quick response to change.', 'start': 7768.443, 'duration': 5.185}, {'end': 7781.692, 'text': 'It promotes delivering value as in working software to the customer in an incremental and iterative way.', 'start': 7775.051, 'duration': 6.641}], 'summary': 'Preserve whole teams, avoid multiple projects, aim for 6±3 team size, use scrum for rapid feedback.', 'duration': 76.498, 'max_score': 7705.194, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw7705194.jpg'}, {'end': 8170.487, 'src': 'embed', 'start': 8144.455, 'weight': 3, 'content': [{'end': 8149.116, 'text': 'The product backlog may also include risk or defect related user stories.', 'start': 8144.455, 'duration': 4.661}, {'end': 8154.558, 'text': 'The product owner is responsible for keeping the product backlog current and up to date.', 'start': 8149.897, 'duration': 4.661}, {'end': 8160.58, 'text': 'This is accomplished by pruning the backlog, which is prioritizing and reprioritizing.', 'start': 8155.178, 'duration': 5.402}, {'end': 8164.322, 'text': 'The product backlog must also be continually groomed.', 'start': 8161.48, 'duration': 2.842}, {'end': 8170.487, 'text': 'This is the process of adding and removing user stories based on the needs and desires of the customer.', 'start': 8164.763, 'duration': 5.724}], 'summary': 'Product backlog requires continuous grooming to prioritize and update user stories.', 'duration': 26.032, 'max_score': 8144.455, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw8144455.jpg'}, {'end': 8220.204, 'src': 'embed', 'start': 8190.791, 'weight': 4, 'content': [{'end': 8195.674, 'text': 'If the sprint is going to be two weeks in duration, then the time box will be four hours.', 'start': 8190.791, 'duration': 4.883}, {'end': 8202.901, 'text': 'If the sprint is going to be four weeks in duration, then the time box for the sprint planning meeting will be eight hours.', 'start': 8196.376, 'duration': 6.525}, {'end': 8207.564, 'text': 'It should be attended by the complete Scrum team, including all roles.', 'start': 8203.821, 'duration': 3.743}, {'end': 8215.431, 'text': "The most important aspects of this meeting are the team's capacity and the definition of done.", 'start': 8208.645, 'duration': 6.786}, {'end': 8220.204, 'text': 'There are two approaches to selecting user stories for a sprint.', 'start': 8216.862, 'duration': 3.342}], 'summary': 'Sprint planning: 2-week sprint = 4-hour time box, 4-week sprint = 8-hour time box, involves complete scrum team, focuses on capacity and definition of done, 2 approaches for selecting user stories.', 'duration': 29.413, 'max_score': 8190.791, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw8190791.jpg'}, {'end': 8270.827, 'src': 'embed', 'start': 8239.327, 'weight': 5, 'content': [{'end': 8245.25, 'text': 'The time box for the daily scrum is 15 minutes, regardless of the duration of the sprint length.', 'start': 8239.327, 'duration': 5.923}, {'end': 8250.565, 'text': 'The entire Scrum team, including all roles, should attend the daily Scrum.', 'start': 8246.164, 'duration': 4.401}, {'end': 8255.867, 'text': 'Each development team member individually answers three questions.', 'start': 8251.606, 'duration': 4.261}, {'end': 8258.008, 'text': 'What did I do yesterday??', 'start': 8256.687, 'duration': 1.321}, {'end': 8260.248, 'text': 'What am I going to do today?', 'start': 8258.748, 'duration': 1.5}, {'end': 8261.949, 'text': 'And what are my impediments?', 'start': 8260.647, 'duration': 1.302}, {'end': 8270.827, 'text': 'This is how the team members coordinate their work and the scrum master learns of the impediments he or she should be taking care of.', 'start': 8263.139, 'duration': 7.688}], 'summary': 'Daily scrum lasts 15 mins, involves all team roles, with each member answering 3 questions to coordinate work and address impediments.', 'duration': 31.5, 'max_score': 8239.327, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw8239326.jpg'}, {'end': 8333.928, 'src': 'embed', 'start': 8308.666, 'weight': 6, 'content': [{'end': 8317.715, 'text': 'The sprint retrospective takes place after the conclusion of the sprint review and is time boxed at 45 minutes for each week of the sprint.', 'start': 8308.666, 'duration': 9.049}, {'end': 8324.941, 'text': 'So if the sprint has two weeks in duration, then the retrospective would be one and a half hours in length.', 'start': 8319.316, 'duration': 5.625}, {'end': 8329.665, 'text': 'It should be attended by the complete scrum team, including all roles.', 'start': 8325.861, 'duration': 3.804}, {'end': 8333.928, 'text': "However, the product owner's attendance is considered optional.", 'start': 8330.565, 'duration': 3.363}], 'summary': 'Sprint retrospective is a 45-minute meeting after each sprint review, lasts 1.5 hours for a 2-week sprint, attended by complete scrum team.', 'duration': 25.262, 'max_score': 8308.666, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw8308665.jpg'}, {'end': 8402.829, 'src': 'embed', 'start': 8359.814, 'weight': 7, 'content': [{'end': 8366.842, 'text': "At the conclusion of the retrospective, the team's velocity and the project's information radiators are updated.", 'start': 8359.814, 'duration': 7.028}, {'end': 8373.428, 'text': 'Then the next sprints planning meeting takes place and this cycle continues until the project is complete.', 'start': 8367.803, 'duration': 5.625}, {'end': 8377.432, 'text': 'The definition of done is an important artifact for a scrum team.', 'start': 8373.909, 'duration': 3.523}, {'end': 8384.897, 'text': 'It is the primary reporting mechanism for team members and there may be a different definition of done at various levels.', 'start': 8377.652, 'duration': 7.245}, {'end': 8389.102, 'text': 'Definition of done for a feature or user story.', 'start': 8385.978, 'duration': 3.124}, {'end': 8394.942, 'text': 'the definition of done for a sprint, and the definition of done for a release.', 'start': 8390.137, 'duration': 4.805}, {'end': 8402.829, 'text': "It's really just a checklist of activities that add verifiable and demonstrable value to the product.", 'start': 8396.083, 'duration': 6.746}], 'summary': 'Retrospective updates velocity and information radiators, followed by sprint planning until project completion. definition of done crucial for reporting and has different levels.', 'duration': 43.015, 'max_score': 8359.814, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw8359814.jpg'}, {'end': 8690.243, 'src': 'embed', 'start': 8663.367, 'weight': 9, 'content': [{'end': 8670.929, 'text': "Why don't you go first, Aaron? Yesterday I was working on creating the mock objects to mask the database calls from the unit tests.", 'start': 8663.367, 'duration': 7.562}, {'end': 8679.636, 'text': 'The difficulty with this approach is that our server-side logic is so dependent on the metadata that writing a true mock is a mammoth exercise.', 'start': 8671.991, 'duration': 7.645}, {'end': 8683.479, 'text': 'There are decisions that are taken during runtime based on the data.', 'start': 8680.497, 'duration': 2.982}, {'end': 8690.243, 'text': 'Some of the stored procedure calls are also made based on the values returned through inline queries that are also embedded in the code.', 'start': 8684.019, 'duration': 6.224}], 'summary': 'Creating mock objects for unit tests; server-side logic heavily dependent on metadata and dynamic data', 'duration': 26.876, 'max_score': 8663.367, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw8663367.jpg'}], 'start': 7705.194, 'title': 'Agile team and scrum framework', 'summary': 'Emphasizes team formation, productivity, and the sweet spot of 6 plus or minus 3 team members, discusses key principles of scrum, including sprint planning, duration, overhead costs, and backlogs, and addresses scrum ceremonies, methodology, and challenges with unit test mocking.', 'chapters': [{'end': 7757.554, 'start': 7705.194, 'title': 'Team formation and productivity', 'summary': 'Emphasizes the importance of preserving and assigning whole teams to projects, avoiding assigning team members to multiple projects, and considering the sweet spot of 6 plus or minus 3 team members to maximize productivity.', 'duration': 52.36, 'highlights': ['Preserve and assign whole teams to projects rather than individuals, avoiding assigning team members to multiple projects at the same time.', 'Consider the sweet spot of 6 plus or minus 3 team members for optimal productivity.', 'Put technology processes and ground rules in place to overcome the disadvantages of distributed teams.', 'Co-locate team members based at the same geographical location in the same team room.', 'Plotting team size and productivity will likely result in an S-curve, indicating that a team can be too small or too large.']}, {'end': 8164.322, 'start': 7757.554, 'title': 'Understanding scrum framework', 'summary': 'Discusses the key principles and practices of scrum, including sprint planning, sprint duration, overhead costs, and the three backlogs used in scrum, emphasizing the importance of delivering working software and continuous improvement.', 'duration': 406.768, 'highlights': ['Scrum promotes delivering value as in working software to the customer in an incremental and iterative way. Scrum emphasizes delivering working software in short cycles to the customer, enabling rapid feedback, continuous improvement, and quick response to change.', 'The sprint duration is determined at the beginning of the project and factors affecting it include the stability of the product backlog. The duration of sprints is determined at the beginning of the project and can vary based on factors such as the stability of the product backlog.', 'The product backlog, release backlog, and sprint backlog are used in Scrum, with the product backlog being continuously pruned and prioritized to deliver maximum value to the customer. Scrum uses three backlogs: the product backlog, release backlog, and sprint backlog, with the product backlog being continually prioritized to deliver maximum value to the customer.', 'The goal of a sprint is to deliver near-releasable or potentially shippable software, with the sprint ending at the appointed time to allow for effective continuous improvement. The goal of a sprint is to deliver near-releasable or potentially shippable software, with the sprint ending at the appointed time to allow for effective continuous improvement.', 'The product owner is responsible for keeping the product backlog current and up to date by continually grooming and prioritizing it. The product owner is responsible for maintaining the product backlog by continually grooming, pruning, and reprioritizing it to keep it current and up to date.']}, {'end': 8358.893, 'start': 8164.763, 'title': 'Scrum ceremonies and process', 'summary': 'Discusses the four scrum ceremonies, including their time boxing and key aspects, and emphasizes the importance of team buy-in and feedback in achieving project success in agile development.', 'duration': 194.13, 'highlights': ['The sprint planning meeting is time boxed at two hours for each week of the sprint. Emphasizes the time boxing for sprint planning meeting, highlighting its duration.', 'The time box for the daily scrum is 15 minutes, regardless of the duration of the sprint length. Highlights the fixed time duration for daily scrum, regardless of sprint length.', 'The sprint retrospective takes place after the conclusion of the sprint review and is time boxed at 45 minutes for each week of the sprint. Emphasizes the time boxing for sprint retrospective, indicating its duration.', 'The purpose of the review is to demonstrate working software and obtain and assess feedback. Stresses the purpose of sprint review, emphasizing the demonstration of working software and the importance of feedback.', 'There are two approaches to selecting user stories for a sprint. One is based on the velocity of the team, the other is commitment driven. Highlights the two approaches for selecting user stories, emphasizing velocity-based and commitment-driven approaches.']}, {'end': 8623.856, 'start': 8359.814, 'title': 'Scrum methodology and daily stand-up meeting', 'summary': 'Discusses the importance of the definition of done in scrum, the process of updating velocity and information radiators in a retrospective, and the outline of a daily stand-up meeting in a new scrum project, emphasizing the role of the scrum master and the participation of team members.', 'duration': 264.042, 'highlights': ['The definition of done is an important artifact for a Scrum team, serving as the primary reporting mechanism for team members, with different levels of definition for features/user stories, sprints, and releases. The definition of done serves as the primary reporting mechanism for team members, with different levels of definition for features/user stories, sprints, and releases, providing a checklist of activities that add verifiable and demonstrable value to the product.', "The process of updating velocity and information radiators takes place at the conclusion of the retrospective, with the next sprints planning meeting continuing the cycle until project completion. At the conclusion of the retrospective, the team updates its velocity and the project's information radiators, with the next sprints planning meeting continuing the cycle until the project is complete.", 'The daily stand-up meeting in the new Scrum project is outlined, with the Scrum Master leading the 15-minute time-boxed meeting, encouraging team members to discuss their activities, plans, and obstacles, and ensuring the inclusion of all team members, including those joining via video chat. The chapter outlines the daily stand-up meeting in the new Scrum project, highlighting the role of the Scrum Master in leading the 15-minute time-boxed meeting, encouraging team members to discuss their activities, plans, and obstacles, and ensuring the inclusion of all team members, including those joining via video chat.']}, {'end': 8983.659, 'start': 8663.367, 'title': 'Challenges with unit test mocking', 'summary': 'Discusses the challenges faced in creating mock objects for unit tests due to server-side logic dependency on metadata, inline queries, and performance reasons, along with the need for offline conversations to track down blocking issues.', 'duration': 320.292, 'highlights': ['The difficulty with this approach is that our server-side logic is so dependent on the metadata that writing a true mock is a mammoth exercise. The server-side logic is heavily reliant on metadata, making it challenging to create a true mock for unit testing.', 'Some of the stored procedure calls are also made based on the values returned through inline queries that are also embedded in the code. Stored procedure calls are dependent on values from inline queries embedded in the code, adding to the complexity of the mocking process.', 'This is mainly for performance reasons when the overheads of making a procedure call based on a metadata value and then processing the. Inline queries are utilized for performance reasons to avoid overheads of making a procedure call based on metadata value.', "May I suggest we write this issue in the parking lot? I'm not sure what you mean by that, Rick. Let me explain. Suggestion to move the issue to the parking lot for offline discussions after the daily scrum to address blocking issues effectively.", "I'll also make a note that will track the impediment Aaron faced daily until it is removed. Commitment to track and address the impediment faced by Aaron on a daily basis until resolved."]}], 'duration': 1278.465, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw7705194.jpg', 'highlights': ['Preserve and assign whole teams to projects for optimal productivity', 'Consider the sweet spot of 6 plus or minus 3 team members', 'Scrum emphasizes delivering working software in short cycles', 'Product backlog continuously pruned and prioritized for value delivery', 'Sprint planning meeting time boxed at two hours per week of sprint', 'Daily scrum time box fixed at 15 minutes, regardless of sprint length', 'Sprint retrospective time boxed at 45 minutes per week of sprint', 'Definition of done serves as primary reporting mechanism for team', 'Updating velocity and information radiators at conclusion of retrospective', 'Server-side logic heavily reliant on metadata, challenging for unit testing']}, {'end': 11406.185, 'segs': [{'end': 9011.511, 'src': 'embed', 'start': 8984.379, 'weight': 4, 'content': [{'end': 8990.204, 'text': "Anything else before we close the meeting? All right, that's it for today.", 'start': 8984.379, 'duration': 5.825}, {'end': 8991.224, 'text': 'Have a great day.', 'start': 8990.584, 'duration': 0.64}, {'end': 8994.487, 'text': 'Do you have a moment to chat about the inline queries real quick?', 'start': 8992.165, 'duration': 2.322}, {'end': 9000.147, 'text': 'The purpose of a Scrum meeting is to keep the team members updated and resolve any impediments.', 'start': 8995.765, 'duration': 4.382}, {'end': 9003.768, 'text': "It's an ideal way to kickstart the day on a positive note.", 'start': 9000.827, 'duration': 2.941}, {'end': 9011.511, 'text': 'The Scrum Master reinforces the sense of the self-managing team, facilitates communication between team members,', 'start': 9004.568, 'duration': 6.943}], 'summary': 'Scrum meetings facilitate team updates and issue resolution, reinforcing self-management and positive start to the day.', 'duration': 27.132, 'max_score': 8984.379, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw8984379.jpg'}, {'end': 9050.963, 'src': 'embed', 'start': 9025.74, 'weight': 0, 'content': [{'end': 9033.447, 'text': 'Scrum is a simple, agile project management framework that is used by organizations to help teams collaborate,', 'start': 9025.74, 'duration': 7.707}, {'end': 9040.834, 'text': 'handle unpredictability and complex projects or products, while ensuring the products delivered are of the highest value.', 'start': 9033.447, 'duration': 7.387}, {'end': 9050.963, 'text': 'It describes a set of meetings, tools, and roles that enable teams to work in sync and help them structure themselves and manage their work.', 'start': 9041.915, 'duration': 9.048}], 'summary': 'Scrum: agile framework for collaboration and delivering high-value products.', 'duration': 25.223, 'max_score': 9025.74, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw9025740.jpg'}, {'end': 9162.526, 'src': 'embed', 'start': 9134.315, 'weight': 2, 'content': [{'end': 9141.018, 'text': 'Following this the scrum team which is usually 5 to 9 members strong will work on these tasks.', 'start': 9134.315, 'duration': 6.703}, {'end': 9151.241, 'text': 'Now they also have regular scrum meetings where they talk about their victories, the issues they face and what they plan to do in the next 24 hours.', 'start': 9142.178, 'duration': 9.063}, {'end': 9155.843, 'text': 'And then they have the sprint review.', 'start': 9153.943, 'duration': 1.9}, {'end': 9162.526, 'text': 'The sprint review is a meeting during which the team shows what they accomplished during the sprint.', 'start': 9156.764, 'duration': 5.762}], 'summary': 'Scrum team of 5-9 members works on tasks, has regular scrum meetings, and sprint review.', 'duration': 28.211, 'max_score': 9134.315, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw9134315.jpg'}, {'end': 9257.983, 'src': 'embed', 'start': 9228.907, 'weight': 1, 'content': [{'end': 9233.171, 'text': 'Kanban uses something known as the Kanban board to make these things possible.', 'start': 9228.907, 'duration': 4.264}, {'end': 9241.078, 'text': 'With this, you can easily identify bottlenecks and then fix them cost effectively at optimal speeds.', 'start': 9234.732, 'duration': 6.346}, {'end': 9245.019, 'text': 'The main focus with Kanban is transparency.', 'start': 9242.298, 'duration': 2.721}, {'end': 9252.281, 'text': 'Since everything related to the tasks are on the board, everyone can keep themselves updated.', 'start': 9245.819, 'duration': 6.462}, {'end': 9257.983, 'text': "It also ensures that teams focus on their current tasks until they're done.", 'start': 9253.261, 'duration': 4.722}], 'summary': 'Kanban optimizes workflow with transparency and efficiency, enabling bottleneck identification and faster problem-solving.', 'duration': 29.076, 'max_score': 9228.907, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw9228907.jpg'}, {'end': 9329.805, 'src': 'embed', 'start': 9294.229, 'weight': 3, 'content': [{'end': 9296.97, 'text': 'Now the board consists of three major components.', 'start': 9294.229, 'duration': 2.741}, {'end': 9302.529, 'text': "There's the to-do list, which represents items that need to be completed.", 'start': 9298.339, 'duration': 4.19}, {'end': 9307.72, 'text': 'The ongoing column, which represents items that are being currently worked on.', 'start': 9303.611, 'duration': 4.109}, {'end': 9310.8, 'text': 'and the completed or the done column.', 'start': 9309.099, 'duration': 1.701}, {'end': 9315.701, 'text': 'Now these represent tasks or items that have already been completed.', 'start': 9311.36, 'duration': 4.341}, {'end': 9320.102, 'text': 'Now, although this is a physical representation of the board,', 'start': 9316.621, 'duration': 3.481}, {'end': 9329.805, 'text': 'several organizations use software versions of the board that replaces the sticky notes with cards that can be moved from one column to another as work progresses.', 'start': 9320.102, 'duration': 9.703}], 'summary': 'Board consists of to-do, ongoing, and completed columns for task management.', 'duration': 35.576, 'max_score': 9294.229, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw9294229.jpg'}, {'end': 9589.8, 'src': 'embed', 'start': 9535.522, 'weight': 5, 'content': [{'end': 9538.643, 'text': 'In Scrum for planning and process improvement.', 'start': 9535.522, 'duration': 3.121}, {'end': 9544.686, 'text': 'velocity, which is the measure of the work that can be completed by a team in a sprint, is the key metric.', 'start': 9538.643, 'duration': 6.043}, {'end': 9548.358, 'text': 'In Kanban, lead time is the key metric.', 'start': 9545.936, 'duration': 2.422}, {'end': 9555.565, 'text': "This represents the period of time between a new task's appearance in your workflow and its final departure from the system.", 'start': 9548.939, 'duration': 6.626}, {'end': 9562.15, 'text': "Next, let's have a look at how teams work in these frameworks.", 'start': 9558.767, 'duration': 3.383}, {'end': 9568.056, 'text': 'In Scrum, you need a cross-functional team to achieve your goals in a sprint.', 'start': 9563.151, 'duration': 4.905}, {'end': 9577.45, 'text': 'In Kanban, cross-functional teams are optional, but specialized teams that focus on particular aspects of the workflow are required.', 'start': 9569.264, 'duration': 8.186}, {'end': 9581.974, 'text': "Now let's talk about new additions.", 'start': 9579.792, 'duration': 2.182}, {'end': 9589.8, 'text': "In Scrum, just like handling changes, you can't add any items between a sprint or an iteration.", 'start': 9583.074, 'duration': 6.726}], 'summary': 'Scrum uses velocity as key metric; kanban uses lead time. scrum requires cross-functional teams; kanban allows specialized teams.', 'duration': 54.278, 'max_score': 9535.522, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw9535522.jpg'}, {'end': 9660.495, 'src': 'embed', 'start': 9623.671, 'weight': 7, 'content': [{'end': 9627.632, 'text': 'With Scrum, the board needs to be reset once a particular sprint is complete.', 'start': 9623.671, 'duration': 3.961}, {'end': 9634.38, 'text': 'With Kanban, the board stays persistent throughout the entirety of the project.', 'start': 9629.957, 'duration': 4.423}, {'end': 9638.422, 'text': "And finally, let's have a look at project length.", 'start': 9635.901, 'duration': 2.521}, {'end': 9642.345, 'text': "With Scrum, it's better suited for longer projects.", 'start': 9639.383, 'duration': 2.962}, {'end': 9649.629, 'text': 'And with Kanban, projects that can be completed in a shorter period of time are better.', 'start': 9644.686, 'duration': 4.943}, {'end': 9660.495, 'text': 'So which one should you choose? Now selecting from these two methods is mainly based on the requirements of the team.', 'start': 9652.031, 'duration': 8.464}], 'summary': 'Scrum suits longer projects, kanban for shorter ones; choice based on team requirements.', 'duration': 36.824, 'max_score': 9623.671, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw9623671.jpg'}, {'end': 9719.204, 'src': 'embed', 'start': 9694.3, 'weight': 6, 'content': [{'end': 9700.443, 'text': 'Some of the companies that have successfully implemented Scrum are Facebook, General Electronics and Adobe.', 'start': 9694.3, 'duration': 6.143}, {'end': 9706.286, 'text': 'Companies that have implemented Kanban are Siemens, BBC and SAP.', 'start': 9701.524, 'duration': 4.762}, {'end': 9713.53, 'text': 'If getting your learning started is half the battle, what if you could do that for free? Visit SkillUp by SimplyLearn.', 'start': 9707.186, 'duration': 6.344}, {'end': 9716.111, 'text': 'Click on the link in the description to know more.', 'start': 9713.87, 'duration': 2.241}, {'end': 9719.204, 'text': 'So, as part of this tutorial,', 'start': 9717.403, 'duration': 1.801}], 'summary': 'Companies like facebook, general electronics, and adobe have implemented scrum, while siemens, bbc, and sap have implemented kanban.', 'duration': 24.904, 'max_score': 9694.3, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw9694300.jpg'}, {'end': 9800.021, 'src': 'embed', 'start': 9771.162, 'weight': 11, 'content': [{'end': 9776.865, 'text': 'So what are the typical roles we come across in scrum? So one of the roles we come across is product owner.', 'start': 9771.162, 'duration': 5.703}, {'end': 9786.751, 'text': 'So product owner is primarily responsible for maximizing the ROI by determining the product features, prioritizing it into list.', 'start': 9777.726, 'duration': 9.025}, {'end': 9794.137, 'text': 'what needs to be focused on for the next print and constantly reprioritizing and refining it.', 'start': 9787.432, 'duration': 6.705}, {'end': 9800.021, 'text': 'so what happens is whenever we may require to deliver, it is very important for us to have the requirements clear,', 'start': 9794.137, 'duration': 5.884}], 'summary': 'In scrum, the product owner is responsible for maximizing roi by prioritizing and refining product features.', 'duration': 28.859, 'max_score': 9771.162, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw9771162.jpg'}, {'end': 10181.624, 'src': 'embed', 'start': 10154.411, 'weight': 14, 'content': [{'end': 10162.417, 'text': 'Whereas scrum defines the roles like the scrum master, the product owner, the self organizing teams, which is cross functional self organizing team.', 'start': 10154.411, 'duration': 8.006}, {'end': 10165.84, 'text': 'So these are the main three roles which scrum defines.', 'start': 10163.238, 'duration': 2.602}, {'end': 10170.744, 'text': 'Now generally when we say projects, we come across the role like project manager.', 'start': 10166.461, 'duration': 4.283}, {'end': 10173.787, 'text': 'So do we see such project managers in scrum??', 'start': 10171.185, 'duration': 2.602}, {'end': 10181.624, 'text': 'Answer is no, because the scrum master, who engages with the team regularly, More than management,', 'start': 10174.367, 'duration': 7.257}], 'summary': 'Scrum defines roles like scrum master, product owner, and self-organizing teams, not project managers.', 'duration': 27.213, 'max_score': 10154.411, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw10154411.jpg'}, {'end': 10250.393, 'src': 'embed', 'start': 10221.27, 'weight': 15, 'content': [{'end': 10227.616, 'text': 'the scrum methodology is made such a way, the team understanding that can able to react,', 'start': 10221.27, 'duration': 6.346}, {'end': 10231.74, 'text': 'and those changes and modifications are made visible to the team.', 'start': 10227.616, 'duration': 4.124}, {'end': 10240.069, 'text': 'so delivery perspective manifesto provides necessary guidelines on frequent delivery of product or software.', 'start': 10232.566, 'duration': 7.503}, {'end': 10250.393, 'text': 'so scrum, with time boxed iterations called sprints builds, delivers to the users regularly and upheld agile principles.', 'start': 10240.069, 'duration': 10.324}], 'summary': 'Scrum methodology enables frequent delivery of software, upholding agile principles.', 'duration': 29.123, 'max_score': 10221.27, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw10221270.jpg'}, {'end': 10383.278, 'src': 'embed', 'start': 10359.487, 'weight': 16, 'content': [{'end': 10368.271, 'text': 'As per the list which is prioritized in the product backlog, that is taken, put into sprint backlog and then those are delivered.', 'start': 10359.487, 'duration': 8.784}, {'end': 10371.792, 'text': 'So next you can think about product increment.', 'start': 10369.271, 'duration': 2.521}, {'end': 10380.697, 'text': 'The product increment is the combination of all product backlog tasks completed in the sprint and the value of the increments of previous sprints.', 'start': 10372.433, 'duration': 8.264}, {'end': 10383.278, 'text': 'The outcome should be in the usable condition.', 'start': 10381.557, 'duration': 1.721}], 'summary': 'Product backlog tasks are taken, put into sprint backlog, and delivered as product increment in usable condition.', 'duration': 23.791, 'max_score': 10359.487, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw10359487.jpg'}, {'end': 10536.743, 'src': 'embed', 'start': 10508.217, 'weight': 12, 'content': [{'end': 10513.098, 'text': 'Scrum Master helps everyone to understand the theory, practices, rules and values in the Scrum.', 'start': 10508.217, 'duration': 4.881}, {'end': 10517.879, 'text': 'So Scrum Master is playing the role of facilitation.', 'start': 10513.878, 'duration': 4.001}, {'end': 10519.519, 'text': 'enablement right?', 'start': 10517.879, 'duration': 1.64}, {'end': 10526.021, 'text': 'So Scrum Master ensures the team follows Scrum values, principles and practices.', 'start': 10520.3, 'duration': 5.721}, {'end': 10530.842, 'text': 'removes blockages that may hamper the progress of the project.', 'start': 10526.021, 'duration': 4.821}, {'end': 10536.743, 'text': 'protects the team from being distracted, ensuring the team delivers value during every sprint.', 'start': 10530.842, 'duration': 5.901}], 'summary': 'Scrum master enables team to follow scrum, remove blockages, and deliver value.', 'duration': 28.526, 'max_score': 10508.217, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw10508217.jpg'}, {'end': 10629.163, 'src': 'embed', 'start': 10601.951, 'weight': 18, 'content': [{'end': 10611.113, 'text': 'any support is required by the team to focus on that, so something like that can be checked on question number nine what is scrum ban?', 'start': 10601.951, 'duration': 9.162}, {'end': 10616.034, 'text': 'so scrum ban is a development methodology that is a combination of scrum and kanban.', 'start': 10611.113, 'duration': 4.921}, {'end': 10625.801, 'text': 'So this can be used to meet the needs of the team that aims to minimize the batching of work and to adopt a pull based system.', 'start': 10617.156, 'duration': 8.645}, {'end': 10629.163, 'text': 'So Kanban is called as pull based system.', 'start': 10626.942, 'duration': 2.221}], 'summary': 'Scrum ban combines scrum and kanban to minimize work batching and adopt a pull-based system.', 'duration': 27.212, 'max_score': 10601.951, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw10601951.jpg'}, {'end': 10704.527, 'src': 'embed', 'start': 10678.32, 'weight': 19, 'content': [{'end': 10685.602, 'text': 'Structure of scrum that has the structure of scrum and the flexibility of a flow based method Like on one.', 'start': 10678.32, 'duration': 7.282}, {'end': 10688.023, 'text': "It's a question number 10..", 'start': 10685.602, 'duration': 2.421}, {'end': 10690.083, 'text': 'What is print zero and spike?', 'start': 10688.023, 'duration': 2.06}, {'end': 10698.305, 'text': 'So the term sprint zero refers to the short amount of effort put for creation of vision, a rough skeleton of the product backlog.', 'start': 10690.483, 'duration': 7.822}, {'end': 10704.527, 'text': 'So now we do this whenever we need to understand certain things, how things looks like, to get certain insights.', 'start': 10698.305, 'duration': 6.222}], 'summary': 'Scrum has the flexibility of a flow-based method, sprint zero creates vision and product backlog skeleton.', 'duration': 26.207, 'max_score': 10678.32, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw10678320.jpg'}, {'end': 10819.239, 'src': 'embed', 'start': 10792.334, 'weight': 20, 'content': [{'end': 10798.797, 'text': 'all of them together, for accomplishing the common objective for business, various scrum teams you would have.', 'start': 10792.334, 'duration': 6.463}, {'end': 10806.779, 'text': 'so scrum of scrum helps in terms of better collaboration and handle them easily or, better way, better control.', 'start': 10798.797, 'duration': 7.982}, {'end': 10811.817, 'text': 'It is best used in situations where teams are working together on complex assignments.', 'start': 10807.415, 'duration': 4.402}, {'end': 10819.239, 'text': 'Just visualizing the system, various different deliverables which are not simple deliverables which we can do with a simple scrum team.', 'start': 10811.977, 'duration': 7.262}], 'summary': 'Scrum of scrum improves collaboration for complex assignments with multiple teams.', 'duration': 26.905, 'max_score': 10792.334, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw10792334.jpg'}, {'end': 10884.798, 'src': 'embed', 'start': 10858.835, 'weight': 21, 'content': [{'end': 10867.461, 'text': "So user story mapping represents and arranges user stories that help with understanding the system's functionalities,", 'start': 10858.835, 'duration': 8.626}, {'end': 10872.144, 'text': "the system's backlog planning releases and providing value to the customers.", 'start': 10867.461, 'duration': 4.683}, {'end': 10879.209, 'text': 'So first of all, we write user stories to understand the required features functionality in the user perspective.', 'start': 10872.765, 'duration': 6.444}, {'end': 10884.798, 'text': 'Now, if we map those user stories, which user story link to other user story?', 'start': 10879.975, 'duration': 4.823}], 'summary': 'User story mapping organizes user stories to understand system functionalities and plan releases.', 'duration': 25.963, 'max_score': 10858.835, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw10858835.jpg'}, {'end': 10939.306, 'src': 'embed', 'start': 10911.343, 'weight': 22, 'content': [{'end': 10914.025, 'text': 'so that things can be done in order with full clarity.', 'start': 10911.343, 'duration': 2.682}, {'end': 10918.687, 'text': 'So question number 13, what happens in sprint retrospective?', 'start': 10914.725, 'duration': 3.962}, {'end': 10923.329, 'text': 'So after the sprint review, so sprint completes.', 'start': 10919.207, 'duration': 4.122}, {'end': 10925.29, 'text': 'so sprint review happens.', 'start': 10923.329, 'duration': 1.961}, {'end': 10926.811, 'text': 'the sprint retrospective is done.', 'start': 10925.29, 'duration': 1.521}, {'end': 10935.104, 'text': 'So during this meeting, The lessons learnt, what went well, what mistakes we did, what were the issues.', 'start': 10927.511, 'duration': 7.593}, {'end': 10937.685, 'text': 'So is there any new way of doing things.', 'start': 10936.144, 'duration': 1.541}, {'end': 10939.306, 'text': 'So all these are discussed.', 'start': 10938.185, 'duration': 1.121}], 'summary': 'Sprint retrospective: review, lessons learned, issues, and improvements discussed after each sprint completion.', 'duration': 27.963, 'max_score': 10911.343, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw10911343.jpg'}, {'end': 10988.712, 'src': 'embed', 'start': 10962.156, 'weight': 23, 'content': [{'end': 10968.301, 'text': 'So these are discussed and very essential to do it at the end of completion of each of the sprints review.', 'start': 10962.156, 'duration': 6.145}, {'end': 10971.944, 'text': 'Question number 14.', 'start': 10970.123, 'duration': 1.821}, {'end': 10974.466, 'text': 'What is empirical process control in Scrum?', 'start': 10971.944, 'duration': 2.522}, {'end': 10984.65, 'text': 'So empiricism refers to work based on facts, experiences, evidences, observations and experimentation.', 'start': 10975.948, 'duration': 8.702}, {'end': 10988.712, 'text': 'so empirical process control is established and followed in scrum,', 'start': 10984.65, 'duration': 4.062}], 'summary': 'Empirical process control is essential in scrum, based on facts, experiences, evidences, observations, and experimentation.', 'duration': 26.556, 'max_score': 10962.156, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw10962156.jpg'}, {'end': 11085.783, 'src': 'embed', 'start': 11056.464, 'weight': 24, 'content': [{'end': 11060.448, 'text': 'so next question is what are some drawbacks of using scrum?', 'start': 11056.464, 'duration': 3.984}, {'end': 11068.471, 'text': 'so scrum requires individuals who have experience, without whom the project risks will have a risk of failure.', 'start': 11060.448, 'duration': 8.023}, {'end': 11072.093, 'text': 'So one does not have a capability, difficult.', 'start': 11069.331, 'duration': 2.762}, {'end': 11075.315, 'text': 'Scrum requires team to be collaborative and committed.', 'start': 11072.594, 'duration': 2.721}, {'end': 11081.26, 'text': 'So people collaborating, individuals collaborating itself is a big challenge in many organizations.', 'start': 11076.196, 'duration': 5.064}, {'end': 11085.783, 'text': 'So bringing this into the place is very important when you want to adopt Scrum.', 'start': 11081.9, 'duration': 3.883}], 'summary': 'Scrum requires experienced individuals for successful implementation and demands collaborative commitment from the team.', 'duration': 29.319, 'max_score': 11056.464, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw11056464.jpg'}, {'end': 11169.425, 'src': 'embed', 'start': 11144.966, 'weight': 25, 'content': [{'end': 11151.311, 'text': 'So next question is, what are the skills of a Scrum Master? So a strong understanding of Scrum and Agile concept.', 'start': 11144.966, 'duration': 6.345}, {'end': 11155.934, 'text': 'Scrum Master should have fine-tuned organizational skills.', 'start': 11152.212, 'duration': 3.722}, {'end': 11160.718, 'text': 'So when Scrum Master is working with self-organizing team with various different capabilities.', 'start': 11156.455, 'duration': 4.263}, {'end': 11169.425, 'text': 'So unless the organization skills, interpersonal skills, if Scrum Master does not have, working with them will become difficult.', 'start': 11161.559, 'duration': 7.866}], 'summary': 'Scrum master needs strong scrum knowledge, organizational and interpersonal skills.', 'duration': 24.459, 'max_score': 11144.966, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw11144966.jpg'}, {'end': 11274.455, 'src': 'embed', 'start': 11240.861, 'weight': 26, 'content': [{'end': 11241.521, 'text': 'Question number 17.', 'start': 11240.861, 'duration': 0.66}, {'end': 11247.197, 'text': 'How can discord be dealt within the scrum team.', 'start': 11241.521, 'duration': 5.676}, {'end': 11250.899, 'text': 'Now the root cause of the issue need to be identified and addressed.', 'start': 11247.837, 'duration': 3.062}, {'end': 11257.364, 'text': 'Complete ownership needs to be established when you deal with this and try to defuse the disagreements.', 'start': 11251.66, 'duration': 5.704}, {'end': 11261.086, 'text': 'So emphasizing on the focus area that complements the project.', 'start': 11257.844, 'duration': 3.242}, {'end': 11269.392, 'text': 'So here, when we take up any of the discussions, any of the opportunities or any actions, what we take, everything,', 'start': 11262.248, 'duration': 7.144}, {'end': 11274.455, 'text': 'should be revolving around objective of ultimate objective of whatever we are doing.', 'start': 11269.392, 'duration': 5.063}], 'summary': 'Address discord in scrum team by identifying root cause and establishing complete ownership to defuse disagreements and focus on project objectives.', 'duration': 33.594, 'max_score': 11240.861, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw11240861.jpg'}, {'end': 11364.398, 'src': 'embed', 'start': 11329.844, 'weight': 27, 'content': [{'end': 11330.625, 'text': 'Very very important.', 'start': 11329.844, 'duration': 0.781}, {'end': 11338.691, 'text': 'Next question, what is a user story? User stories are an agile software development project management tools.', 'start': 11331.548, 'duration': 7.143}, {'end': 11346.733, 'text': "It provides the team with simple natural language explanations of one or more features written from the end user's perspective.", 'start': 11339.891, 'duration': 6.842}, {'end': 11350.775, 'text': 'For example, I am an account holder in a bank.', 'start': 11347.694, 'duration': 3.081}, {'end': 11357.915, 'text': 'so first, what is the facility a bank would give to account holders?', 'start': 11352.592, 'duration': 5.323}, {'end': 11364.398, 'text': 'there is atm banking, there is net banking, there is mobile banking and there is over the counter.', 'start': 11357.915, 'duration': 6.483}], 'summary': "User stories are important in agile development, providing natural language explanations of features from the end user's perspective.", 'duration': 34.554, 'max_score': 11329.844, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw11329844.jpg'}], 'start': 8984.379, 'title': 'Scrum and kanban in agile', 'summary': 'Discusses scrum and kanban, highlighting their principles, differences, and applications, with insights into popular company adoptions, typical interview questions, key differences with agile, and methodologies supporting agile teams.', 'chapters': [{'end': 9339.643, 'start': 8984.379, 'title': 'Scrum vs kanban: agile frameworks compared', 'summary': 'Discusses the key principles and processes of scrum and kanban, highlighting that scrum is a project management framework used for collaboration and managing unpredictability, involving meetings like sprint planning and sprint review, while kanban is a visual system focused on transparency and limiting work in progress, using a kanban board.', 'duration': 355.264, 'highlights': ['Scrum is a project management framework used for collaboration and managing unpredictability, involving meetings like Sprint Planning and Sprint Review. Scrum is described as a simple, agile project management framework used by organizations to help teams collaborate, handle unpredictability and complex projects or products, while ensuring the products delivered are of the highest value. It involves meetings like Sprint Planning and Sprint Review.', 'Kanban is a visual system focused on transparency and limiting work in progress, using a Kanban board. Kanban is described as a popular agile framework that is a visual system by which work can be managed with ease as it progresses. It focuses on transparency and limits the amount of work in progress by using a Kanban board.', 'Scrum team usually consists of 5 to 9 members and works on tasks decided in the Sprint Planning. The Scrum team is usually 5 to 9 members strong and works on the tasks decided in the Sprint Planning, which is a 2-4 week period to deliver tasks from the product backlog.', 'Kanban uses a to-do list, ongoing column, and completed column on the Kanban board to represent the workflow. Kanban uses a to-do list, ongoing column, and completed column on the Kanban board to represent where each item is with respect to the workflow, ensuring transparency and focusing on current tasks until completion.', 'The purpose of a Scrum meeting is to keep the team members updated and resolve any impediments. The purpose of a Scrum meeting is to keep the team members updated and resolve any impediments, reinforcing the sense of a self-managing team and facilitating communication between team members.']}, {'end': 9719.204, 'start': 9343.085, 'title': 'Scrum vs kanban similarities and differences', 'summary': "Explores the similarities and differences between scrum and kanban, highlighting that both frameworks emphasize lean and agile principles, have time-boxed and iterative approaches, aim to reduce work in progress, and employ pull scheduling, while differing in cadence, release methodology, handling changes, metrics, team structure, new additions, job roles, representation, and project length, ultimately suggesting that the choice between the two is based on the team's requirements, with popular companies such as facebook, general electronics, and adobe implementing scrum, and siemens, bbc, and sap implementing kanban.", 'duration': 376.119, 'highlights': ['The chapter explores the similarities and differences between Scrum and Kanban, highlighting that both frameworks emphasize lean and agile principles, have time-boxed and iterative approaches, aim to reduce work in progress, and employ pull scheduling. (relevance: 5)', 'Popular companies that have successfully implemented Scrum include Facebook, General Electronics, and Adobe, while companies that have implemented Kanban include Siemens, BBC, and SAP. (relevance: 4)', "The choice between Scrum and Kanban is based on the team's requirements, with Scrum being suitable for longer projects and involving cross-functional teams, while Kanban is more suitable for shorter projects and allowing changes at any time. (relevance: 3)", 'Scrum and Kanban differ in cadence, release methodology, handling changes, metrics, team structure, new additions, job roles, representation, and project length. For example, in Scrum, releases take place after each sprint, while in Kanban, releases take place in the form of continuous delivery. (relevance: 2)', "In Scrum, velocity is the key metric for planning and process improvement, while in Kanban, lead time is the key metric representing the period of time between a new task's appearance in the workflow and its final departure from the system. (relevance: 1)"]}, {'end': 10023.75, 'start': 9719.204, 'title': 'Scrum interview questions', 'summary': 'Covers typical interview questions related to scrum, including the definition of scrum, roles in scrum such as product owner, scrum master, and scrum team, and the responsibilities of the scrum team in a self-organizing framework, emphasizing the importance of daily scrum meetings and sprint iterations.', 'duration': 304.546, 'highlights': ['Scrum is a framework that enables teams to work together, learn from experiences, self-organize, and reflect on their victories and losses to improve. Scrum framework facilitates team collaboration and self-organization, fostering continuous improvement based on learning from experiences.', "Product Owner is responsible for maximizing ROI by determining product features, prioritizing them, and constantly reprioritizing and refining the product backlog. Product Owner's key responsibilities include maximizing ROI, determining and prioritizing product features, and ensuring constant refinement of the product backlog.", 'Scrum Master helps teams learn and apply Scrum, removes impediments, and ensures the team adopts agile practices to obtain business value. Scrum Master plays a crucial role in mentoring teams, removing impediments, and guiding the adoption of agile practices to achieve business value.', 'Scrum Team is a self-organizing group working together to deliver stakeholder requirements, typically comprising 5 to 7 members with diverse capabilities. The self-organizing Scrum Team collaborates to deliver stakeholder requirements, leveraging diverse capabilities within a specific size range.', "The responsibilities of the Scrum Team include the development and delivery of working products during each sprint, with daily scrum meetings to ensure ownership, transparency, and progress updates. Scrum Team's responsibilities encompass developing and delivering working products in each sprint, while daily scrum meetings ensure ownership, transparency, and progress updates."]}, {'end': 10601.951, 'start': 10023.75, 'title': 'Agile vs scrum: key differences and implementation', 'summary': 'Differentiates between agile and scrum, highlighting agile as the ability to move quickly and easily, and scrum as an agile methodology enabling organizations to become agile. it emphasizes the roles, collaboration, and artifacts involved in scrum, and its alignment with the agile manifesto and 12 principles.', 'duration': 578.201, 'highlights': ["Scrum is an Agile methodology enabling organizations to become Agile, emphasizing flexibility and adaptability. Scrum is highlighted as an Agile methodology, focusing on flexibility and adaptability, aligning with the Agile manifesto's emphasis on working software and embracing changes.", 'Scrum defines roles like the scrum master, the product owner, and the self-organizing teams, emphasizing collaboration and flexibility. Scrum defines specific roles including the scrum master, product owner, and self-organizing teams, promoting collaboration and flexibility in decision-making.', 'Scrum methodology is designed for reacting to changes, with time-boxed iterations called sprints delivering to users regularly. The Scrum methodology facilitates quick reactions to changes through time-boxed iterations (sprints) for regular delivery to users, aligning with Agile principles.', 'The product backlog, sprint backlog, and product increment are key artifacts in the Scrum process, highlighting the tasks and value delivery. Key artifacts in the Scrum process include product backlog, sprint backlog, and product increment, emphasizing task management and value delivery.', 'The scrum master promotes and supports the adoption of Scrum, ensuring the team follows Scrum values, principles, and practices. The scrum master plays a crucial role in promoting and supporting Scrum adoption, ensuring adherence to Scrum values, principles, and practices for the team.']}, {'end': 10911.343, 'start': 10601.951, 'title': 'Agile methodologies overview', 'summary': 'Covers the methodologies scrumban, sprint zero and spike, scrum of scrums, and user story mapping, emphasizing their key principles and applications to effectively support agile teams in minimizing work batching, visualization, risk reduction, and collaboration between multiple teams for complex assignments.', 'duration': 309.392, 'highlights': ["Scrum ban methodology Scrum ban combines the structure of Scrum with the flexibility and visualization of Kanban, aiming to minimize work batching and adopt a pull-based system to support the team's needs.", 'Sprint Zero and Spike Sprint Zero involves creating a vision and product backlog skeleton, while Spike activities aim to reduce technical approach risks through research, design, and investigation, facilitating informed decisions and improving reliability.', 'Scrum of Scrums Scrum of Scrums is utilized for better collaboration and control between multiple Scrum teams, especially in complex project scenarios, helping to establish transparency, collaboration, and adaptation to ensure the successful development and delivery of products aligned with business objectives.', 'User Story Mapping User story mapping arranges user stories to understand system functionalities, backlog planning, and value delivery, aiding in determining interlinked functionalities and prioritizing them based on sophistication levels to facilitate a specific flow of handling.']}, {'end': 11406.185, 'start': 10911.343, 'title': 'Scrum retrospective and empirical process control', 'summary': 'Discusses the importance of sprint retrospective, empirical process control in scrum, drawbacks of using scrum, skills of a scrum master, dealing with discord within the scrum team, and user stories in agile software development.', 'duration': 494.842, 'highlights': ['Importance of Sprint Retrospective The sprint retrospective is essential to collect and discuss lessons learned, mistakes, and new ways of doing things, in order to make necessary corrections for upcoming iterations, with data from the meeting being incorporated when planning new sprints.', 'Empirical Process Control in Scrum Empirical process control in Scrum is based on facts, experiences, evidences, observations, and experimentation, ensuring project progress and interpretation is transparent and based on observed data, mindset of the team, and shift required in thought process and culture.', 'Drawbacks of Using Scrum Scrum requires experienced individuals for project success, collaborative and committed teams, skilled Scrum Masters, well-defined tasks, and may be less suitable for large complex projects.', "Skills of a Scrum Master A Scrum Master should possess a strong understanding of Scrum and Agile concepts, organizational skills, familiarity with the team's technology, ability to coach the team in following Scrum methodologies, conflict resolution skills, and be a servant leader.", 'Dealing with Discord within the Scrum Team Dealing with discord within the Scrum team involves identifying and addressing the root cause of the issue, establishing complete ownership, defusing disagreements, emphasizing the focus area that complements the project, and guiding the team towards a common understanding.', "User Stories in Agile Software Development User stories are agile software development project management tools that provide the team with simple natural language explanations of one or more features written from the end user's perspective, facilitating the visualization of user needs and requirements."]}], 'duration': 2421.806, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw8984379.jpg', 'highlights': ['Scrum is a project management framework for collaboration and managing unpredictability, involving Sprint Planning and Sprint Review.', 'Kanban is a visual system focused on transparency and limiting work in progress, using a Kanban board.', 'Scrum team usually consists of 5 to 9 members and works on tasks decided in the Sprint Planning.', 'Kanban uses a to-do list, ongoing column, and completed column on the Kanban board to represent the workflow.', 'The purpose of a Scrum meeting is to keep the team members updated and resolve any impediments.', 'Scrum and Kanban emphasize lean and agile principles, have time-boxed and iterative approaches, aim to reduce work in progress, and employ pull scheduling.', 'Popular companies that have successfully implemented Scrum include Facebook, General Electronics, and Adobe.', "The choice between Scrum and Kanban is based on the team's requirements, with Scrum being suitable for longer projects and involving cross-functional teams.", 'Scrum and Kanban differ in cadence, release methodology, handling changes, metrics, team structure, new additions, job roles, representation, and project length.', "In Scrum, velocity is the key metric for planning and process improvement, while in Kanban, lead time is the key metric representing the period of time between a new task's appearance in the workflow and its final departure from the system.", 'Scrum is a framework that enables teams to work together, learn from experiences, self-organize, and reflect on their victories and losses to improve.', 'Product Owner is responsible for maximizing ROI by determining product features, prioritizing them, and constantly reprioritizing and refining the product backlog.', 'Scrum Master helps teams learn and apply Scrum, removes impediments, and ensures the team adopts agile practices to obtain business value.', 'Scrum is an Agile methodology enabling organizations to become Agile, emphasizing flexibility and adaptability.', 'Scrum defines roles like the scrum master, the product owner, and the self-organizing teams, emphasizing collaboration and flexibility.', 'Scrum methodology is designed for reacting to changes, with time-boxed iterations called sprints delivering to users regularly.', 'The product backlog, sprint backlog, and product increment are key artifacts in the Scrum process, highlighting the tasks and value delivery.', 'The scrum master promotes and supports the adoption of Scrum, ensuring the team follows Scrum values, principles, and practices.', "Scrum ban methodology combines the structure of Scrum with the flexibility and visualization of Kanban, aiming to minimize work batching and adopt a pull-based system to support the team's needs.", 'Sprint Zero involves creating a vision and product backlog skeleton, while Spike activities aim to reduce technical approach risks through research, design, and investigation.', 'Scrum of Scrums is utilized for better collaboration and control between multiple Scrum teams, especially in complex project scenarios.', 'User story mapping arranges user stories to understand system functionalities, backlog planning, and value delivery, aiding in determining interlinked functionalities and prioritizing them based on sophistication levels.', 'Importance of Sprint Retrospective to collect and discuss lessons learned, mistakes, and new ways of doing things for necessary corrections in upcoming iterations.', 'Empirical process control in Scrum is based on facts, experiences, evidences, observations, and experimentation, ensuring project progress and interpretation is transparent and based on observed data.', 'Drawbacks of Using Scrum: requires experienced individuals, collaborative and committed teams, skilled Scrum Masters, well-defined tasks, and may be less suitable for large complex projects.', "Skills of a Scrum Master: strong understanding of Scrum and Agile concepts, organizational skills, familiarity with the team's technology, ability to coach the team in following Scrum methodologies, conflict resolution skills, and be a servant leader.", 'Dealing with discord within the Scrum team involves identifying and addressing the root cause of the issue, establishing complete ownership, defusing disagreements, emphasizing the focus area that complements the project, and guiding the team towards a common understanding.', "User stories are agile software development project management tools that provide the team with simple natural language explanations of one or more features written from the end user's perspective."]}, {'end': 12520.892, 'segs': [{'end': 11437.605, 'src': 'embed', 'start': 11406.185, 'weight': 0, 'content': [{'end': 11413.309, 'text': 'and what features functionality the particular mobile app should have, so that account holder can download the statements.', 'start': 11406.185, 'duration': 7.124}, {'end': 11416.811, 'text': 'So user stories will provide that insights, whatever users.', 'start': 11414.13, 'duration': 2.681}, {'end': 11419.273, 'text': 'So account holder is not just an user here.', 'start': 11417.352, 'duration': 1.921}, {'end': 11422.895, 'text': 'There are many users when it comes to mobile app of a bank.', 'start': 11419.453, 'duration': 3.442}, {'end': 11427.358, 'text': 'We have people who monitor it, manage it, who develop it.', 'start': 11423.696, 'duration': 3.662}, {'end': 11437.605, 'text': 'So they need to have a clarity on what exactly they need and that needs to be written as part of user story that what features functionality can be easily determined out of it.', 'start': 11428.419, 'duration': 9.186}], 'summary': 'User stories define features for mobile app, including statement download for account holders.', 'duration': 31.42, 'max_score': 11406.185, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw11406185.jpg'}, {'end': 11608.155, 'src': 'embed', 'start': 11562.519, 'weight': 3, 'content': [{'end': 11567.12, 'text': 'What is Sprint? Now as I mentioned earlier in the earlier question number 4.', 'start': 11562.519, 'duration': 4.601}, {'end': 11570.145, 'text': 'So Sprint is the terminology used in the scrum.', 'start': 11567.12, 'duration': 3.025}, {'end': 11573.467, 'text': 'I think we explained various different concepts as we went through.', 'start': 11570.665, 'duration': 2.802}, {'end': 11578.511, 'text': 'So sprint is the terminology used in scrum which refers to time box iterations.', 'start': 11574.468, 'duration': 4.043}, {'end': 11583.155, 'text': 'So we understood what is this iterations in scrum approaches when we are going through that.', 'start': 11578.771, 'duration': 4.384}, {'end': 11588.519, 'text': 'The creation of specific module or feature which is part of a product is done during the sprint.', 'start': 11583.935, 'duration': 4.584}, {'end': 11592.342, 'text': 'The duration of sprint varies between a week or two.', 'start': 11589.579, 'duration': 2.763}, {'end': 11594.303, 'text': "So means it's a short duration.", 'start': 11592.842, 'duration': 1.461}, {'end': 11597.966, 'text': 'Simple few features functionalities are taken and created.', 'start': 11594.984, 'duration': 2.982}, {'end': 11608.155, 'text': 'So what is velocity? So velocity is the metric used in scrum that is a measurement of the amount of work that is completed by team during the sprint.', 'start': 11598.507, 'duration': 9.648}], 'summary': 'Sprint is a time-boxed iteration in scrum, lasting a week or two, completing specific product features. velocity measures work completed in a sprint.', 'duration': 45.636, 'max_score': 11562.519, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw11562519.jpg'}, {'end': 11660.836, 'src': 'embed', 'start': 11630.564, 'weight': 4, 'content': [{'end': 11634.765, 'text': 'so what are the responsibilities of a product owner?', 'start': 11630.564, 'duration': 4.201}, {'end': 11645.028, 'text': 'so product owner define the vision of the project, they anticipate the needs of the customer and to create appropriate user stories.', 'start': 11634.765, 'duration': 10.263}, {'end': 11647.469, 'text': "so they don't write user stories as such.", 'start': 11645.028, 'duration': 2.441}, {'end': 11652.811, 'text': 'they definitely have a set of people who should get involved the team to write the user stories.', 'start': 11647.469, 'duration': 5.342}, {'end': 11660.836, 'text': 'lot of discussion has to happen, brainstorming has to happen to write user stories, but product owner is accountable.', 'start': 11652.811, 'duration': 8.025}], 'summary': 'Product owners define project vision, anticipate customer needs, and oversee user story creation.', 'duration': 30.272, 'max_score': 11630.564, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw11630564.jpg'}, {'end': 11771.434, 'src': 'embed', 'start': 11741.835, 'weight': 5, 'content': [{'end': 11742.936, 'text': 'It helps you to understand that.', 'start': 11741.835, 'duration': 1.101}, {'end': 11752.739, 'text': 'So it shows total effort against the amount of work for each iterations, which is helpful for you to see to that what is pending to complete.', 'start': 11743.976, 'duration': 8.763}, {'end': 11754.8, 'text': 'Question 24.', 'start': 11753.4, 'duration': 1.4}, {'end': 11757.181, 'text': 'How is estimation in the scrum project done?', 'start': 11754.8, 'duration': 2.381}, {'end': 11767.932, 'text': 'So the estimation of user stories is done based on its difficulty, a particular scale in which which is used to assess the difficulty of user stories.', 'start': 11758.542, 'duration': 9.39}, {'end': 11771.434, 'text': 'So you have to analyze how difficult or easy is that.', 'start': 11768.713, 'duration': 2.721}], 'summary': 'Estimation in scrum project is based on user story difficulty using a specific scale.', 'duration': 29.599, 'max_score': 11741.835, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw11741835.jpg'}, {'end': 11822.086, 'src': 'embed', 'start': 11792.185, 'weight': 6, 'content': [{'end': 11801.111, 'text': 'So some types of risk in Scrum are related to budget, people, sprint, product, knowledge and capability.', 'start': 11792.185, 'duration': 8.926}, {'end': 11811.799, 'text': 'Now when we say budget, risk of increase exceeding that allocated budget, looking for more variations.', 'start': 11802.412, 'duration': 9.387}, {'end': 11816.082, 'text': 'I estimated for x, it is going like x plus delta x.', 'start': 11811.959, 'duration': 4.123}, {'end': 11818.243, 'text': 'So can we control it? We need to look at that.', 'start': 11816.082, 'duration': 2.161}, {'end': 11819.464, 'text': 'So you need to assess that risk.', 'start': 11818.283, 'duration': 1.181}, {'end': 11822.086, 'text': 'In what possibilities the cost can escalate.', 'start': 11819.644, 'duration': 2.442}], 'summary': 'Scrum risks include budget exceeding x, need to assess and control', 'duration': 29.901, 'max_score': 11792.185, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw11792185.jpg'}, {'end': 11942.608, 'src': 'embed', 'start': 11916.913, 'weight': 1, 'content': [{'end': 11924.559, 'text': 'So once you have implemented and defined and implemented the response plans, quite obvious you should keep monitoring it and manage the risks.', 'start': 11916.913, 'duration': 7.646}, {'end': 11929.323, 'text': 'Now risk impacts and probabilities may vary as the project progresses.', 'start': 11925.38, 'duration': 3.943}, {'end': 11936.97, 'text': 'So we may require to keep assessing the identified risk and keep identifying the new risks as we progress in the project.', 'start': 11929.804, 'duration': 7.166}, {'end': 11942.608, 'text': 'So these are done on a continual basis right from starting of the project till completion.', 'start': 11938.044, 'duration': 4.564}], 'summary': 'Continuously monitor and manage risks throughout project implementation.', 'duration': 25.695, 'max_score': 11916.913, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw11916913.jpg'}, {'end': 12051.569, 'src': 'embed', 'start': 12022.494, 'weight': 7, 'content': [{'end': 12029.92, 'text': 'The identified one keep assessing as the project progresses and check on is there any new risk is introduced as the project is progressing.', 'start': 12022.494, 'duration': 7.426}, {'end': 12037.587, 'text': 'So next question, what are some popular tools used in Scrum? So these are the list.', 'start': 12032.042, 'duration': 5.545}, {'end': 12046.354, 'text': 'So you can think of Gtub, Zoho, Trello, Jira Software, Yordix, Version 1.', 'start': 12038.327, 'duration': 8.027}, {'end': 12051.569, 'text': 'So now what I am saying is these are the tools, technology tools.', 'start': 12046.354, 'duration': 5.215}], 'summary': 'Assess project risk continuously; popular scrum tools include gtub, zoho, trello, jira software, yordix, version 1.', 'duration': 29.075, 'max_score': 12022.494, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw12022494.jpg'}, {'end': 12297.946, 'src': 'embed', 'start': 12270.301, 'weight': 2, 'content': [{'end': 12279.431, 'text': 'So just to explain you along with scope creep what else would happen to where the additional deliverables would come in which is gold plating.', 'start': 12270.301, 'duration': 9.13}, {'end': 12288.042, 'text': 'so question 29 what is mvp and mmp, which means minimum viable product and minimal marketing product?', 'start': 12280.02, 'duration': 8.022}, {'end': 12297.946, 'text': 'so now, minimum viable product is a concept of lean startup which stresses upon the impact of learning while performing product development.', 'start': 12288.042, 'duration': 9.904}], 'summary': 'Mvp and mmp defined as minimum viable product and minimal marketing product, emphasizing learning in product development.', 'duration': 27.645, 'max_score': 12270.301, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw12270301.jpg'}, {'end': 12350.512, 'src': 'embed', 'start': 12324.622, 'weight': 8, 'content': [{'end': 12331.364, 'text': 'this will also provide more insight towards what the customers or users needs are.', 'start': 12324.622, 'duration': 6.742}, {'end': 12336.945, 'text': 'so when it comes to minimal marketable product, This refers to the description of the product,', 'start': 12331.364, 'duration': 5.581}, {'end': 12341.768, 'text': 'which will have a minimal number of features that addresses the requirements of the users.', 'start': 12336.945, 'duration': 4.823}, {'end': 12350.512, 'text': 'The MMP would help also the organization reduce the time to market because you have the clarity what is that we may require to provide.', 'start': 12342.848, 'duration': 7.664}], 'summary': 'Minimal marketable product (mmp) reduces time to market by addressing user needs with minimal features.', 'duration': 25.89, 'max_score': 12324.622, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw12324622.jpg'}], 'start': 11406.185, 'title': 'Importance of user stories and agile framework in mobile app development', 'summary': 'Discusses the significance of user stories in determining mobile app features and functionality, emphasizing clarity and value for end users. it also explains the agile framework, user stories, and risk management in project management, emphasizing team involvement, continual risk assessment, and understanding mvp and mmp.', 'chapters': [{'end': 11469.915, 'start': 11406.185, 'title': 'User stories for mobile app features', 'summary': 'Discusses the importance of user stories in determining the features and functionality of a mobile app, emphasizing the need for clarity and value for end users, both internal and external.', 'duration': 63.73, 'highlights': ['The user stories provide insights into the features and functionality required for account holders to download statements, emphasizing that the account holder is not the only user, and clarity is needed for those who monitor, manage, and develop the mobile app.', 'User stories focus on how a certain type of work will bring value to the end user, whether they are external end users or internal customers or colleagues within the organization, as exemplified by the creation of an HR application for internal users in the banking context.', 'The clarity on what features and functionality are needed for the mobile app is crucial and should be written as part of the user story, with an emphasis on not going into detail but rather easily determining the required features and functionality.']}, {'end': 11869.936, 'start': 11472.656, 'title': 'Agile framework and user stories', 'summary': 'Explains the agile framework, user stories, epics, tasks, sprints, velocity, product owner responsibilities, burn up and down charts, estimation, and risks in scrum, emphasizing the importance of team involvement in writing user stories.', 'duration': 397.28, 'highlights': ['User stories provide a simple explanation of business requirements from the end user perspective, while epics are collections of related user stories that form an epic. User stories provide a simple explanation of business requirements from the end user perspective, while epics are collections of related user stories that form an epic.', 'Sprints refer to time box iterations in Scrum, with a duration varying between a week or two, during which specific modules or features are created. Sprints refer to time box iterations in Scrum, with a duration varying between a week or two, during which specific modules or features are created.', 'Velocity, a metric used in Scrum, measures the amount of work completed by the team during a sprint, indicating the speed at which work is progressing. Velocity, a metric used in Scrum, measures the amount of work completed by the team during a sprint, indicating the speed at which work is progressing.', 'The responsibilities of a product owner include defining the project vision, anticipating customer needs, evaluating project progress based on the backlog, and being accountable for all product-related questions. The responsibilities of a product owner include defining the project vision, anticipating customer needs, evaluating project progress based on the backlog, and being accountable for all product-related questions.', 'Estimation of user stories in Scrum is done based on difficulty, utilizing scales such as numeric sizing, t-shirt sizing, Fibonacci series, or dog breeds to assess the difficulty of user stories. Estimation of user stories in Scrum is done based on difficulty, utilizing scales such as numeric sizing, t-shirt sizing, Fibonacci series, or dog breeds to assess the difficulty of user stories.', 'Risks in Scrum include budget, people, sprint, product, knowledge, and capability-related risks, such as exceeding allocated budget, team members lacking appropriate skills, ill-defined user stories and epics, and uncertainties about project knowledge and capabilities. Risks in Scrum include budget, people, sprint, product, knowledge, and capability-related risks, such as exceeding allocated budget, team members lacking appropriate skills, ill-defined user stories and epics, and uncertainties about project knowledge and capabilities.']}, {'end': 12520.892, 'start': 11870.296, 'title': 'Risk management in projects', 'summary': 'Covers the importance of risk management in project management, emphasizing the need for continual risk assessment and monitoring, popular tools used in scrum, tracking sprint progress, dealing with scope creep, understanding mvp and mmp, the definition of done (dod), and the role of a scrum master as a servant leader and coordinator between multiple teams.', 'duration': 650.596, 'highlights': ['Understanding the importance of continual risk assessment and monitoring Continual risk assessment and monitoring are emphasized to manage project risks effectively, with a focus on identifying, assessing, and managing risks throughout the project lifecycle.', 'Explanation of popular tools used in Scrum such as Gtub, Zoho, Trello, Jira Software, Yordix, and Version 1 The chapter provides a list of popular technology tools used in Scrum, including Gtub, Zoho, Trello, Jira Software, Yordix, and Version 1, and emphasizes the need to understand the specific project requirements before selecting a tool.', 'The concept of minimum viable product (MVP) and minimal marketable product (MMP) The concept of MVP is discussed, stressing the importance of learning from the initial version of the product for target customers. Additionally, the concept of MMP is explained as a product with minimal features that address user requirements, reducing time to market.', 'Definition of Done (DoD) and its role in project development The Definition of Done is elaborated as a collection of deliverables that add demonstrable value to project development, helping to identify the steps required for project iterations and ensuring effective project management.', 'The role of a Scrum Master as a servant leader and coordinator between multiple teams The concept of a servant leader is explained, emphasizing the need for the Scrum Master to demonstrate service orientation and act as a facilitator, guide, and mentor. Additionally, the coordination between multiple teams is addressed through scrum of scrums meetings and the role of a chief scrum master.']}], 'duration': 1114.707, 'thumbnail': 'https://coursnap.oss-ap-southeast-1.aliyuncs.com/video-capture/RLFy9BoH6Sw/pics/RLFy9BoH6Sw11406185.jpg', 'highlights': ['User stories provide insights into features and functionality for account holders, emphasizing clarity and value for all users.', 'Understanding the importance of continual risk assessment and monitoring for effective project risk management.', 'The concept of minimum viable product (MVP) and minimal marketable product (MMP) is discussed, stressing the importance of learning from the initial version of the product for target customers.', 'Sprints refer to time box iterations in Scrum, with a duration varying between a week or two, during which specific modules or features are created.', 'The responsibilities of a product owner include defining the project vision, anticipating customer needs, evaluating project progress based on the backlog, and being accountable for all product-related questions.', 'Estimation of user stories in Scrum is done based on difficulty, utilizing scales such as numeric sizing, t-shirt sizing, Fibonacci series, or dog breeds to assess the difficulty of user stories.', 'Risks in Scrum include budget, people, sprint, product, knowledge, and capability-related risks, such as exceeding allocated budget, team members lacking appropriate skills, ill-defined user stories and epics, and uncertainties about project knowledge and capabilities.', 'Explanation of popular tools used in Scrum such as Gtub, Zoho, Trello, Jira Software, Yordix, and Version 1, emphasizing the need to understand specific project requirements before selecting a tool.', 'The concept of MMP is explained as a product with minimal features that address user requirements, reducing time to market.', 'Velocity, a metric used in Scrum, measures the amount of work completed by the team during a sprint, indicating the speed at which work is progressing.']}], 'highlights': ['Scrum emphasizes delivering working software in short cycles - Ch. 9', 'The sprint retrospective identifies past mistakes and new ways to handle them for planning the new sprint - Ch. 4', 'The responsibilities and objectives of product owner and scrum master are detailed, emphasizing the importance of maximizing ROI - Ch. 3', "Velocity is the team's capacity to complete work in a given sprint, calculated as an average of previous sprints, disregarding outliers - Ch. 6", 'The video will cover important interview questions that will help you ace your interview, providing valuable insights for career advancement - Ch. 1', 'Agile methodologies enable quick and efficient changes, reducing time and cost implications - Ch. 2', 'The significance of CI-CD in DevOps, focusing on continuous integration, delivery, and deployment - Ch. 4', 'The INVEST criteria for user stories, ensuring value creation and independence - Ch. 5', 'The scrum master promotes and supports the adoption of Scrum, ensuring the team follows Scrum values, principles, and practices - Ch. 10', 'Scrum is a project management framework for collaboration and managing unpredictability, involving Sprint Planning and Sprint Review - Ch. 10']}