REPUBULIKA YU RWANDA

Introduction

  • This training manual is dedicated to the methodologies required for effectively delivering the module titled "Project Requirement Analysis".
  • Trainees will participate in practical activities to develop competencies related to project requirements.
  • The training manual follows a Competency-Based Training and Assessment (CBT/A) model with ample practical opportunities that simulate real-life situations.
  • Activities are organized into Learning Outcomes, which are comprised of indicative content and detailed information on key competencies.
  • Trainers are encouraged to engage trainees through questioning to stimulate critical thinking, linking training to real-world applications.
  • Essential operational information includes learning hours, materials needed, and suggested methodologies.

Module Code and Title

  • SWDPR301: Project Requirements Analysis

Learning Outcomes Overview

  1. Identify Customer Needs
  2. Gather Project Requirements
  3. Determine User Requirements

Detailed Outline of Learning Outcomes

Learning Outcome 1: Identify Customer Needs

Key Competencies

  • Knowledge: Understanding concepts in data gathering, work communication, methods of data collection, interpretation of data, and organization based on customer needs.
  • Skills: Preparing data collection tools, collecting raw data, interpreting data accurately, and organizing data based on customer needs.
  • Attitudes: Collaborative, teamwork, critical thinking, and effective communication during data collection.
  • Duration: Approximately 10 hours.

Objectives

By the end of this learning outcome, trainees will be able to:

  1. Define key concepts related to project requirements.
  2. Describe the communication process in project requirements.
  3. Gather and interpret data based on customer needs accurately.
  4. Organize data effectively based on customer needs.

Required Resources

  • Equipment: Computers, Tablets, Internet access.
  • Materials: Papers, Pens, Microsoft Office (Word, Excel).

Indicative Content

  1. Data Gathering
    • Definitions
      • Internal Customer: A customer within the same organization.
      • External Customer: A customer from different organizations.
      • Data: Raw facts needing processing.
      • Information: Processed data, meaningful for decision-making.
      • Pain Points: Specific challenges faced by users.
      • User Story: Describes software or product requirements simply.
      • Research Project: A structured inquiry into a question.
    • Duration: 5 hours.
    • Tasks:
    • Group discussions on key concepts.
    • Practical activity preparing data collection tools for a school website project.

Detailed Learning Activities for Learning Outcome 1

1.1 Data Gathering

  • Introduce activity:
    • Questions for trainees:
    • Differentiate between internal and external customers.
    • Differentiate between data and information.
    • Define pain points.
    • Explain user story importance in project requirements.
    • Define research project scope.
  • Steps:
    • Facilitate group discussions and presentations.
    • Provide expert opinions for clarification.
  • Theoretical Activity 1.1.1: Description of key concepts in project requirements.
  • Conduct individual or small groups discussions to explain work communication processes and their components, including sender, encoding, message, receiver, feedback, and types of communication channels.

1.2 Interpretation of Data

  • Introduction:
    • Define data manipulation and data visualization.
    • Promote group discussions on best practices for interpreting data effectively.
  • Duration: Approximately 2 hours.
  • Utilize qualitative data from real surveys for hands-on interpretation in a guided format.

1.3 Organization of Customer Needs

  • Engage trainees with the categorization of data based on characteristics, cleansing processes, and report composition.
  • Expected Competencies:
    • Demonstrate knowledge of data organization techniques, including documentation report standards, categorization tools, and data cleansing guidelines.
  • Practice Assessment: Evaluate the completion of categorized data reports against an analytical checklist.