INTRODUCTION TO SOFTWARE ENGINEERING
AGILE SOFTWARE DEVELOPMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
Lack of feedback contributes to higher holding cost
|
|
|
Feedback and batch size are generally not connected
|
|
|
Small batch sizes enable faster feedback with lower transaction costs
|
|
|
Large batches reduce transaction cost and provide a higher return on investment
|
Detailed explanation-1: -What is the connection between feedback and optimum batch size? Lack of feedback contributes to higher holding cost.
Detailed explanation-2: -Smaller batches go through the system faster and with less variability, fostering faster learning. Moreover, since each item in the batch has some variability, larger batches accumulate more variability.
Detailed explanation-3: -Small batches ensures variability flow is reduced, accelerate feedback which is economically important and leads to less risk of delays/cost overruns. Small batches go through the system faster with lower variability.
Detailed explanation-4: -The benefits of small batches are: Reduced amount of Work in Process and reduced cycle time. Since the batch is smaller, it’s done faster, thus reducing the cycle time (time it takes from starting a batch to being done with it, i.e. delivering it), thus lowering WIP, thus getting benefits from lowered WIP.