Session 6 - Testing Requirements - Lesson plan

Last updated 5 months ago

Learning objectives

By the end of the session students will be able to:

  • Describe what requirements testing is

  • Discuss why requirements testing is important and how to can execute it

  • Apply techniques to question requirements

  • Evaluate the pros and cons of waterfall and agile approaches

Before the session

Students will be recommended to view the following videos:

Schedule

Start time

End time

Activity

Mentor notes

Resources

6:30pm

6:35pm

Introduction to the session

  • Ground rules

  • What we are covering tonight including covering before session learning material

  • Other business

None

6:35pm

7:05pm

Exercise - Waterfall requirements testing exercise

  • Team splits into BA’s and Developers

  • Mentor acts as product owner and shows BA an image and asks them to write down requirements to describe the image

  • Requirements go to Developer who draws image

This exercise gives students an experience in waterfall. We want them to discover the pros and cons for later discussion

  • When talking with the business analysts, be vague

  • Ensure that students stick to their roles

Just before the end of the exercise encourage the Students to jot down one word descriptions of how they felt the exercise went

Pictures to draw, paper, pens

7:05pm

7:20pm

Food break

7:20pm

7:35pm

Big group debrief

Clinic hosts will encourage the students to share their thoughts about

  • How did that go?

  • What went well

  • What didn’t go well

  • Why didn’t it go well?

Encourage a student to debrief

None

7:35pm

8:00pm

Big group discussion

What is Requirements testing?

Clinic hosts will mindmap ideas from students

Clinic hosts share why requirements testing is important and how to execute it (What, Why, Who and How):

  • Communication / Collaboration

  • Involving testers

  • Multiple testing activities

Use the fifteen second rule

  • Sit back and let the students submit ideas

  • If nobody speaks for 15 seconds then offer something your group discussed

Whiteboard, whiteboard pens

8:00pm

8:15pm

Big group exercise

Clinic hosts will take a website and make up a requirement based on existing functionality and present it to the group to ask questions about. Students will test this for 10 minutes.

There will be a 5 minute debrief at the end.

We want to encourage the students to suggest ideas and questions for the user story under test.

  • Use the 15 second rule: only contribute if no students have said anything for 15 seconds

  • This allows students time to think and contribute

Whiteboard, whiteboard pens

8:15pm

8:45pm

Exercise - Requirements testing exercise

  • Same exercise as before with fresh images but this time work as a team, with a new role of tester in the team, to collaborate on getting work done

This exercise gives students an experience in agile. We want them to discover the pros and cons for later discussion and comparison to the simulation 1

  • Support the students by suggesting communication techniques

  • Encourage the students to collaborate on problems and keep an eye on when students start working by themselves

Pictures to draw, paper, pens

8:45pm

8:55pm

Big group debrief

Clinic hosts will encourage the students to share their thoughts about

  • How did that go?

  • What went well

  • What didn’t go well

  • Why didn’t it go well?

  • How might we encourage this way of working in a team?

Encourage a student to debrief

Whiteboard, whiteboard pens

8:55pm

9:00pm

Wrap up

Hosts will wrap up the session and offer additional activities to carry out after the session on the Ministry of Testing Club forum

Activities after the session

  • Clinic hosts will post a requirement onto the Club and students are encouraged to test the requirement and submit their questions and observations on the forum.