2018 LeSS Conference on twitter
#LeSS2018 #conference is about to start!@basvodde #scrum #agile #LeSSWorks #nyc #newyork pic.twitter.com/907TRdVMlQ
— Michał Kret (@krtexxx) September 14, 2018
#LeSS2018 #conference is about to start!@basvodde #scrum #agile #LeSSWorks #nyc #newyork pic.twitter.com/907TRdVMlQ
— Michał Kret (@krtexxx) September 14, 2018
Though I have been associated with the Large Scale scrum (LeSS) community for about five years (though the “community” did not exist, I can think of my association with like minded folks) this is my first LeSS conference. While I used to attend a lot of conferences in the past, I have started focusing more on deep learning (by attending focused workshops) than focusing on conferences. But this year, I had to make an exception for the LeSS conference. Why? (a) It was the first LeSS conference in North America, (b) It was not very far, and (c) I was thinking that I might meet some of the smartest people in the LeSS community whom I may not meet otherwise, and (d) I have heard that it is a “team based” conference (unlike other conferences where you are on your own), and I wanted to find out what the heck it was. I was not disappointed.
I’ve attended the 2018 LeSS Conference – my first – in the Angela Orensanz Center in New York. I was really inspired by the many great speakers, experiments and experiences and was glad I could help Jurgen de Smet by his workshop on Management 3.0 practices that can complement LeSS with experiments.
A couple of notes on the Conference; it has been the first Conference I attended in years where I actually learned a lot, either from the many speakers, experiments and experiences, but from my ‘team’ as well. As the LeSS Conference is a team-based conference, we reflected on the content and our insights during the Conference, which accelerated my learnings.
I enjoyed learning from Real people with Real solutions to problems many organizations try to solve(strikeout) avoid.
I wish I made it to parallel sessions too 👥😅, here is
If you worked in large organizations you have probably heard about the term “dependencies”. I am convinced that dependencies need to be eliminated, not managed. With a help of system diagrams in this article, I will uncover the main reasons why Scrum Teams suffer from dependencies, how they impact organizational agility, and what the fundamental solutions to this issue are.