Working in an agile team, have you ever tried to *not* estimate activities and a delivery schedule ?

Yes I have in a few projects, but again "one size does not fit all" and the circumstances, stakeholder profiles, project organisational structure and other parameters [process, culture and ways of working] need to be aligned correctly to achieve the successful utilisation of this approach.

Its a major paradigm shift that is not usually achievable in my experience. The time taken to estimate/re-estimate could be used to deliver the new product or system change. The preference for hypothetical/abstract prediction [the "Linus blanket"" of crystal balling, magic wands and other quasi-religious ceremonial artifacts] compared to actual business value realising delivery. I support the principle of #noestimates movement, which is to shift organisations to the lean priniciple of maximising value creation, and reducing waste. Yes the argument can be made that there is value to be be derived from estimations and plans, but this needs to be carefully considered as to the actual level of effort required versus the perceived or objectively quantifiable "value"[cost saving? increase in efficiency/profitability?] or is just for "peace of mind"or to secure contractual parameters that in the end prove unreasonable to hold a vendor hostage in an untenable situation.

Again I have witnessed first hand the success of moving business organisations to the truly lean agile approach and maximising delivery of actual value where the correct stakeholders actively participate in the project with a medium term [6month to 12month] high level roadmap and then short term timeboxed [sprints - 2weeks] plan driven by a prioritised backlog, and continuous delivery/integration approach to evolve the final project product deliverables.

In addition the project team needs to achieve lean flow and empirical techniques such as cumulative flow measurements, and velocity, to create metrics on delivery [as opposed to hypothetical metrics in planning such as planning poker]. Extrapolating the evidence based data allows for projections for completion which replace traditional up front estimation techniques. Allow the work to emerge and commit budget to tranches of work. Again this is usually too much of a radical shift from the safety blanket of "knowing everything upfront".

Author: Richard Smith - for: Knowledgesmith

KM Goals and Measurements - More insight from Stan Garfield

Another insightful piece from KM guru Stan Garfield.

In particular are the very practical suggestions for implementing KM Performance Metrics.

To quote:
"Each member of the organization should have three simple knowledge-related goals that are easy to remember, straightforward to measure, and consistent with the top 3 objectives. You should define personal goals, organizational targets, how employees will be measured, and how progress will be reported."

Communities of Practice - platform for realising KM strategy

Another great article by Stan Garfield on Communities of Practice as a platform for KM strategy realisation, the article includes a number of links to other articles and online resources.

To Quote the article:

"Communities are fundamental to connecting people with related interests so that they can share with one another, innovate, reuse each other's ideas, collaborate, and learn together. Starting a community is an excellent first step in launching a KM initiative, and can be used as a building block for more elaborate functionality.

Communities enable knowledge to flow between people."

Read the full article on LinkedIN here:

Mindfulness – Where Business and the Behavioral Sciences Intersect

Great video introducing mindfulness and its ability to positively impact business value, as part of knowledge processes through organisational culture not just applying some kind of checklist methodology.