10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Mark Levison on Aug 14, 2008
Beginner's Mind is the idea of approaching things without preconceptions, pre-conceived ideas or prior judgements. This approach is useful to agile practitioners and coaches, inviting us to enter situations and observe what is really happening before we act. At Agile2008 Jean Tabaka and David Hussman ran a group workshop on the topic.
The workshop involved the participants, sitting at tables, who recorded their discoveries in reaction to questions that Jean and David posed. To set the stage, and imagine Beginner's Mind, we were given a quote from: Abbess Zenkei Blanche Hartman (in Suzuki Roshi's epic work "Zen Mind, Beginner's Mind"):
"Beginner's mind is Zen practice in action. It is the mind that is innocent of preconceptions and expectations, judgments and prejudices. Beginner's mind is just present to explore and observe and see 'things as-it-is.' I think of beginner's mind as the mind that faces life like a small child, full of curiosity and wonder and amazement. 'I wonder what this is? I wonder what that is? I wonder what this means?' Without approaching things with a fixed point of view or a prior judgment, just asking 'what is it?' "
Of Beginner's Mind, Suzuki says "Once we decide we know everything, we shut down opportunities to learn." To exercise Beginner's Mind we must stay in the present. Perhaps the hardest activity for a coach, staying in the present, requires that we are "fully conscious and aware in the present moment" and "sensing and actualizing new realities".
Our reactions to Beginner's mind: Mindful, Fully Present, Curiosity, No Expectations, Staying out of our own way, Pause Reflect, Many Possibilities.
Expert Mind Trap
David explained that in Expert's Mind many possibilities have been narrowed down to a few, or even one. Once we enter the Expert Mind trap we think we know everything and are no longer open to learning new things. This is what leads to prescriptive Agile adoptions – ones (as Amr described) where the consultant walks in and assumes that they know what is best for the client without studying the current situation. David went on to say in the music world no one would ever describe a fellow musician as an expert. Instead they would say she's: great, skilled, really talented. Some examples of Expert Mind that group noted:
So how do we share knowledge that we have and still retain Beginner's Mind? Jean's approach:
Letting go appears to be key.
We discussed the questions: When were you complacent? When did you anonymously drop a practice? Where is your agility growing stale?Finally we all finished the sentence: "I would embrace Beginner's Mind by ...":
Transforming Software Delivery: An IBM Rational Case Study
18 agile and lean practices for effective software development governance
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
I've been looking for a good post-facto description, and yours is the best so far. I was there, and enjoyed every minute.
Thanks for quoting my "Embrace Beginner's Mind..." answer. A minor correction, if you don't mind: I'm sure I mumbled when I said it, but I wrote "innocence" instead of "interest." So it's
Each day, ask five times why with innocence and without arrogance
And I've been working on it! ;-)
Cheers.
+ Michael
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
1 comment
Watch Thread Reply