If you are an agile software development practitioner or have worked in the industry around these practices, you are free to skip ahead. This chapter is meant as an introduction to all things agile, lean, and product/service innovation for those who are unfamiliar with the terms, values, practices, and philosophy. It is a tough chapter…
Read more
Talking to a team about carryover at a daily scrum meeting led me into a very uncomfortable confrontation with someone who already didn’t like me. Not sure why but I ascertained it had something to do with the unhealthy relationship between product and technology organizations and the fact that product was pushed by sales to make commitments on behalf of the teams that were essentially never met on time (more on that issue in a later post). So a contentious confrontation – read on…
Waste seems to be a simple enough concept: anything that does not add value should be eliminated. But what about the features that are supposed to add value and actually don’t? What about the features that are started working on as an idea or a quick win that we do to just get it out there quickly – MVP style but not really – that end up being thrown away or redone soon after? Afterward, no one denies those are waste; but how do we turn waste into something that can be recycled?
I recently had the amazing opportunity to travel to Lviv, Ukraine to speak at the Lviv IT Arena conference. Speaking internationally in a country I had never traveled to and experiencing the discomfort of not understanding the languages and culture made for a very memorable trip. I met some wonderful people and formed some hopefully lasting networking and collaboration relationships.
