Agile Communications Plans

Dolphins are easier to track than submarines. They surface more often and are usually within view of where you last saw them. Subs, on the other hand, can disappear for months or years at a time, and it is difficult to tell where they have gone. What does this have to do with project communications? Has Mike finally gone mad? These are valid questions, so let me explain. Many traditional project management deliverables have agile alternatives. For instance, a product backlog is somewhat analogous to a work breakdown structure. A release roadmap contains many of the elements of a Gantt chart. Yet we rarely see agile communications management plans. Why is this?

Read more

Innovation: Running Experiments and Learning

In my last article on Incubating Innovation, we explored the culture and mindset of accountable experimentation. This article focuses on actionable tools and approaches. Within agile frameworks, the team retrospective is the primary workshop for planning and evaluating experiments. Yet most team retrospectives I see are broken. Teams spend too much time recording viewpoints and information—but not enough time reviewing or planning experiments. It is common to see the majority of the time spent gathering what went well, what did not go well, and appreciations. Yet where’s the focus on experiments, the learning process and trials for the next iteration? To make things worse, some teams do not take the retrospective seriously. Maybe after the potential stress of the sprint review, […]

Read more

Incubating Innovation

If success goes to those who can innovate the fastest, how do we nurture innovation? The basics are simple to understand—but difficult to implement and stick with in the face of adversity. We need to create an environment that encourages experimentation while also tolerating, investigating and learning from the inevitable failures. It may sound easy, but executives and shareholders demand results, not “learning opportunities.” We need an approach that fosters experimentation and learning in a defendable way, with a bias for results. To innovate faster than our competitors, we need to maximize our learning potential. This means that by design, 50% of our experiments should fail since we are seeking knowledge expansion, not validation of things we already know. The […]

Read more

They are “Lessons to be Learned”, not “Lessons Learned”

The suggestions, observations and ideas we capture at retrospectives are not Lessons Learned. That would imply we have already learned from them and will not make that mistake again. Instead, they are Lessons-to-be-Learned which is subtly different but stresses the most important part, which is we now need to learn something. Learning involves several steps. David Kolb, an educational theorist, describes a 4-step learning process: Concrete Experiences (What we already know) Observation and Reflection (What our retrospectives help us identify) Abstract Conceptualization (Thinking about the problems and designing potential solutions) Active Experimentation (Trying something new) These stages act as part of an experimental learning cycle. The last step, Active Experimentation, creates new concrete experiences and builds on what we already […]

Read more

An Antidote to Velocity Obsession

Getting things done is great; to get things done is why we start things in the first place and why we follow through even when presented with obstacles and setbacks. We do things because they will (hopefully) bring us to some better state. So getting these things done quickly is good because we arrive at this better state sooner.  We track our rate of development (velocity) as a useful measure of progress and also as a leading indicator towards when we should be done. However focussing too much on velocity is dangerous; it leads to myopic mindsets and even moronic behaviour. Yes, velocity is good, but not at the expense of quality, good-will, or noticing subtle changes in direction. At […]

Read more

Agile Communications

Why so much Communication?“We work with bits not atoms”. This phrase speaks to the distinction of IT projects from physical construction. Our tools and processes manipulate ideas, concepts, and models, not steel, concrete, or plastic. Given the intangible nature of software, it is no surprise we need more focus on communications, collaboration and information sharing to keep everyone informed and aligned towards a common goal. Agile methods recognize this increased need for communication and provide a variety of tools and checkpoints to help avoid the classic project mistakes of mismatched expectations and confusion. In the absence of a visible physical product to point at and measure, we need to be constantly confirming understandings and aligning ideas against increments of the […]

Read more

Reinvigorate Your Retrospectives

Come and see Jennitta Andrea present on how to reinvigorate your retrospectives at the Calgary APLN meeting this Friday 27 February. From the outline:“You know you should be performing regular retrospectives, but you can't convince management or the team that it's a worthwhile investment of time … Your team has been performing retrospectives every iteration, and they have become monotonous and have stopped producing valuable insights … You've heard about retrospectives, but don't even know how to get started …” Jennitta is a thought leader in the agile community and serves on the board of the Agile Alliance. I am sure the talk will promote many ideas to make retrospectives extra productive. To register for this free event visit the […]

Read more