As businesses acknowledge the value of business analysis – the result of the absolute necessity to drive business results through projects – they are struggling to figure out three things:
What are the characteristics of their current BA workforce, and how capable does their BA team need to be?
What is needed to build a mature BA Practice?
How are we going to get there?
Of the four articles in the series, this particular article is the most sensitive. If not practiced with caution, trying to influence someone or a situation could have a devastating impact. Therefore, this article comes with a disclaimer: “Stupid is as stupid does.”
Teams that are geographically distributed and primarily work virtually face many challenges. One of them is sharing knowledge. I am part of an organization which has a team in Denmark responsible for development of the platform we support, while a team in India is responsible for the maintenance.
Now that you’re prepared to work with executives, I’m sorry to inform you that the tough stuff is about to begin. While preparation and understanding are crucial elements, and speaking executive language further deepens our conversations, the real meat on the dog bone is taking the next step and beginning to develop your relationship and establishing yourself as a trusted advisor.
Business value is a new indicator for project success. Huh? You may be wondering what ever happened to the good ole scope, schedule, and budget. They are still there and measured, but what the 2012 trends have been pointing to is that a project completed within scope, schedule, and budget and not be successful.
In this four part series, I will give you the confidence and motivation you need to make a difference; a difference that will allow you to “Bark with the Big Dogs.” What I’m about to share is tried, tested and true. There are no gimmicks. Before you read on, ask yourself this: “Am I willing to try something different?”
I was recently working with a client who said that the life of a BA in his organization is complicated, primarily because very few people really understand what Business Analysts (BAs) do. I have felt for a very long time that perhaps our most compelling challenge is to change the organizational view of our role as primarily “requirements collectors” and to help stakeholders see the true value that business analysis brings to the enterprise.
December ought to be a month of celebrations, but for managers it often isn’t. In many companies this is the time for the yearly performance appraisals. When top management is not trusting employees, and employees are not trusting top management, the middle manager is usually caught between a rock and a hard place. But they don’t have to be.
Leadership is like genius, it is one of those concepts that is recognizable when you observe it in action, but is otherwise somewhat difficult to define. And creative leadership is even harder to define because we haven’t been focusing on it in the context of business, unless we are talking about new product development. But creativity and innovation in the business world is not just about product innovation.
... it became clear to me that it was time to revisit the core role a business analyst fulfills in an organization. In my experience thus far, well over 75% of the business analysts I know report through the IT side of their organization. Of the 25% that report through the business side, most have a primary responsibility that is outside of the typical business analysis role.
I was asked my opinion about whether I’d want project managers to focus on processes first or tools first. Without hesitation, my response was “I don’t really care whether project managers focus on process or tools first,as long as they don’t get in the way of our doing good business analysis!”
The Agile Extension to the BABOK® describes “business analysis areas of knowledge, their associated activities and tasks, and the skills necessary to be effective in their execution within the framework of agile software development”. Below are 3 misconceptions that, in my opinion, the current draft of the Agile Extension is helping perpetuate.
In many organizations, culture and conventional wisdom make it difficult for the BA to break out of mostly tactical roles within projects. However, in many ways, the future competitiveness of your organization (and consequently of your future employment) depends on it! So don’t blink or you will miss out on the best BA opportunity of your career.
In a nutshell, a methodology represents a series of steps in a project specifying Who is to perform What, When, Where, Why, and How (aka, "5W+H"), from start to finish. Perhaps the best way to think of a methodology is as a roadmap or an assembly line where a product is developed over a series of work stations.
I’m pleased to continue to uphold: the unveiling of this year’s top 10 business analysis trends. This year business analysts (BAs) will need not only the balanced portfolio of technical and business skills they have been perfecting, but also a more comprehensive perspective in order to meet the challenging business environment of 2012.
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: