Prioritizing Project Requirements

Objectives

1. Understand the concept of project requirements and their importance in project management.
2. Learn how to prioritize project requirements using different methods and tools.
3. Apply the acquired knowledge to solve practical problems related to project requirements prioritization.

Introduction (10-15 minutes)

1. Review of Previous Content: Start the lesson by briefly reviewing the concepts of project management and the importance of defining clear project requirements. Use real examples to illustrate how project requirements affect the success or failure of a project.

2. Problem Situations: Present two problem situations to the students:

   • Situation 1: "Imagine you are managing a project to create a new website for a company. The client has provided you with a long list of requirements, but they are not in order of importance. How would you decide which requirements to prioritize?"

   • Situation 2: "You are part of a team developing a new mobile app. The team has defined several requirements, but there is a limited budget and time. How would you prioritize the requirements to ensure the app is delivered on time and within budget?"

3. Contextualization: Explain the importance of prioritizing project requirements in the real world. Mention how this skill is essential for project managers, software developers, product designers, among others. Use examples of real projects to illustrate how prioritizing requirements can affect project outcomes.

4. Introduction to the Topic: Finally, introduce the topic of the lesson - prioritizing project requirements. Explain that students will learn different methods and tools to prioritize requirements and that they will have the opportunity to apply this knowledge in practical activities.

   • Curiosity: Share a curiosity about the topic. For example, you can mention that one of the most widely used methods for prioritizing requirements is the MoSCoW method, which divides requirements into four categories: Must have (Must have), Should have (Should have), Could have (Could have), and Would like (Would like).

5. Gaining Students' Attention: To spark interest in the topic, share some real-world success stories. For example, you can mention how the proper prioritization of requirements helped a company reduce development time and costs, or how the lack of prioritization led to the failure of a project.

Development (20-25 minutes)

1. Theory

   1.1. Project Requirements: Start by explaining what project requirements are. Highlight that they are the conditions that must be met for the project to be considered a success. Use a simple and clear example to illustrate the concept. For instance, if the project is developing a new mobile app, the requirements may include having a user-friendly interface, being compatible with iOS and Android, and having a fast and secure performance.

   1.2. Prioritizing Requirements: Next, explain the importance of prioritizing project requirements. Emphasize that, in most cases, it is impossible to meet all requirements due to constraints such as budget, time, and resources. Therefore, it is crucial to identify which requirements are most important and should be addressed first.

   1.3. Methods and Tools for Prioritization: Introduce the methods and tools commonly used for prioritizing project requirements. Explain that each method has its strengths and weaknesses, and the choice of method depends on the project's characteristics and the team's preferences.

    1.3.1. **MoSCoW Method**: Start with the MoSCoW method, which was mentioned in the introduction. Explain that this method divides requirements into four categories: Must have (Must have), Should have (Should have), Could have (Could have), and Would like (Would like). Each category is given a different level of priority.
   
    1.3.2. **Kano Model**: Next, present the Kano model, which is based on the concept of customer satisfaction. Explain that this model divides requirements into five categories: Basic (Basic), Expected (Expected), Exciting (Exciting), Indifferent (Indifferent), and Disappointing (Disappointing). 
   
    1.3.3. **Weighted Scoring**: Finally, introduce the weighted scoring method, which quantifies the importance of each requirement. Explain that this method assigns a score to each requirement based on its importance and difficulty of implementation. 
   

   1.4. Choosing a Method: Conclude the theoretical part by explaining how to choose the most suitable method for a project. Emphasize that it is important to consider the project's characteristics, the team's experience, and the stakeholders' preferences.

2. Practice

   2.1. Practical Activity 1 - MoSCoW Method: Divide the class into groups and give each group a list of project requirements. Ask them to prioritize the requirements using the MoSCoW method. After the activity, ask a representative from each group to present the group's prioritization and explain the reasoning behind it.

   2.2. Practical Activity 2 - Kano Model: Repeat the previous activity, but this time using the Kano model.

   2.3. Practical Activity 3 - Weighted Scoring: For the third activity, provide each group with a set of criteria and ask them to assign a score to each requirement based on the criteria.

   2.4. Group Discussion: After the activities, conduct a group discussion. Ask students about the difficulties they encountered, the strategies they used, and what they learned from the activities.

   2.5. Teacher's Feedback: Finally, provide feedback to the students. Highlight the positive aspects of the activities and suggest areas for improvement.

Return (10-15 minutes)

1. Theory Review (5-7 minutes): Start this stage by briefly reviewing the theoretical concepts covered in the lesson. Remind students about the importance of project requirements and the need to prioritize them to achieve project success. Go over the methods and tools introduced - MoSCoW, Kano model, and weighted scoring - and emphasize the key points of each.

2. Practical Connection (3-5 minutes): Next, connect the theory to practice. Ask students to reflect on the practical activities they performed and how they applied the theoretical concepts. Encourage them to identify the advantages and disadvantages of each method they used and to discuss which method they would prefer to use in a real project.

3. Individual Reflection (2-3 minutes): Now, ask students to reflect individually on what they learned in the lesson. Pose some questions to guide their reflection, such as:

   • What was the most important concept learned today?
   • What questions have not been answered yet?
   • How can you apply what you learned today in your life or future career?

4. Sharing Reflections (3-5 minutes): After the reflection time, ask students to share their answers. This can be done in a roundtable format, where each student has the opportunity to speak. Encourage students to listen to their classmates' reflections and to ask questions or make comments.

5. Teacher's Feedback (2-3 minutes): Finally, provide feedback to the students on their reflections. Highlight the positive aspects of their answers and suggest areas for improvement. Encourage students to continue reflecting on what they learned and to apply their knowledge in future situations.

Conclusion (5-10 minutes)

1. Summary of Contents (2-3 minutes): Start the conclusion by summarizing the main points covered in the lesson. Remind students about the definition of project requirements and the importance of prioritizing them. Reiterate the three methods introduced - MoSCoW, Kano model, and weighted scoring - and highlight the strengths and weaknesses of each one.

2. Theory-Practice Connection (2-3 minutes): Explain how the lesson connected theory to practice. Mention the practical activities that were carried out and how they allowed students to apply the theoretical concepts. Emphasize that understanding the theory is essential, but the ability to apply it in practice is what truly matters.

3. Additional Materials (1-2 minutes): Suggest additional materials for students who wish to deepen their knowledge on the subject. This could include books, articles, videos, online courses, among others. For example, you could recommend the book "User Story Mapping" by Jeff Patton, which discusses the MoSCoW method in detail.

4. Relevance of the Subject (1-2 minutes): Finally, emphasize the importance of the subject presented for the students' daily lives. Explain that even if they do not become project managers, the ability to prioritize requirements is useful in many situations. For example, when planning a trip, they need to decide which places they want to visit (requirements) and in which order (prioritization). Similarly, when studying, they need to decide which topics are most important or interesting to them.

5. Closure (1 minute): Conclude the lesson by thanking the students for their participation and encouraging them to continue studying the subject. Remind them that learning is a continuous process and that practice is essential for mastering any concept.