Requirements - engage stakeholders Flashcards
Kanban - WIP
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
lead time
time it takes in kanban to flow through workflow from start to completion
throughput
total amount of work a team completed in a set period of time
tasks marked as in progress are not counted
kanban cards
work items that need to be completed by team members
kanban boards
visualizes stages an item of work goes through to completion
scrum - product backlog
list of items needed to be completed for deliverable
tasks prioritized by product owner, refined by team to be selected in upcoming sprint
scrum events
5 mandatory meetings during sprint -
sprint, sprint planning, daily scrum, sprint review, sprint retrospective
scrum values
courage, respect, commitment, focus, openness
scrum team
non-hierarchical
scrum master
product owner
developers
sprint backlog
sprint goal, product backlog items, plan for how to deliver work items during sprint
kanban
visualizes all work items needed to be completed. Categorizes the stages an item of work has to go through
kanban board
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
new requests in kanban
product owner can reprioritize project backlog to put new request at top
when team members capacity if free, they can work on it
new requests scrum
new requests added to next sprint, current sprints not recommended to change
Product owner has sole authority to cancel sprint it if becomes irrelevant
stakeholder engagement plan
plan on how to talk to stakeholders throughout project stages
distributed version control system sf recommends
git
distributed version control system
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
github
service provider for git-based version control repositories
centralized version control system
central project copy is where users apply changes and updates directly on the main branch
- easier
- rely on single backup
distributed version control system terms
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
who prioritizes work in scrum and kanban?
product owner
where does new work go in scrum and kanban?
scrum - backlog for next sprint
kanban - backlog reordered continuously for next person available to work on it
when does the work start? Scrum and Kanban
scrum - during sprint planning, team commits what work will be completed next sprint
kanban - as soon as a person is available
why is there a delay? Scrum and Kanban
scrum - changes to sprints discouraged
kanban - top of backlog always first thing to be worked on
how long does it take to deliver?
scrum - 2 weeks or more
kanban - as soon as possible
when to use kanban
necessary to change directions often, minimize disruptions to a plan, and start the urgent work quickly.
when to use scrum
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.
