Topic 11 Flashcards

1
Q

What is Lean?

A

Lean maximize customer value while minimizing waste.

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

What is the ultimate goal of lean?

A

Provide value to customer through a value creation process with zero waste

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

What are the core principles of lean?

A
  • Value: Define what it means to the customer and how to align processes to deliver it.
  • Value Stream: Map the steps involved in delivering value, from concept to customer.
  • Flow: Create smooth, uninterrupted flow in the value stream, eliminating waste.
  • Pull: Let customer demand drive production, avoid overproduction.
  • Perfection: Continuously improve processes, striving for zero waste and optimal efficiency
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the Key Lean Tools and Techniques

A
  • Value Stream Mapping (VSM): Create visual map of the value stream to identify bottleneck and waste
  • 5S Steps: Sort, Set in Order, Shine, Standardize, and Sustain
  • Kaizen: Continuous improvement through small, incremental changes.
  • Poka-Yoke: Design processes and tools to prevent errors from occurring.
  • Just-in-Time (JIT): Produce goods and services only when needed, reducing inventory and waste.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Is Kanban a continuous process?

A

YES

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

What is the background of Kanban?

A
  • From family of “pull” systems which expose bottlenecks
  • Creates slack in non-bottlenecks
  • New work is “pulled’ into system
  • Lean thinking applied to software development
  • Empirical Process
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the benefits of Kanban?

A
  • Improve productivity and predictability
  • Increase customer satisfaction
  • Reduce delivery times
  • Facilitates moving to a continually improving organization
  • Create more functional working relationships across organization
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

When is Kanban a good fit?

A

-Uneven flow of work (Large batch transfers and Unplanned and disruptive requests)
-Deferred commitment is desirable (Priorities change frequently and Constant replanning and High abandonment)
- System or workers are overburdened (Too much work-in-progress and Stressed workers)

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

What is the Kanban Core Practices?

A
  • Visualize what you do today (workflow) : Seeing all the items in context of each other can be very informative.
  • Limit the amount in progress (WIP) : This helps balance the flow-based approach so teams don’t start and commit too much work at once.
  • Enhance flow : When something is finished, the next highest thing from the backlog is pulled into play after sprint planning meeting.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is XP (Xtreme Programming)?

A

XP is one of the foremost agile methods. It aims to produce the finish result ASAP. Developers test new innovations every few weeks and receive feedback from the customer and improve them based on the feedback. It works best amongst a small group of experienced developers.

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

What are XP values?

A
  • Communication: Everyone on a team works jointly at every stage of the project.
  • Simplicity: Developers strive to write simple code bringing more value to a product, as it saves time and efforts.
  • Feedback: Team members deliver software frequently, get feedback about it, and improve a product according to the new requirements.
  • Respect: Every person assigned to a project contributes to a common goal.
  • Courage: Programmers objectively evaluate their own results without making excuses and are always ready to respond to changes.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the Pros of XP?

A
  • Fewer documentation
  • Clear code
  • Stable system
  • No overtime
  • High visibility
  • Team collaboration
  • Fast MVP delivery
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the cons of XP?

A
  • Not enough documentation
  • Unclear estimates
  • Pair programming takes longer
  • Time waste
  • Big cultural change needed
  • Co-located teams only
  • Code over design
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Difference between XP and Scrum?

A

Shorter iterations vs longer sprints
Flexible with changes vs no change within sprints
Focus on technical aspect vs Focus on managerial aspect
Customer determines the order of feature development vs Self-organized teams decide on what to work on first

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

When to use XP?

A
  • Manage a smaller team
  • Are in constant contact with your customers
  • Have an adaptable team that can embrace change
  • Are well versed in the technical aspects of coding
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is the XP life cycle?

A
  • Pull unfinished work from user stories and prioritize the most important items
  • Begin iterative honest planning
  • Stay in constant communication with all stakeholders and empower the team
  • Release work and Receive feedback
  • Return to the iterative planning stage and repeat as needed.
17
Q

What are the list of XP Practices?

A
  • Test driven development
  • Pair programming
  • Code refactoring
  • Continuous integration
18
Q

Explain what is test driven development

A

TDD involves writing an automated unit test before the code itself which is only released if the code passes the test. TDD allows developers to receive instant feedback to produce reliable software.

19
Q

Explain what is code refactoring

A

Aims to remove redundancy, eliminate unnecessary functions, increasing code coherency, and at the same time decoupling elements.

20
Q

Explain what is pair programming

A

Developer sit side by side to develop the code. One codes, the other reviews it and fixes any error and suggest improvements.

21
Q

Explain what is continuous integration

A

XP teams keep the system fully integrated at all times. They build multiple times per day. CI leads to a more stable system, a higher throughput and a higher quality software.