Lynn BollowProject Manager | TekSystems/ State of New Jersey Certification Orange, Nj, United States
I am in the process of gathering ideas on ground rules for the project I am currently on. It has been three months and there are some issues and unacceptable behaviors. I feel with grounds rule some of the issues can be easily corrected. Saving Changes...
Lynn BollowProject Manager | TekSystems/ State of New Jersey Certification Orange, Nj, United States
Oct 24, 2019 6:59 PM
Replying to Adrian Carlogea
...
In order to impose anything to a group of people you need formal authority over them. If you don't have such authority (you are not their line manager) better forget about ground rules as you are not the boss.
You could try to impose the ground rules by influencing the line managers but if they don't like the idea it can make things worse.
I am not sure what you mean by unacceptable behavior but if it is HR related then this is not for the PM to resolve but by the line managers and the HR department.
Hi Adrian, It's not HR related. It's all the behavior PMBOK and all of PMI best practice suggest we shouldn't do. Like speaking badly about other team members. Undermining the PM and team decisions in front of clients.
...
1 reply by Adrian Carlogea
Oct 25, 2019 12:01 PM
Adrian Carlogea
...
In understand that but in the end the employee follows the orders of his/her line manager. If you are not a line manager then it would be difficult to impose ground rules to the team members. I think a company-wide policy should be defined and the line managers should observe it and ensure it is followed.
I was working for a customer on a project and the vendor's project manager had left on holiday. Before leaving on holiday the PM had agreed with out project director some things that were a change to the original plan. In a meeting the technical lead nonetheless said that he did not agree with what the PM had decided and he would follow the originally agreed plan. At the organizational level the technical lead was two levels above the PM and as such the PM had not authority to do anything about it.
Without the approval of the tech lead the PM was unable to do anything. Probably that time he hadn't agreed with the tech lead and that's why that situation occurred.
Saving Changes...
Lynn BollowProject Manager | TekSystems/ State of New Jersey Certification Orange, Nj, United States
As Kiron and Sergio point out, the rightness of behaviours is in the eye of the beholder. At what point does confidence become arrogance? At what point does analysis become paralysis?
Not only would I let the team set the ground rules, I would also let the team enforce them.
Hello Mr. Parent,
I absolutely agree. The goal is to have the team decide on what Ground Rules would be best for this team. I want to be clear that this is not a perception. Out of 20 team members I've hear from 14 with the same complaints.
Thank You Saving Changes...
Lynn BollowProject Manager | TekSystems/ State of New Jersey Certification Orange, Nj, United States
Oct 25, 2019 4:08 AM
Replying to Thomas Walenta
...
Lynn,
often unacceptable behaviors can be tracked down to violations of human values that are detailed in Codes of Ethics / Conduct. If your company does not have these, you can use PMI's Code of Ethics.
Human values have been proven by research to be ubiquitous, they are respect, responsibility, fairness and honesty as to PMI's code. On top of that, research has shown that community, compassion, autonomy and humility are further values most humans can agree to.
For groundrules, it is important to formulate specific expected behaviors that have been identified to be shaping the team culture (e.g. punctuality for a meeting, listening to others, raising concerns, ..). As a rule of thumb, these should be 10 or less, otherwise they are easily ignored. In diverse teams, I found it worthwhile to conduct a cultural workshop and let the team identify potential gaps in expectations, which then can be closed by a ground rule.
As a project manager, you might not be able to impose rules to the team (and this is a questionable approach anyway), but since you are in charge of success and it only can be achieved with a performing team, it is your responsibility to shape the teams behavior.
Hello Thomas,
Words of wisdom, Thank you kindly. I am hearing complaints From one team member after another. The goal is to present the idea
...
1 reply by Thomas Walenta
Oct 25, 2019 12:00 PM
Thomas Walenta
...
Hi Lynn,
if 14/20 team members complain to you this is a prty 1 issue (which is a good thing: they expect you to make changes, you have their permission to act).
If you haven't experience with facilitation or if your emotions are too high, you should try to get help from the outside, and setup a day workshop (maybe afternoon-dinner-morning).
Target should be to jointly agree on roles and responsibilities, an orgchart and team communication plan/meetings (which gives you the team infrastructure).
And then jointly develop the groundrules, considering the different excpectations/culture, and as I wrote, up to ten specific behaviors (e.g. brainstorm expected behaviors, groups them and vote to get to ten).
Inputs about the importance of ethics and team maturity (I like the youtube video on tribal leadership) might be helpful.
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Oct 25, 2019 9:31 AM
Replying to Lynn Bollow
...
Hello Thomas,
Words of wisdom, Thank you kindly. I am hearing complaints From one team member after another. The goal is to present the idea
Hi Lynn,
if 14/20 team members complain to you this is a prty 1 issue (which is a good thing: they expect you to make changes, you have their permission to act).
If you haven't experience with facilitation or if your emotions are too high, you should try to get help from the outside, and setup a day workshop (maybe afternoon-dinner-morning).
Target should be to jointly agree on roles and responsibilities, an orgchart and team communication plan/meetings (which gives you the team infrastructure).
And then jointly develop the groundrules, considering the different excpectations/culture, and as I wrote, up to ten specific behaviors (e.g. brainstorm expected behaviors, groups them and vote to get to ten).
Inputs about the importance of ethics and team maturity (I like the youtube video on tribal leadership) might be helpful. Saving Changes...
Hi Adrian, It's not HR related. It's all the behavior PMBOK and all of PMI best practice suggest we shouldn't do. Like speaking badly about other team members. Undermining the PM and team decisions in front of clients.
In understand that but in the end the employee follows the orders of his/her line manager. If you are not a line manager then it would be difficult to impose ground rules to the team members. I think a company-wide policy should be defined and the line managers should observe it and ensure it is followed.
I was working for a customer on a project and the vendor's project manager had left on holiday. Before leaving on holiday the PM had agreed with out project director some things that were a change to the original plan. In a meeting the technical lead nonetheless said that he did not agree with what the PM had decided and he would follow the originally agreed plan. At the organizational level the technical lead was two levels above the PM and as such the PM had not authority to do anything about it.
Without the approval of the tech lead the PM was unable to do anything. Probably that time he hadn't agreed with the tech lead and that's why that situation occurred. Saving Changes...
Ground rules should never be imposed. Assuming you are working with a group of professionals, they should be able to come up with these with your facilitation. Then, the hard work is getting them to work as a team to hold each other accountable to living by those rules without one person having to be "bad cop". Saving Changes...
"Ground rules" should not be project specific, but driven by the organizations policies on such matters. Expected behaviours in the workplace are fundamental to an organizations success and well-being. An example, the Canadian Armed Forces initiative to address sexual misconduct.
Let's differentiate organization standards & policies from working agreements which are made at the team level. The term "ground rules" might be equally applied to both. The former is non-negotiable and is imposed from above whereas the latter are developed by the team but their definition may be facilitated by a PM or agile lead.
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Dear Lynn
Interesting your question
Thank you for placing it
The Team Appointment Term is similar to the ground rules that define a set of rules and procedures that guide the work of the entire team.
If they are well defined and agreed upon, they can motivate the team and make a big difference to the project outcome.
The team nomination term may include the team's values, agreements and operational guidelines. He should advise on unacceptable types of behavior within the team.
It is output from the Plan Resource Management process. Saving Changes...
"Ground rules" should not be project specific, but driven by the organizations policies on such matters. Expected behaviours in the workplace are fundamental to an organizations success and well-being. An example, the Canadian Armed Forces initiative to address sexual misconduct.
Let's differentiate organization standards & policies from working agreements which are made at the team level. The term "ground rules" might be equally applied to both. The former is non-negotiable and is imposed from above whereas the latter are developed by the team but their definition may be facilitated by a PM or agile lead.
...
1 reply by Steve Ratkaj
Oct 25, 2019 4:48 PM
Steve Ratkaj
...
Agreed. maybe it's semantics, but I see "unacceptable behaviors" being addressed through formal organizational policies and not "ground rules". I could see ground rules pertaining such things as "etiquette" during meetings (e.g. don't interrupt while others are speaking, do not speak while others are speaking, don't be late for meetings, etc., etc.)
Let's differentiate organization standards & policies from working agreements which are made at the team level. The term "ground rules" might be equally applied to both. The former is non-negotiable and is imposed from above whereas the latter are developed by the team but their definition may be facilitated by a PM or agile lead.
Agreed. maybe it's semantics, but I see "unacceptable behaviors" being addressed through formal organizational policies and not "ground rules". I could see ground rules pertaining such things as "etiquette" during meetings (e.g. don't interrupt while others are speaking, do not speak while others are speaking, don't be late for meetings, etc., etc.) Saving Changes...