Lecture 7: Scrum, Domain Analysis, Requirements Analysis

Question 1

What are the different scrum roles?

Answer 1

Product owner
Scrum Master
Development Team

Question 2

What are the traits of a product owner?

Answer 2

Defines the features of the product
Decides on release date and content
Prioritizes features
Adjusts features and priority every iteration, as needed
Accepts or rejects work results

Question 3

What are the traits of a scrum master?

Answer 3

Represents management to the project
Responsible for ensuring adherence to scrum practices
Removes impediments
Ensures that the team is fully functional
Shields team from external interference

Question 4

What are the traits of the development team?

Answer 4

Members are assumed cross-functional
Only title for member is “developer”
No sub-teams
Optimal size is 3-9 members

Question 5

What is a sprint?

Answer 5

“Heart” of scrum
Usually one month or less, consistent development throughout
“Done”, usable product increment is created
New sprint starts immediately after previous ends
Quality attributes don’t change
Scope can be clarified/re-negotiated

Question 6

What is a sprint planning meeting?

Answer 6

Work to be performed in upcoming sprint is planned
Suggested meeting length is 8 hours for a one month sprint
What will be delivered and how will the work get done?

Question 7

What are deliverables?

Answer 7

Product owner presents a list of items to complete, team develops a sprint goal, considering the backlog, capacity, and past performance

Question 8

What is in the sprint backlog?

Answer 8

Selected product backlog items
Estimated time to complete each item
Assigned tasks to individual members

Question 9

What is the goal of a daily scrum meeting?

Answer 9

15 minutes to synchronize and plan for the next 24 hours
Same time, same place
Questions: What was accomplished, what will be done before next meeting, and what obstacles are in the way?

Question 10

What is the goal of the sprint review meeting?

Answer 10

Present accomplishments
Form of a demo of new features or progress
Informal, entire team participation

Question 11

What is the sprint retrospective?

Answer 11

Opportunity to reflect and plan for improvements during the next sprint

Question 12

What is a project charter?

Answer 12

Problem statement
Project objectives
Stakeholders
Deliverables

Question 13

What is a product backlog?

Answer 13

Ordered list of everything that might be needed in the product (source of requirements)
Product owner is responsible for the backlog
Never complete
Lists all features, function, requirements, enhancements, fixes
Format: As a, I want, so that” (called user stories)

Question 14

What is a burn down chart?

Answer 14

Graphical representation of work left to do vs. time left in which to do it

Question 15

What are some scrum criticisms?

Answer 15

Assumes you can estimate task duration
A lot of meetings
Difficult to collaborate with outside groups
Assumes development will be ongoing

Question 16

What do the terms “Greenfield” and “Brownfield” mean?

Answer 16

Greenfield: From scratch
Brownfield: Must work with existing systems

Question 17

What is design?

Answer 17

Deciding how the requirements should be implemented using available technology

Question 18

What is domain analysis?

Answer 18

Process by which a software engineer learns about the domain (general field of business or technology in which the software will be used) to better understand the problem
Benefits: Faster development, better system, easier to anticipate future modifications

Question 19

What are the different types of requirements?

Answer 19

Real: functional and performance
Constraints: non-functional (all software must be in C)
Possible: non-measurable, subjective (look good)
Probably not: Expectations, wishes, desires

Question 20

How do you gather requirements?

Answer 20

Observation: Read documents and discuss requirements with users, shadow potential users
Interviewing: Ask about specific details, stakeholder’s vision, etc.
Prototype: Draw pictures and show them to users, develop a mock-up UI

Question 21

How do you explore the requirements?

Answer 21

Need to determine what the system is compared to the world
Can change: System
Can influence: Boundary
Can’t change: World

Question 22

What are user stories?

Answer 22

Short, simple descriptions of a feature told from the perspective of the person who wants the feature, usually a user or a customer
“As a “type of user”, I want “some goal”

Question 23

Why are user stories helpful?

Answer 23

Help define the scope of the system, help plan, form basis for test cases

Question 24

What is a use case?

Answer 24

A typical sequence of actions that a user performs to complete a given task
Cover the full sequence of steps from beginning to end
Describe the user’s interaction with the system
As independent from UI design as possible

Question 25

What do use case diagrams look like?

Answer 25

Use case: horizontal ellipse
Actor: Stick figure, person, organization or external system
Associations: Lines, connect actors and use cases

Question 26

What are use case extensions?

Answer 26

Make optional interactions explicit
Handle exceptional cases
Think “hardware interrupt”

Question 27

What are use case generalizations?

Answer 27

Represent several similar use cases
One or more specializations provides details of the similar use cases
Ex: Manage Personal Account and Manage Business Account inherit behavior from Manage Account but add specific steps

Question 28

What are use case inclusions?

Answer 28

Allow one to express commonality between several use cases
Included in other use cases
Represents the performing of a lower-level task with a lower-level goal

Question 29

What is the purpose of exploring requirements?

Answer 29

Reduce the uncertainty about what was needed and not requested and what was asked for and not needed

Question 30

What are the steps to managing requirements?

Answer 30

Review them
Track them
Verify them
Control the changes to them

Question 31

What are the considerations when reviewing requirements?

Answer 31

Benefits that outweigh the costs
Important
Unambiguous
Consistent, etc.