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 received a text message last night from one of my developers around 8:15 pm. “Do you want to talk shop?” it said. My first thought was, oh dear, what is broken now? (it’s release week as it is every other week and it’s been a rough month or two). When he called me and what he said next completely blew my mind.
Coming up on Agile2015 is hitting me right in the feels. This will be my fourth Agile Alliance conference, my fourth job in as many years (actually fifth), my second time presenting at an Agile Alliance conference, my second time presenting in Washington D.C., and my first time really feeling like I have no idea what I’m doing.
Agile2014 marks another Agile conference this year. As usual it did not disappoint. This year was extra special because I was able to be a reviewer for the Collaboration, Culture and Teams session track and was also selected to present my session on the UX Runway. It was great to once again catch up with old friends and meet new ones; even some from my home state of Minnesota! Some Women in Agile also got together for an impromptu session in the Open Jam area and though I was not able to make it, I heard great things! After attending many conferences over the past few years I wanted to make a list of some of the things I’ve learned for how to get the most out of your time there.