Over the last few months I have been in more discussions than I can count about the role of the business analyst, project manager vs. business analyst, where the business analyst fits in on an agile team, and which roles are needed to make a successful team. They have been wonderful passionate conversations. With each discussion I kept coming back to the same conclusion…it's all about teamwork.
When I look back at what made some projects challenged and others widely successful it came down to all team members doing what was needed to reach the goal regardless of their role. I don't know about you, but I never had the luxury of the having the best in class PM, BA, development team, and QA analyst. Since that was the case my most successful teams would discuss what needed to be done (tasks) to accomplish our goal and who on the team was the best person to complete or assist with that task. I would say 85-90% of everyone's tasks fell in line with their role. The other 10-15% was filled with tasks that individuals were more qualified to accomplish. This 10-15% is what made those teams great. When team members have the attitude of "what can I do to help the team" you'll have more success. Chances of failure increase when team members bring an attitude of "that task is not in my job description."
This point was illustrated beautifully by Lee Scott and Dawn Solem of VSP in their presentation Business Analyst & Project Manager - The Strategic Partnership to Project Success at the PW & WCBA conference in Anaheim last month. Thank you Lee and Dawn.
Defining roles have its place, but to be a successful team you have to figure out how to use everyone's expertise and skills regardless of roles.
Please add your thoughts and comments!
7 Comments
Agree definitly. Defining the roles is must, while the responsibilities maybe different for the same role in different teams and companies. It’s agile of management. All for the goal to deliver the project on time and with quality.
Well, that
I think we are saying the same thing. You are right, you can’t assume that a task is being done by someone else or that you should be doing it. In the begining of a project the team needs to flesh out all the tasks and determine who is doing what. But, just because the PMBOK says the PM is responsible for task “x” does not mean only the person with the PM title can do that task.
In my opinion "Teamwork" and "Roles" are two entirely different side of the coins and in the day 2 day life of these they get diluted hence the respective essence is lost. In order to achieve project objectives, one has to respect the role defined for them. My role can be of BA and I should devote my focus entirely on achieving what's defined for the role. Also one is assigned to the role based on the best fit criteria and their core competency. We should try not mixing Roles & Responsibility with Teamwork as there can be a threat of ownership and accountability getting diluted. Teamwork on the other hand is an essential spirit that every individual should possess and embrace. It's a key success element but it's far away from the Role one plays. We should be ready/proactive to help other team member's as and when. I can say it should be our responsibility to help others and maintain the Role we assigned to.
I agree with both of you, habilities and certifications lead you to define responsibilities that are better performed with teamwork. (let
The other 10-15% was filled with tasks that individuals were more qualified to accomplish. This 10-15% is what made those teams great. When team members have the attitude of “what can I do to help the team” you’ll have more success. Chances of failure increase when team members bring an attitude of “that task is not in my job description.”
This statement seems to me to be the core of what was being said. Teamwork and Roles can go hand in hand when your team has the “Can do” attitude refered to. I agree that your role on the team should be clear and defined but the best team I ever worked with had individuals with the ability to just put the question out there even if the answer was known. We solicited that kind of input from the whole team when we had update meetings. Not only did this create learning opportunities for team members with less experience, it also led to some pretty creative solutions. But I digress. You can have your role and know your role but where is the thrill of discovery if you are never given the opportunity to participate in the parts of the “project” that are not defined as part of your role?
There is no “BA” in Team or something like that!!!
One Trackback
[...] Kupe over at B2TTraining argues that successful projects are all about teamwork; When I look back at what made some projects challenged and others widely successful it came down to all team members doing what was needed to reach the goal regardless of their role. [...]