04 Lecture Flashcards

1
Q

What are the features of a Defined Process?

A
  • Planned
  • Follows strict rules
  • Avoids deviations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the features of an Empirical Process?

A
  • Not entirely planned

- inspect and adapt

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Define the Defined Process Control Model

A
  • Requires that every piece of work is completely understood

- Given a well-defined set of inputs, the same outputs are generated every time

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Define the Empirical Process Control Model

A
  • Imperfectly defined process, not all pieces of work are completely understood
  • Expects the unexpected: control and risk management is exercised through
    frequent inspection
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

When to use the Empirical Process Control Model

A
  • Change is frequent and cannot be ignored

- Change of requirements, change of technology, change in the organization, people change too.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Definition of scrum in agile processes

A

Scrum is a technique that deals with interruptions (change)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the 3 Scrum Artifacts

A

1) Product Backlog
2) Sprint Backlog
3) Potentially Shippable Product Increment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is the Product Backlog?

A

List of requirements for the whole product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the Sprint Backlog?

A

List of requirements and tasks for one iteration (“Sprint”)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is the Potentially Shippable Product Increment?

A

Release to the Product Owner that contains all results of the current Sprint

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Which Scrum Meetings do you know?

A

1) Project Kickoff Meeting -> Product Backlog
2) Sprint Planning Meeting -> Sprint Backlog
3) Daily Scrum Meeting (Standing)
4) Sprint Review Meeting -> Potentially Shippable Product Increment
5) Retrospective

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the 3 Roles in the Scrum Team

A

1) Scrum Master
2) Product Owner
3) Developer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the responsibilities of the Product Owner?

A
  • Defines the product

- Responsible for results

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are the responsibilities of the Scrum Master?

A
  • Resolves impediments

- Responsible for the process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the responsibilities of the Developer?

A
  • Self-organized and cross-functional

- Realizes the product increments

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Define a Sprint

A
  • Time-box (up to one month) during which the team creates a potentially shippable product increment
  • Sprints have consistent durations throughout a project
  • A new Sprint starts immediately after the conclusion of the previous Sprint
17
Q

What is the Product Backlog

A
  • Collection of items (e.g. user stories, scenarios, etc.) prioritized by the Product Owner
  • The Product Backlog can always be changed and reprioritized during the projects
  • Created on the basis of the problem statement during the Project Kickoff Meeting or in the phase before the actual project starts
18
Q

What priorities do you have in the Product Backlog?

A
  • Critical
  • Major
  • Minor
  • unimportant

(Done by the product owner)

19
Q

What levels of difficulties are there

A
  • S
  • M
  • L
  • XL
20
Q

Properties of a good User Story

A
  • Independent
  • Negotiable
  • Valuable and Vertical
  • Estimable
  • Small
  • Testable
21
Q

The User Story Template

A

As ,
I can
so that

22
Q

Define is an Acceptance Criteria

A

Conditions that a software product must satisfy to be accepted by a user, customer or other stakeholders

23
Q

Define Scenarios

A

An instance of a use case. A scenario represents a concrete sequence of interactions between one or more actors and the system.

24
Q

Relation between User Stories, Use Cases and Scenarios

A
  • Scenarios are typically created during Analysis
  • Use Cases and Scenarios typically cover a larger scope and are more formal than User Stories
  • User Stories are usually created during requirements elicitation