I come across many articles that I think would be great to pass on to others. Most of them I try to post to Twitter, Linked In, or Google Plus (occasionally FaceBook). The issue with that approach is that they are lost to the social media wind.
There are many book marking tools and ways
Project retrospectives are challenging. I spoke a bit about this in lessons learned vs. project retrospectives. You might look at a merger, acquisition, implementation of a new ERP system, or even a major upgrade of an ERP or CRM system. These are non-reoccurring events. A retrospective of this type is
I’ve been training, talking, coaching, and writing recently on the topic of commitment and realized that anytime that comes up, it reminds me of the old (seems old – but not really that old!) discussion on commitment or forecast. I still find there are many questions on this topic. It certainly has not been put
Denver and Boulder, Colorado have a number of different agile groups that meet regularly. There is also an annual Mile High Agile Conference that sells out every year! I’m often talking to people who are new to Denver, Boulder, or somewhere else in Colorado and interested in agile, Scrum, kanban, lean, XP, etc. so I
Learning the different approaches an agile coach may take can be challenging without experiencing them. My preference when training people is to run exercises to help them experience the various approaches to agile coaching. Most recently, I had the opportunity to run one with a diverse group of people at the
The most common agile retrospective focus is on the sprint (or iteration) that was just completed. For most agile teams, this is the past two weeks. We have many more options for retrospectives than simply looking back on the last sprint. We can look at a specific topic, an event, use a future focus, or look