Requirements - engage stakeholders

Question 1

Kanban - WIP

Answer 1

work in progress limits
restricts the number of work items that can be placed in each workflow stage at one time (each sprint)

shows bottlenecks

Question 2

lead time

Answer 2

time it takes in kanban to flow through workflow from start to completion

Question 3

throughput

Answer 3

total amount of work a team completed in a set period of time

tasks marked as in progress are not counted

Question 4

kanban cards

Answer 4

work items that need to be completed by team members

Question 5

kanban boards

Answer 5

visualizes stages an item of work goes through to completion

Question 6

scrum - product backlog

Answer 6

list of items needed to be completed for deliverable

tasks prioritized by product owner, refined by team to be selected in upcoming sprint

Question 7

scrum events

Answer 7

5 mandatory meetings during sprint -

sprint, sprint planning, daily scrum, sprint review, sprint retrospective

Question 8

scrum values

Answer 8

courage, respect, commitment, focus, openness

Question 9

scrum team

Answer 9

non-hierarchical
scrum master
product owner
developers

Question 10

sprint backlog

Answer 10

sprint goal, product backlog items, plan for how to deliver work items during sprint

Question 11

kanban

Answer 11

visualizes all work items needed to be completed. Categorizes the stages an item of work has to go through

Question 12

kanban board

Answer 12

categorizes the stages an item of work has to go through - to do, in progress, done

kanban cards contain the work information, owner, due date

Question 13

new requests in kanban

Answer 13

product owner can reprioritize project backlog to put new request at top

when team members capacity if free, they can work on it

Question 14

new requests scrum

Answer 14

new requests added to next sprint, current sprints not recommended to change

Product owner has sole authority to cancel sprint it if becomes irrelevant

Question 15

stakeholder engagement plan

Answer 15

plan on how to talk to stakeholders throughout project stages

Question 16

distributed version control system sf recommends

Answer 16

git

Question 17

distributed version control system

Answer 17

full project repository is distributed and cloned to all project member’s computers
- multiple backups
- work in feedback loops

everyone gets full access to history of changes on their local computer

Question 18

github

Answer 18

service provider for git-based version control repositories

Question 19

centralized version control system

Answer 19

central project copy is where users apply changes and updates directly on the main branch
- easier
- rely on single backup

Question 20

distributed version control system terms

Answer 20

repository - store all project files
branch - environment used by developers working on new features
commit - changes applies are submitted to the branch
merge - combine 2 branches into one
pull request - finalize merge, must be reviewed first

Question 21

who prioritizes work in scrum and kanban?

Answer 21

product owner

Question 22

where does new work go in scrum and kanban?

Answer 22

scrum - backlog for next sprint
kanban - backlog reordered continuously for next person available to work on it

Question 23

when does the work start? Scrum and Kanban

Answer 23

scrum - during sprint planning, team commits what work will be completed next sprint

kanban - as soon as a person is available

Question 24

why is there a delay? Scrum and Kanban

Answer 24

scrum - changes to sprints discouraged
kanban - top of backlog always first thing to be worked on

Question 25

how long does it take to deliver?

Answer 25

scrum - 2 weeks or more
kanban - as soon as possible

Question 26

when to use kanban

Answer 26

necessary to change directions often, minimize disruptions to a plan, and start the urgent work quickly.

Question 27

when to use scrum

Answer 27

managing a large planned project, your team can commit to a 2-week chunk of work, and the stakeholder can wait until the end of the sprint for the team to start the work.