Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
My day to day life in one sentence is what you have stated. First, what type of requirements? Project or Product? Project manager is accountable for the first one while business analyst is accountable for the second one. Second, are you sure you have requirements? Take a look if you do not have wish/desires/wants instead of requirements. it is a critical difference to decide a stategy to work with.
...
1 reply by Nenad Pesic
Jan 11, 2018 1:03 PM
Nenad Pesic
...
Hi Sergio,
thank you for the comment. Let's think of a hypothetical case : the product will be used by both stakeholder groups. One stakeholder group wants a white product and the other one wants a grey product. White has tighter tolerances in terms of quality because it is premium. Gray is for a different market where the quality requirements are not as strict and they do not want white because it is more expensive.
My day to day life in one sentence is what you have stated. First, what type of requirements? Project or Product? Project manager is accountable for the first one while business analyst is accountable for the second one. Second, are you sure you have requirements? Take a look if you do not have wish/desires/wants instead of requirements. it is a critical difference to decide a stategy to work with.
Hi Sergio,
thank you for the comment. Let's think of a hypothetical case : the product will be used by both stakeholder groups. One stakeholder group wants a white product and the other one wants a grey product. White has tighter tolerances in terms of quality because it is premium. Gray is for a different market where the quality requirements are not as strict and they do not want white because it is more expensive.
...
1 reply by Sergio Luis Conte
Jan 11, 2018 2:44 PM
Sergio Luis Conte
...
I will write about I do in the practice because I guess it will be help you. First of all, a product is created to achieve a strategical objective then strategy is the driver. Second, quality is the strategic driver. To define quality you have to define the business and business is a three axis function where the x,y,z are client, need and technology where technology is a general term (a pencil is a technology). The concept of stakeholders is not valid here. The valid concept is client. If people in your organization has defined the business and the quality attributes that are needed to achieve the business objectives then you must create all needed to go for it. In your case, people on your organization must define what product will address the objectives for the business: white or gray. What I do? I perform a facilitation workshop where all relevant stakeholders are there to decide about this topics and I performing as facilitator. Is not easy, beleive me. But is my job. It requires time for preparation.
Saving Changes...
Michael WilliamsSr. Project Manager| Itron, Inc.Spokane, Wa, United States
Your scenario doesn't sound like opposing requirements, just different levels or features from a base model to the premium model.
Depending on your production model - you could pull the grey product out of production, or skip the steps in production that are not required for the customer's needs and willingness to pay.
You may have two projects on your hands, if you can't figure out how to make both products work in one project. Development of the white product first will lead you down the path of how to develop the gray product more efficiently, rather than producing the gray first, and then having to duplicate development efforts to improve the gray to a white product.
Good Luck!
...
1 reply by Nenad Pesic
Jan 11, 2018 3:43 PM
Nenad Pesic
...
Thank you for the comment Michael, I appreciate it.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Jan 11, 2018 1:03 PM
Replying to Nenad Pesic
...
Hi Sergio,
thank you for the comment. Let's think of a hypothetical case : the product will be used by both stakeholder groups. One stakeholder group wants a white product and the other one wants a grey product. White has tighter tolerances in terms of quality because it is premium. Gray is for a different market where the quality requirements are not as strict and they do not want white because it is more expensive.
I will write about I do in the practice because I guess it will be help you. First of all, a product is created to achieve a strategical objective then strategy is the driver. Second, quality is the strategic driver. To define quality you have to define the business and business is a three axis function where the x,y,z are client, need and technology where technology is a general term (a pencil is a technology). The concept of stakeholders is not valid here. The valid concept is client. If people in your organization has defined the business and the quality attributes that are needed to achieve the business objectives then you must create all needed to go for it. In your case, people on your organization must define what product will address the objectives for the business: white or gray. What I do? I perform a facilitation workshop where all relevant stakeholders are there to decide about this topics and I performing as facilitator. Is not easy, beleive me. But is my job. It requires time for preparation.
...
1 reply by Nenad Pesic
Jan 11, 2018 3:44 PM
Nenad Pesic
...
Thanks Sergio, I like the workshop idea , very useful.
Try to understand interests rather than positions. If we don't take the time to understand the real underlying needs and then try to find the overlap between key stakeholders, we will likely end up with compromises that satisfy no one.
Kiron
...
1 reply by Nenad Pesic
Jan 11, 2018 3:46 PM
Nenad Pesic
...
Thank you Kiron. You are right , understanding interests rather than positions is the basis of good negotiation.
Your scenario doesn't sound like opposing requirements, just different levels or features from a base model to the premium model.
Depending on your production model - you could pull the grey product out of production, or skip the steps in production that are not required for the customer's needs and willingness to pay.
You may have two projects on your hands, if you can't figure out how to make both products work in one project. Development of the white product first will lead you down the path of how to develop the gray product more efficiently, rather than producing the gray first, and then having to duplicate development efforts to improve the gray to a white product.
Good Luck!
Thank you for the comment Michael, I appreciate it. Saving Changes...
I will write about I do in the practice because I guess it will be help you. First of all, a product is created to achieve a strategical objective then strategy is the driver. Second, quality is the strategic driver. To define quality you have to define the business and business is a three axis function where the x,y,z are client, need and technology where technology is a general term (a pencil is a technology). The concept of stakeholders is not valid here. The valid concept is client. If people in your organization has defined the business and the quality attributes that are needed to achieve the business objectives then you must create all needed to go for it. In your case, people on your organization must define what product will address the objectives for the business: white or gray. What I do? I perform a facilitation workshop where all relevant stakeholders are there to decide about this topics and I performing as facilitator. Is not easy, beleive me. But is my job. It requires time for preparation.
Thanks Sergio, I like the workshop idea , very useful. Saving Changes...
Try to understand interests rather than positions. If we don't take the time to understand the real underlying needs and then try to find the overlap between key stakeholders, we will likely end up with compromises that satisfy no one.
Kiron
Thank you Kiron. You are right , understanding interests rather than positions is the basis of good negotiation.
...
1 reply by Kiron Bondale
Jan 11, 2018 3:50 PM
Kiron Bondale
...
Sometimes it also comes down to a lack of alignment in project vision/outcomes between the two groups. If you don't have alignment on that, the devil usually emerges in the details!
If that is the case, it might be time to dust off the charter whose creation both stakeholders should have participated in or at least have bought into and re-confirm that alignment...
Thank you Kiron. You are right , understanding interests rather than positions is the basis of good negotiation.
Sometimes it also comes down to a lack of alignment in project vision/outcomes between the two groups. If you don't have alignment on that, the devil usually emerges in the details!
If that is the case, it might be time to dust off the charter whose creation both stakeholders should have participated in or at least have bought into and re-confirm that alignment...
Kiron Saving Changes...
Suleander ZahnCo-organizer & Facilitator| Agile ConnectPorto, Porto, Portugal
Hi Nenad,
I'm not sure if your real context allows you to do that, but, making a small experiment (like prototyping or mock ups) of both opposing "products" directly with possible end customers could give you lots of hacks on which requirements (wishes, desires, whatever...) to attack first.
It would also give you solid arguments to defend your position in front of the non-satisfied group and even other stakeholders.
Att, Suleander
...
1 reply by Nenad Pesic
Jan 11, 2018 4:32 PM
Nenad Pesic
...
Hi Suleander,good idea, I'll keep that in mind. Thank you.
