Agile & lean frameworks Flashcards
What are the 8 wastes of the lean framework?
Defects, overproduction, waiting, non-effective use of time and talent, transport, inventory, motion, and excessive processing.
What is the goal of lean?
To reduce project waste by removing the identified waste
Lean thinking
Identify value, map the value stream, create flow, establish pull, and seek perfection
Identify value
Identify value from the customer’s point of view
Map the value stream
Map the process of value delivery from the time the customer orders to when the product or service is delivered. Display and reduce nonvalue-added activities that don’t directly add value to the customer.
Create flow
Make the value-creating steps in a tight sequence so the product flows smoothly toward the customer.
Establish pull
Let customers pull value from the previous upstream activity when needed—don’t overproduce or create large batches of work.
The house of lean
Everything is done to improve the customer-driven quality, delivery, and cost metrics.
What is a pull system?
Having a small inventory (similar to a supermarket shelf) that customers can pull from when they need it. Increases flow for products to be produced quickly.
What is continuous flow or “one piece” flow
An item moves continuously through the system without being blocked or stopped until it reaches the customer.
What is Takt time?
The “heartbeat” of the process, where value can be created only as fast as the slowest part of the process. Reduce that time, and the whole process will improve.
What is error-proofing? “Poke yoke”
We try to make it impossible to make mistakes to reduce defects.
What is the “plan do check act?” “Deming cycle”
Where we plan an improvement, do it, check the results and then adjust, continually improving until perfection.
Line balancing
Splitting up and separating long processes into smaller consecutive processes. When each one is full and flowing continuously, the overall value is created faster.
Stop and notify
As soon as a defect is found we stop and swarm around the issue to fix it.
Error detection
Autonomation or jidoka where an item cannot proceed if a defect is found.
Standard process or standard operating procedures
Make sure the team is all on the same page.
Go look and go see
Genchi Genbutsu meaning we go and see the work and any issues first hand, where the work is done.
Visual management
Making anything our customers need to know visible. Like items in queue left to complete.
Informed decision making
Where we make decisions based on data, and seeing the work first hand.
PIPS
Buckets most issues arise from- perfect for brainstorming root causes. People information process system
Customer first
Creating value as determined by the customer
Respect for people
Ensuring our team understands their work, have control over their outcomes, that meets their talent
Continuous improvement
Aka kaizen, small improvements that anyone can perform anytime.
Scrum
Emphasizes teamwork made up of product owner, scrum master, and the team.
Scrum product owner
Represents the customer
Scrum master
Facilitates ceremonies and problem solving
Daily scrum
Used to meet daily to assess progress and raise blockers
End sprint with retrospective
Reflect on how the team can improve
At the end of a sprint the work should be a usable __________
Increment
extreme Programming (XP)
Core values, core activities, core practices
Core values (extreme programming)
Communication, simplicity, feedback, respect, and courage
Simplicity
Starting with the simplest solution, removing what is not needed to get a similar outcome, reducing dependencies in the system, refactoring and reducing technical debt.
