- Less Overproduction (of unused functions in interface between team members)
- Less Waiting (for the only person who knows a particular area)
- Less Motion (as everyone gets more skilled)
- Fewer Defects (because two pair of eyes see better than one)
- Less Over-processing (from duplicate responsibility)
- Less Inventory (as team works on focused set of features and tasks)
- Less Transportation (handoffs inside a story)
- Less Underused talent (as everyone gets to share their skills)
Using Pair Programming to Combat Project Waste
Join the DZone community and get the full member experience.Join For Free
Microservices! They are everywhere, or at least, the term is. When should you use a microservice architecture? What factors should be considered when making that decision? Do the benefits outweigh the costs? Why is everyone so excited about them, anyway? Brought to you in partnership with IBM.
Published at DZone with permission of Johannes Brodwall, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.