Start with why.
Why blog? Why not? or…
To diversify my thinking; to bring diversity to the frameworks, methods, and other components; to improve BA and how BA is done; to rant about the rantworthy to support all of the above.
I’ll get to comments and blog stuff down the road. I’m not sure I have blogging in me. So we’ll see how this goes.
This site is turned on. I’ve got the content to a presentable state. Soon going live on LinkedIn to start spreading the news that this site is up and looking to become a pragmatic force in BA governance and advancing the value of business analysis and business analysts.
I started my career as a business applications developer. I moved to analysis on a fairly technical program. Over the years, my interests have drifted from the technical to the business; helping business get what they need to solve their problems or improve their capabilities.
I’ve seen things. I’ve been under a bus. I’ve learned how to manage expectations. And I’ve seen projects fail to meet their objectives.
How to improve business analysis is a wicked problem. Business Outcome Analysis is a framework I’ve built to address requirements quality. IAG Consulting published some great stuff on the impact of requirements quality here. The material sang to me. It reflected and supported much of what I had been formulating over the years as a BA.
I’m no requirements guru, but I have a broad experience, I’ve worked with some really strong folks, and I hope that I come across as humble as I feel. I can be a sarcastic bastard, but it’s all in fun.
I was astounded that the url businessAnalysisStandards.org was available, so I started this. I’ve been inspired to use this medium to accelerate the transformation of business analysis and help moving it out of a primarily IT domain and into more areas of the business.
And, bring stronger governance to improve business analyst’s business value. All ahead full.
More as it develops…