Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Software Projektmanagement > Scrum & Kanban > Flashcards

Scrum & Kanban Flashcards

1
Q

Scrum

A
  1. The scrum is a means of restarting play after a stoppage which has been caused by type of rule violation or error
  2. Scrum framework for software development
    - the team operates as cohesive unit working
    - frequent communication
    - realistic goal setting
  3. Provides a means for teams to establish a hypothesis of how they think something works
  4. Allows teams to incorporate practices from other frameworks
  5. Does not define techniques and technologies
  6. Is light weight and easy to learn but hard to apply
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Scrum - Events: Sprint Planning

A
  • Negotiation between product owner and team about the set of features to be realized in the next sprint
  • Effort is estimated by the team
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Scrum - Events: Daily Scrum

A

15 min meeting:
- What did you do since last daily scrum
- Are there any problems, blockers?
- What will you do until next daily scrum

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

Scrum - Events: Sprint Review

A
  • Presentation of the realized features to the product owner
  • Acceptance / rejection decision for each feature of the initial sprint backlog
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Scrum - Events: Sprint Retrospective

A

Are there improvement potentials for forthcoming sprints?

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

Scrum - Roles: Product Owner

A
  • represents all stakeholders
  • knows requirements (business and technical)
  • maintains product backlog
  • decides what to develop next (during the next sprint)
  • accepts or denies realized features
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Scrum - Roles: Sprint Master

A
  • ensures that scrum process is performed as intended
  • supports the team and the product owner
  • supports the team in improving its process and competencies
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Scrum - Roles: Development Team

A
  • self-organized interdisciplinary team
  • estimates development effort for each feature
  • there is not team leader
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Scrum - Artifacts: Product Backlog

A
  1. contains all product features and changes
    - technical and non technical ones
  2. estimated by e. g. story points or person hours / days
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Scrum - Artifacts: Sprint Backlog

A
  • contains features to be developed in one sprint
  • determined in sprint planning meeting
  • more detailed than product backlog
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Scrum - Artifacts: Product Burndown & Sprint Burndown

A

serves to monitor sprint progress and the projectʼs progress

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

Scrum - Artifacts: Release Plan

A

defines number of sprints and delivered working releases

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

Scrum - Typical Errors

A
  1. Scrum master acts as a project manager
    - is planning and controlling
    - makes decisions for team
  2. Scrum masters act as mediator
  3. Team member dominates
  4. Product owner
    - identifies activities
    - is not available
  5. Stories are too vague or too big
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Nexus Framework

A
  • All teams (the Nexus) work on the entries from a common product backlog in their sprints
  • The goal is to produce a common integrated product increment at the end of each sprint
  • Nexus extends the elements of Scrum so that they can be used at the level of all teams
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Nexus Elements - Nexus Sprint Backlog

A

Contains all entries taken from the product backlog that the teams will implement together

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

Nexus Elements - Nexus Integration Team

A
  • Product owner, scrum master, and members of the teams
  • Other people can temporarily participate in the NIT
  • Is not responsible for integration
  • Supports the teams in delivering a common integrated product increment
  • Is responsible for identifying dependencies between entries in the product backlog and reducing them as much as possible
  • All required competencies must be present in this team: Members should perform their tasks in the NIT full-time
17
Q

Nexus Elements - Refinement

A
  • Members of all teams and the product owner take part in this process
  • Product backlog entries are processed, refined and, if necessary, divided in smaller ones
  • Care must be taken to ensure that the backlog entries can be implemented by the individual teams as independently as possible and without excessive coordination effort
  • Takes place as often as necessary
  • Entries considered for the next sprint should be elaborated in sufficient detail to be distributed among teams
18
Q

Nexus Elements - Nexus Sprint Planning

A
  • The collaborative goal, the Nexus Goal, of the next sprint is defined
  • Product backlog entries for the next sprint are selected and included in the Nexus Sprint Backlog
  • Entries are divided among the teams and each team creates its team- specific sprint plan
  • If dependencies exist between the teamsʼ entries, then the teams consider them together as part of their sprint planning
19
Q

Kanban Method

A
  1. A means to design, manage, and improve flow systems for knowledge work
  2. Allows organizations to start with their existing workflow and drive evolutionary change
    - visualizing the flow of work
    - limit work in progress
    - stop starting and start finishing
  3. Can be used in any knowledge work setting, particularly
    - where work arrives unexpected
    - when you want to deploy as soon as it is ready
20
Q

Kanban Practices - Visual Workflow

A
  • Split the work into pieces, write each item on a card and put on the wall
  • Use name columns to illustrate where each item is in the workflow
  • Shows the commitment and the delivery point
21
Q

Kanban Practices - Limit Work in Progress

A
  • Assign explicit limits to how many items may be in progress at each workflow state
  • Large item can be decomposed into smaller
22
Q

Kanban Practices - Measured the Lead Time

A
  • Average time of item completion i. e. start queuing until delivery
  • Make it as small and predictable as possible for optimization
23
Q

Kanban Practices - Manage the Flow

A
  • maximize value delivery, minimize lead times
  • identify bottlenecks and blockers
24
Q

Scrum and Kanban Similarities

A
  • lean and agile
  • based on self-organizing teams
  • breaking work into pieces
  • limit work in progress
  • focus on delivering software early and often
  • optimize the process based on empirical data

Software Projektmanagement (15 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions