PD

Prep Working Software and Done

Module
Databases
Skill
[Time/Project Management]
Minutes
80

Learning Objectives

  • Provide an example of a Definition of Done for a user story
  • Provide an example of an Acceptance Criteria for a User Story

Introduction

Agile software developers focus on delivering valuable working products. It’s, therefore, good to understand what Agile working is and why it’s important. You’ll also learn about concepts that benefit you during the course and at work.

Exercises

Agile Manifesto (10 minutes)

Goal: To get familiar with Agile ways of working

Definition of ‘Done’ vs Acceptance criteria (10 minutes)

Goal: To differentiate between ‘Done’ and Acceptance criteria

Scrum requirement of ‘Done’ (20 minutes)

Goal: To get familiar with why Scrum Requires Completely “Done” Software Every Sprint

Increment and Definition of Done (10 minutes)

Goal: To get familiar with the meaning of Increment and ‘Done’

Understand the roles (30 minutes)

Goal: To understand the roles and the work they do you will need the knowledge in the class

Different types of roles will impact a team delivering valuable “working software”. Below is a list of roles with different characteristics. Research about them using any tool you would like.

You will use these roles in your exercises in class, so make sure you understand their personalities.

  • Lazy software developer
  • “Hacker” software developer
  • Bean-counter project manager
  • Salesperson
  • Proxy customer who is not the end user
  • Customer’s lawyer, who wants to verify the progress
  • Product Owner trying to maximise “value”.