0% found this document useful (0 votes)
253 views

Client Needs and Software Requirements - Course Map PDF

This four-week course covers techniques for eliciting and expressing software requirements from clients, including: 1) Creating clear requirements to drive effective software development and visualizing client needs with prototypes. 2) Maximizing effective client interactions and adapting to changing product requirements. 3) Upon completion, students will be able to elicit requirements, analyze client needs, write requirements documents, and define quality acceptance criteria.

Uploaded by

Hahne Mann
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
253 views

Client Needs and Software Requirements - Course Map PDF

This four-week course covers techniques for eliciting and expressing software requirements from clients, including: 1) Creating clear requirements to drive effective software development and visualizing client needs with prototypes. 2) Maximizing effective client interactions and adapting to changing product requirements. 3) Upon completion, students will be able to elicit requirements, analyze client needs, write requirements documents, and define quality acceptance criteria.

Uploaded by

Hahne Mann
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Course Description

This four-week course covers practical techniques to elicit and express software requirements from client interactions. Upon successful SOFTWARE PRODUCT MANAGEMENT Specialization Development Team:
Ken Wong
completion of this course, you will be able to:
Kari Rasmussen
• Create clear requirements to drive effective software development
• Visualize client needs using low-fidelity prototypes
Course 3: Client Needs & Software Rus Hathaway
• Maximize the effectiveness of client interactions
• Adapt to changing product requirements
Requirements Bradley Poulette
Morgan Patzelt

Module 1 Module 2 Module 3 Module 4


Introduction to Requirements User Interaction Writing Requirements Quality Requirements

Introduction: Specialization Preview 2 minutes Lesson 3.2.1: Restaurant Scenario 1 minute Lesson 3.3.1: Agile Requirements 6 minutes Lesson 3.4.1(A): Criteria for User Stories 11 minutes
• Recognize that requirements is an aspect of Agile • Summarize the criteria for user stories
Introduction: Introduction to Client Needs & Client Needs 2 mins Lesson 3.2.2(A, B): User Considerations 17 minutes • Recall the basic principles of Agile 14.1.1 Summarize the concept of correct
• Summarize the concept user 14.1.2 Summarize the concept of complete
Course Resources: Client Needs & Software Requirements - - List the types of users (primary, secondary, tertiary) 14.1.3 Summarize the concept of consistent
Lesson 3.3.2(A, B): User Stories 18 minutes
Course Notes & Glossary - Summarize the term stakeholder 14.1.4 Summarize the concept of clear
• Generate a user story
- List the characteristics of users 14.1.6 Summarize the concept of traceable
- Summarize the concept of a user story
Lesson 3.1.1(A): What is a Requirement/Requirement Activities • List some issues that may arise with user interactions 14.1.7 Summarize the concept of verifiable
- Recognize what makes a good user story
16 minutes • List types of human limitations • Recognize if user stories meet the criteria of feasible,
- Recall the purpose of user stories
• Summarize the concept of a software requirement manageable and simple
• Deconstruct a user story
• Summarize the types of activities associated with requirements: Discussions: Cultural Differences - Recognize when a user story is too large
- Summarize the concept of elicitation - Analyze a user story Reading: Ambiguous Requirements Study Guide
- Summarize the concept of requirements analysis
- Summarize the concept of requirements management Lesson 3.2.3(A): Involving Clients 14 minutes
• Summarize how to properly interact with clients Peer Graded Assignment: User Stories Assignment Lesson 3.4.2: Ambiguous Requirements 23 minutes
- Summarize the concept of requirements prioritization
• Summarize how to create a list of requirements Passing threshold - 80% Course weight 5% • Determine if a user story is free of ambiguity
- Summarize the concept of requirements expression
• Summarize the key aspects of customer interactions 15.1.1 Summarize the concept of ambiguous requirements
• List key questions to enable elicitation Reading: User Stories Assignment Proposed Solution (Locked) 15.1.2 Recognize if the requirement is detailed enough
Lesson 3.1.2(A, B, C, D): Types of Requirements 25 minutes
15.1.3 Recognize ambiguous terms
• Differentiate between the different types of requirements
Lesson 3.3.3: Acceptance Tests 8 minutes 15.1.4 Clarify ambiguous terms
- Summarize the concept business requirement Reading: Good Questions to Ask Your Client
- Summarize the concept business rule • Generate an acceptance test from user stories
- Summarize the concept user requirement - Summarize the concept of an acceptance test Discussions: Ambiguous Requirements
Lesson 3.2.4: Use Cases 9 minutes - Recall the format of an acceptance test
- Summarize the concept functional requirement
• Generate a use case
- Summarize the concept non-functional requirement Reading: Ambiguous Requirements Quiz Pre-Reading
- Summarize the concept of a use case
- Summarize the concept external interfaces Lesson 3.3.4(A): Product Backlog 12 minutes
- List what goes into a use case description (name, actors,
- Summarize the concept physical setting • Generate a backlog
goal, trigger, pre-condition, post-condition, basic flow, exceptions, Peer Graded Assignment: Ambiguous Requirements Quiz
- Summarize the concept developer constraints - Summarize the concept of a product backlog
qualities) Passing threshold - 80% Course weight 5%
- Identify priorities of user stories (by client)
Quiz: Module 1 Practice Quiz – Ungraded - Recall how backlogs fit into Scrum iteration and release
Lesson 3.2.5: Wireframes 6 minutes plans Lesson 3.4.3: Course Summary 5 minutes
(15 questions on types of requirements)
• Summarize how a wireframe works • Summarize the concepts learned in the course
Passing threshold - 80% Course weight 0%
• Deconstruct requirements from a wireframe
Lesson 3.3.5: Story Maps 8 minutes
• Assemble a story map Reading: Module 4: Supplemental Resources
Lesson 3.1.3: Controlling Scope 12 minutes
• Recognize that changes to software requirements are common Peer Graded Assignment: Wireframes Assignment - Summarize the concept of a story map
and need to be accounted for Passing threshold - 80% Course weight 5% - Recall the structure of a story map Module Assessment: Quiz 4 – Graded (8 questions)
• Summarize the concept of vision - Recognize the application of a story map Passing threshold - 70% Course weight 10%
• Summarize the concept of scope Lesson 3.2.6: Storyboards 9 minutes - Recognize if a story map has missing aspects or
• Summarize the concept of managing expectations • Summarize how a storyboard works inconsistencies
Course Assessment: Course Final Quiz – Graded (32 questions)
• Summarize the concept of defending against scope creep and • Deconstruct requirements from a storyboard - Summarize benefits of story maps
Passing threshold - 75% Course weight 40%
why it’s important
Reading: Module 2: Supplemental Resources Reading: Module 3: Supplemental Resources
Discussions: Week 4
Lesson 3.1.4: Requirements and Design 6 minutes
• Differentiate between design and requirements Module Assessment: Quiz 2 – Graded (8 questions) Module Assessment: Quiz 3 – Graded (8 questions)
Passing threshold - 70% Course weight 10% Passing threshold - 70% Course weight 10%
Reading: Module 1: Supplemental Resources
Discussions: Week 2 Discussions: Week 3
Module Assessment: Quiz 1 – Graded (8 questions)
Passing threshold - 70% Course weight 15%

Discussions: Week 1
NOTE: The lesson number refers to the course, module, and lesson. For example, lesson 1.2.3 refers to the first course, second module, third lesson.

You might also like