You Kanbanized your development process and setup a perfect workflow. You see the flow and feel its power. You even measure cycle time and want to reduce it. But it is not as easy as expected. Some problems in your development process are hard to find and are revealed on team level.
I’m reading books on TRIZ and becoming enthusiastic about its potential for software development industry. Yes, it is not clear how to apply it directly, since TRIZ focuses on technical systems, but I believe we can apply general rules and even have solution patterns in the future. TRIZ has several patterns of evolution. Here are my thoughts about the most interesting patterns and their applicability to software development.
Its been a good experience to speak to various agile product suppliers and get their interesting views on journey deveoping the product, the outlook and vision into shpaing the products and the key trends. While its easy for us to get carried away with what you think and read on next trends in agile tooling, i was caught with a thought provoking insights speaking to Michael Dubakov, founder of "TargetProcess" about next key trend, TargetProcess focus and whats new in current release v.2.22