[{"_1":2,"_46":-5,"_47":-5},"loaderData",{"_3":4,"_14":15,"_44":-5,"_45":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9,"_10":11},"user","shoppingCartId","toast","locale","en","constants",{"_12":13},"paypalClientId","AenrHU49peF-ZUH-Yq7AXLLNZYGUGlml474U16NCjB4ZznmQCEjiliN3whyuVZmkb7VxEzmTALgtKEKE","routes/_store+/_readers+/email_author.$slug/route",{"_16":17,"_43":-5},"book",{"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNTAwNTY","title","Standing on Bits","state","published","contactAuthorMethod","email","aboutText","

The current crop of Agile approaches and the Theory of Constraints have thus far been like the proverbial oil and water. Agile enthusiasts have always considered TOC as grounded in manufacturing, and thus completely inadequate to handle the peculiarities of knowledge-work, and software engineering management in particular. On the other hand, TOC practitioners, notwithstanding the decade long experience in many different fields, have a hard time accepting Agile methods, as they do not seem supported by the scientific rigor and logical reasoning that is typical of TOC; and yet they do not have a workable solution for software engineering management.

In this book we have outlined a solution that merges and takes the best of both worlds.

In particular Agile practitioners will enjoy a more financially sound way of prioritizing and selecting the work to be done; a better way to deal with multiple projects (or product development streams), stakeholders, deadlines and teams; finally resolve the conundrum of dependency management at scale by collapsing the combinatorial explosion of dependency networks in a simple linear queue in front of the Constraint.

Likewise TOC practitioners, by leveraging on the techniques that are well established in Critical Chain Project Management, will be able to create the behavioral habits and response patterns that are typical of Agile settings. By using the Work Execution Signals (Aging Signals and Buffer Signals), we trigger intense, frequent and engaging collaboration between all players, leading to an environment that unleashes the organization's collective intelligence via co-creation and social learning.

The instrumentation to collect Flow Metrics at the team level enabled us to identify and reason in terms of the Work Flow Constraint, Work Process Constraint and Work Execution Constraint, bringing together information from the past, the outlook of the future and the current conditions of execution. By understanding and observing the interactions between the three, we create the setting for effective Constraints Management even in the field of software engineering management.

With the solution that we have outlined, Agile and TOC can now co-exist, and work better together. Any other Agile or TOC concept can be leveraged on top of this solution too.

Whether you have an Agile or a TOC background, you will learn about a new way to handle software engineering management at scale.

","authors",[30],{"_18":31,"_32":33,"_5":34},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci81Mjg4OA","name","Steve Tendon",{"_35":36},"avatar",{"_37":38,"_39":40,"_41":42},"url","https://d308did4coypzi.cloudfront.net/avatars/50295/medium/steve-kob-3.jpg?1545673569","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the Author