Lean development

Question 1

7 key principles of lean software development

Answer 1

1) Eliminate Waste 2. Build Quality In 3. Create Knowledge 4. Defer Commitment 5. Deliver Fast 6. Respect People 7. Optimise The Whole

Question 2

Lean over other

Answer 2

k

Question 3

22 lean tools

Answer 3

1

Question 4

See the whole

Answer 4

1) All the working parts
2) Everything integrating
3) Focus on overall system performance
4) Important in contracting, not individual needs drive the focus

Question 5

Eliminate waste

Answer 5

1) anything does not add value
2) Anything not needed immediately
3) Handing development one group to another

Question 6

Amplify learning

Answer 6

1) Communicate early and often
2) Decision based on empirical finding not on assumptions
3) Repeat throughout the process
4) Continually improve
5) Expect and embrace mistake

Question 7

Decisions as late possible

Answer 7

1) Avoid locking in decision (design should be flexible)

2) Build a capacity for change in the system

Question 8

Deliver as soon as possible

Answer 8

1) Quick feedback

2) Discovery cycle is critical (shorter the cycle, more can be learned)

Question 9

Empowering the team

Answer 9

1) Developers can let others know when works needs to be done
2) Not possible for central authority to direct
3) Pull mechanism, self organizing, do whatever it takes to resolve the challenges

Question 10

Build integrity into the system

Answer 10

1) Whatever delivered is what wanted
2) System maintain usefulness
3) Adaptable

Question 11

Tools to eliminate waste -Seeing waste

Answer 11

1) partially done work
2) Extra processes - someone waiting for the output from the process
3) No extra features
4) Task switching
5) Waiting (not able to realize value)
6) Motion (co location), not only people
7) Defects (find as soon as it occurs, so test immediately)

Question 12

Tools to eliminate waste -Value stream mapping

Answer 12

1) Flow of work (all process steps) -shows waiting and unnecessary steps

Question 13

Principle 2-Amplifying

Answer 13

1) Feedback
2) Immediate customer not a future customer
3) Increase frequency loop in problem area
4) Iteration
5) Synchronization (feature based development)
6) Set based development(develop multi options, communicate constraints, letting solutions emerge)

Question 14

Principle - 3, Decide as late

Answer 14

1) Options thinking
2) last possible moment
3) Making decisions (breadth first, depth first)

Question 15

Option thinking

Answer 15

1) Maximize reward until more information available
2) Flexibility to respond to change
3) Fact based decision

Question 16

last possible moment

Answer 16

1) Concurrent development

Question 17

Making decisions

Answer 17

1) breadth first - how details most likely emerge, late commitment, business expected to evolve
2) depth first - early commitment, focus on particular area

Question 18

Principle 4 - Deliver as fast as possible

Answer 18

1) pull system
2) Queuing theory tool
3) Cost of delay

Question 19

Pull system development

Answer 19

1) Kanban is most often used tool
2) display task progress
3) increased team motivation and cross functionality

Question 20

Queuing theory tool

Answer 20

1) remove project bottlenecks
2) minimizes task wait time inside a process
3) goal is minimize Cycle time

Question 21

Cost of delay

Answer 21

1) Minimize cost of delay
2) Understand relationship between cost and time
3) Only delay as long as profit is not affected

Question 22

Principle 5 - Empower the team

Answer 22

1) Self Determination
2) Motivation
3) Leadership
4) Expertise

Question 23

Self determination tool

Answer 23

1) Developers chose how and when to do work
2) Team leaders enforces standards, coordinate work
3) Overall team is responsible

Question 24

Motivation

Answer 24

1) Encourage, recognize and reward creativity and initiative

2) Building blocks: belonging, safety, competence, progress

Question 25

Leadership

Answer 25

1) Coach and facilitator
2) how to use tools and to work as whole
3) Facilitate activities so team can focus

Question 26

Expertise

Answer 26

1) Each member as different level of expertise
2) Encourage to learn for cross functionality
3) Share expertise by knowledge transfer

Question 27

Principle 6 Build integrity in

Answer 27

1) Perceived integrity
2) Conceptual integrity
3) Refactoring
4) Testing

Question 28

Perceived integrity

Answer 28

1) perceived by user of the system
2) affected by deliver, access, intuitiveness, cost
3) cost

Question 29

Conceptual integrity

Answer 29

1) Central concept work together as unit
2) prerequiste for perceived integrity
3) emerges as system matures and evolves
4) helps to illustrate system purpose

Question 30

Refactoring

Answer 30

1) For continuous improvement
2) refactor and realign for conceptual integrity
3) key method for avoiding waste

Question 31

Principle 7 see the whole tools

Answer 31

1) Measurements

2) Contracts

Question 32

Measurements

Answer 32

1) Information measurement (not performance measurement)
2) Don’t attribute defects to the developer
3) collaborate as team to identify defects (information measurement)

Question 33

Contracts

Answer 33

1) Time and material
2) Multistage (master contract, work orders)
3) Target cost (solution to meet target cost, limit cost)
4) Shared benefit contract (mutual benefits)

Question 34

In times of trouble

Answer 34

1) find and fix its root cause
2) identify biggest concern and focus on removing it
3) move up one level and improve

Question 35

lean vs scrum

Answer 35

1) ability using specific set of engineering
2) cost is important
3) when driven at process level