4.8: 4 Review and an Exercise - Video Tutorials & Practice Problems

<v ->Now let's review what we learned in lesson four.</v> Today we discussed how to define requirements in Agile and how this is different from traditional methodologies. We also defined ways to prioritize this backlog to create a list of discrete user stories. User stories reflect user needs and address them feature by feature. We also emphasized that the development team takes an active role in defining acceptance criteria, and acceptance criteria are used in building taste cases for the product. And finally, we spoke about the story mapping technique that allows for a holistic view of Agile requirements in a well-refined backlog. And as we do in the end of each lesson, I am offering you a five question quiz. I will show and read the question. Please pause the video after you see the question and write down your answer before restarting your video. And then I will reveal the answer for you. So here are questions one through five. Question one, which is not part of requirements measurement in traditional project management? Please write down the answer. And now let me reveal the correct one. Stakeholder analysis. Stakeholder analysis is part of the waterfall project delivery, but it is not part of the requirements analysis or requirements management. The next question is what is the most accurate description of a product backlog? Please select the letter, pause your video, write it down. And now let me show the correct answer. Prioritized list of product features, which may be expressed as user stories. As we said, it doesn't have to happen as user stories because Agile is a framework. It is not a prescriptive methodology that tells you exactly how you're supposed to do your work. Let's go to question three. What is the primary difference between a product backlog and a software requirements document, SRS? We use the latter in waterfall or traditional project management. Please pause your video, write the letter. And now let me reveal the correct answer. The answer is the product backlog is iterative and SRS has to be finalized and signed off before the development starts. That creates change management process in traditional project management, and in Agile, the changes manage organically in the end of every sprint and throughout the delivery life cycle because your product backlog is refined continuously. Now let's go to question four. What does INVEST mean as related to a user story? How do you invest in the user story? Please write your answer, pause the video. And now let me reveal the correct answer. It's a mnemonic to remember features of the user story. Now take a pause and think. Do you remember what each of the letters stands for? If not go, back and review the lesson. Now let me move to question five. The benefits of story mapping do not include which of the following? Please review the answers, write down the correct letter, and pause the video before I reveal the correct answer. And the answer is creating a comprehensive software requirement specification. As we just discussed, SRS is part of the traditional project management, not of the story mapping, which is specific to Agile product backlog development and management. I hope you got all the answers correctly. And if you did, you are ready to move to lesson five.