Should the Product Owner dictate what info the UI needs to display? Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?using the prototype for live when building CMS/CRUD systems - wrong?Should our Tech Manager or Product Manager be the Project Manager?User story conversation vs. scope creepFrom user stories to product, where and when to do graphic design?How to make user stories independent in multi-discipline teamsIs it ok to define a user story that has no real business value without another story?How can user stories meet INVEST criteria in design-led development?Achieving independence for story itemsWhat to do with a Product Owner who is not able to understand the roleWhat should a UI designer know and how to deliver this knowledge to him?
When do you need buffers/drivers on buses in a microprocessor design?
Is there any pythonic way to find average of specific tuple elements in array?
A Paper Record is What I Hamper
std::unique_ptr of base class holding reference of derived class does not show warning in gcc compiler while naked pointer shows it. Why?
How can I wire a 9-position switch so that each position turns on one more LED than the one before?
Jaya, Venerated Firemage + Chandra's Pyrohelix = 4 damage among two targets?
Do I need to watch Ant-Man and the Wasp and Captain Marvel before watching Avengers: Endgame?
Putting Ant-Man on house arrest
What makes accurate emulation of old systems a difficult task?
Why does Arg'[1. + I] return -0.5?
Is this homebrew arcane communication device abusable?
Can you stand up from being prone using Skirmisher outside of your turn?
Why doesn't the standard consider a template constructor as a copy constructor?
How do I reattach a shelf to the wall when it ripped out of the wall?
Which big number is bigger?
How does the mezzoloth's teleportation work?
A faster way to compute the largest prime factor
Could moose/elk survive in the Amazon forest?
Are there moral objections to a life motivated purely by money? How to sway a person from this lifestyle?
What *exactly* is electrical current, voltage, and resistance?
Is Diceware more secure than a long passphrase?
How much cash can I safely carry into the USA and avoid civil forfeiture?
Is Electric Central Heating worth it if using Solar Panels?
finding a tangent line to a parabola
Should the Product Owner dictate what info the UI needs to display?
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?using the prototype for live when building CMS/CRUD systems - wrong?Should our Tech Manager or Product Manager be the Project Manager?User story conversation vs. scope creepFrom user stories to product, where and when to do graphic design?How to make user stories independent in multi-discipline teamsIs it ok to define a user story that has no real business value without another story?How can user stories meet INVEST criteria in design-led development?Achieving independence for story itemsWhat to do with a Product Owner who is not able to understand the roleWhat should a UI designer know and how to deliver this knowledge to him?
I hope someone can help me understand one part of the role of the Product Owner (PO).
In my company, we have a PO that is responsible for the Product Backlogs of all our products. I work as a UX designer. The PO specifies features and requirements to the Teams.
Very often, the PO suggests, in detail, how a user interface of our software should be, such as what type of information is to be displayed in the user interface (e.g. "I'd like to see a date in list" or "I'd like to see so and so in this view"). Often the PO has asked the customer, or knows already, but the product UI ends up being quite cluttered and complex.
I am now introducing user testing to encourage user-centered design and advocate making better design decisions based on user involvement.
My question is: to what extent should the PO describe the requirements of a UI? Should we (the developers and designers) look to the PO to decide and say what the information in the UI should be?
user-stories product-owner roles
edited 1 hour ago
Sarov
9,74932143
asked 1 hour ago
A designerA designer
161
New contributor
A designer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I hope someone can help me understand one part of the role of the Product Owner (PO).
In my company, we have a PO that is responsible for the Product Backlogs of all our products. I work as a UX designer. The PO specifies features and requirements to the Teams.
Very often, the PO suggests, in detail, how a user interface of our software should be, such as what type of information is to be displayed in the user interface (e.g. "I'd like to see a date in list" or "I'd like to see so and so in this view"). Often the PO has asked the customer, or knows already, but the product UI ends up being quite cluttered and complex.
I am now introducing user testing to encourage user-centered design and advocate making better design decisions based on user involvement.
My question is: to what extent should the PO describe the requirements of a UI? Should we (the developers and designers) look to the PO to decide and say what the information in the UI should be?
user-stories product-owner roles
edited 1 hour ago
Sarov
9,74932143
asked 1 hour ago
A designerA designer
161
New contributor
A designer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
In my opinion that's not a Scrum problem, but how you use your expertise efficiently. From a Scrum perspective it's fine to have clear requirements. From UX perspective you're doing a bad job.
– Christian Strempfer
1 hour ago
add a comment |
I hope someone can help me understand one part of the role of the Product Owner (PO).
In my company, we have a PO that is responsible for the Product Backlogs of all our products. I work as a UX designer. The PO specifies features and requirements to the Teams.
Very often, the PO suggests, in detail, how a user interface of our software should be, such as what type of information is to be displayed in the user interface (e.g. "I'd like to see a date in list" or "I'd like to see so and so in this view"). Often the PO has asked the customer, or knows already, but the product UI ends up being quite cluttered and complex.
I am now introducing user testing to encourage user-centered design and advocate making better design decisions based on user involvement.
My question is: to what extent should the PO describe the requirements of a UI? Should we (the developers and designers) look to the PO to decide and say what the information in the UI should be?
user-stories product-owner roles
edited 1 hour ago
Sarov
9,74932143
asked 1 hour ago
A designerA designer
161
New contributor
A designer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I hope someone can help me understand one part of the role of the Product Owner (PO).
In my company, we have a PO that is responsible for the Product Backlogs of all our products. I work as a UX designer. The PO specifies features and requirements to the Teams.
Very often, the PO suggests, in detail, how a user interface of our software should be, such as what type of information is to be displayed in the user interface (e.g. "I'd like to see a date in list" or "I'd like to see so and so in this view"). Often the PO has asked the customer, or knows already, but the product UI ends up being quite cluttered and complex.
I am now introducing user testing to encourage user-centered design and advocate making better design decisions based on user involvement.
My question is: to what extent should the PO describe the requirements of a UI? Should we (the developers and designers) look to the PO to decide and say what the information in the UI should be?
user-stories product-owner roles
user-stories product-owner roles
edited 1 hour ago
Sarov
9,74932143
asked 1 hour ago
A designerA designer
161
New contributor
A designer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 1 hour ago
Sarov
9,74932143
asked 1 hour ago
A designerA designer
161
New contributor
A designer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 1 hour ago
Sarov
9,74932143
edited 1 hour ago
Sarov
9,74932143
edited 1 hour ago
Sarov
9,74932143
9,74932143
asked 1 hour ago
A designerA designer
161
New contributor
A designer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 hour ago
A designerA designer
161
asked 1 hour ago
A designerA designer
161
161
New contributor
A designer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
A designer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
A designer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
In my opinion that's not a Scrum problem, but how you use your expertise efficiently. From a Scrum perspective it's fine to have clear requirements. From UX perspective you're doing a bad job.
– Christian Strempfer
1 hour ago
add a comment |
In my opinion that's not a Scrum problem, but how you use your expertise efficiently. From a Scrum perspective it's fine to have clear requirements. From UX perspective you're doing a bad job.
– Christian Strempfer
1 hour ago
In my opinion that's not a Scrum problem, but how you use your expertise efficiently. From a Scrum perspective it's fine to have clear requirements. From UX perspective you're doing a bad job.
– Christian Strempfer
1 hour ago
In my opinion that's not a Scrum problem, but how you use your expertise efficiently. From a Scrum perspective it's fine to have clear requirements. From UX perspective you're doing a bad job.
– Christian Strempfer
1 hour ago
add a comment |
1 Answer
1
active
oldest
votes
My question is, to what extent should the PO describe the requirements of a UI?
To the extent that the designers know what to design and the programmers know what to program. In your example, "as a user I want to see a list of dates so I can..." seems to be a good user story. Who else would know what the purpose of that user interface is and what data the users need at that point.
Should we (the developers and designers) look to the PO to decide and say what the information in the UI should be?
Yes. Now the Product Owner might not be a technical person. That means you have to provide feedback on how hard it is to do what the PO requests so the PO can adjust the story accordingly. And you might want to bring in the experience of your job and maybe say "but studies have shown comparing dates is easier done in a grid than a list" or "but the design guidelines of the mobile device say it should never be blinking. Maybe we can use bold font instead?".
But in the end, the decision what data to display is a clear cut Product Owner responsibility. How it is displayed is the job of the dev team. Ideally, the whole Scrum team talks about this in the Backlog Refinement Meeting.
edited 1 hour ago
Todd A. Jacobs♦
34.4k333124
answered 1 hour ago
nvoigtnvoigt
3,962918
Backlog Grooming Meeting is a good start. In practice this kind of stuff is often discussed initially outside of the Scrum team during the requirements engineering, before any backlog item is created, and refined during the Grooming.
– Christian Strempfer
1 hour ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "208"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
A designer is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fpm.stackexchange.com%2fquestions%2f26291%2fshould-the-product-owner-dictate-what-info-the-ui-needs-to-display%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
My question is, to what extent should the PO describe the requirements of a UI?
To the extent that the designers know what to design and the programmers know what to program. In your example, "as a user I want to see a list of dates so I can..." seems to be a good user story. Who else would know what the purpose of that user interface is and what data the users need at that point.
Should we (the developers and designers) look to the PO to decide and say what the information in the UI should be?
Yes. Now the Product Owner might not be a technical person. That means you have to provide feedback on how hard it is to do what the PO requests so the PO can adjust the story accordingly. And you might want to bring in the experience of your job and maybe say "but studies have shown comparing dates is easier done in a grid than a list" or "but the design guidelines of the mobile device say it should never be blinking. Maybe we can use bold font instead?".
But in the end, the decision what data to display is a clear cut Product Owner responsibility. How it is displayed is the job of the dev team. Ideally, the whole Scrum team talks about this in the Backlog Refinement Meeting.
edited 1 hour ago
Todd A. Jacobs♦
34.4k333124
answered 1 hour ago
nvoigtnvoigt
3,962918
Backlog Grooming Meeting is a good start. In practice this kind of stuff is often discussed initially outside of the Scrum team during the requirements engineering, before any backlog item is created, and refined during the Grooming.
– Christian Strempfer
1 hour ago
add a comment |
My question is, to what extent should the PO describe the requirements of a UI?
To the extent that the designers know what to design and the programmers know what to program. In your example, "as a user I want to see a list of dates so I can..." seems to be a good user story. Who else would know what the purpose of that user interface is and what data the users need at that point.
Should we (the developers and designers) look to the PO to decide and say what the information in the UI should be?
Yes. Now the Product Owner might not be a technical person. That means you have to provide feedback on how hard it is to do what the PO requests so the PO can adjust the story accordingly. And you might want to bring in the experience of your job and maybe say "but studies have shown comparing dates is easier done in a grid than a list" or "but the design guidelines of the mobile device say it should never be blinking. Maybe we can use bold font instead?".
But in the end, the decision what data to display is a clear cut Product Owner responsibility. How it is displayed is the job of the dev team. Ideally, the whole Scrum team talks about this in the Backlog Refinement Meeting.
edited 1 hour ago
Todd A. Jacobs♦
34.4k333124
answered 1 hour ago
nvoigtnvoigt
3,962918
Backlog Grooming Meeting is a good start. In practice this kind of stuff is often discussed initially outside of the Scrum team during the requirements engineering, before any backlog item is created, and refined during the Grooming.
– Christian Strempfer
1 hour ago
add a comment |
My question is, to what extent should the PO describe the requirements of a UI?
To the extent that the designers know what to design and the programmers know what to program. In your example, "as a user I want to see a list of dates so I can..." seems to be a good user story. Who else would know what the purpose of that user interface is and what data the users need at that point.
Should we (the developers and designers) look to the PO to decide and say what the information in the UI should be?
Yes. Now the Product Owner might not be a technical person. That means you have to provide feedback on how hard it is to do what the PO requests so the PO can adjust the story accordingly. And you might want to bring in the experience of your job and maybe say "but studies have shown comparing dates is easier done in a grid than a list" or "but the design guidelines of the mobile device say it should never be blinking. Maybe we can use bold font instead?".
But in the end, the decision what data to display is a clear cut Product Owner responsibility. How it is displayed is the job of the dev team. Ideally, the whole Scrum team talks about this in the Backlog Refinement Meeting.
edited 1 hour ago
Todd A. Jacobs♦
34.4k333124
answered 1 hour ago
nvoigtnvoigt
3,962918
My question is, to what extent should the PO describe the requirements of a UI?
To the extent that the designers know what to design and the programmers know what to program. In your example, "as a user I want to see a list of dates so I can..." seems to be a good user story. Who else would know what the purpose of that user interface is and what data the users need at that point.
Should we (the developers and designers) look to the PO to decide and say what the information in the UI should be?
Yes. Now the Product Owner might not be a technical person. That means you have to provide feedback on how hard it is to do what the PO requests so the PO can adjust the story accordingly. And you might want to bring in the experience of your job and maybe say "but studies have shown comparing dates is easier done in a grid than a list" or "but the design guidelines of the mobile device say it should never be blinking. Maybe we can use bold font instead?".
But in the end, the decision what data to display is a clear cut Product Owner responsibility. How it is displayed is the job of the dev team. Ideally, the whole Scrum team talks about this in the Backlog Refinement Meeting.
edited 1 hour ago
Todd A. Jacobs♦
34.4k333124
answered 1 hour ago
nvoigtnvoigt
3,962918
edited 1 hour ago
Todd A. Jacobs♦
34.4k333124
edited 1 hour ago
Todd A. Jacobs♦
34.4k333124
edited 1 hour ago
Todd A. Jacobs♦
34.4k333124
34.4k333124
answered 1 hour ago
nvoigtnvoigt
3,962918
answered 1 hour ago
nvoigtnvoigt
3,962918
answered 1 hour ago
nvoigtnvoigt
3,962918
3,962918
Backlog Grooming Meeting is a good start. In practice this kind of stuff is often discussed initially outside of the Scrum team during the requirements engineering, before any backlog item is created, and refined during the Grooming.
– Christian Strempfer
1 hour ago
add a comment |
Backlog Grooming Meeting is a good start. In practice this kind of stuff is often discussed initially outside of the Scrum team during the requirements engineering, before any backlog item is created, and refined during the Grooming.
– Christian Strempfer
1 hour ago
Backlog Grooming Meeting is a good start. In practice this kind of stuff is often discussed initially outside of the Scrum team during the requirements engineering, before any backlog item is created, and refined during the Grooming.
– Christian Strempfer
1 hour ago
Backlog Grooming Meeting is a good start. In practice this kind of stuff is often discussed initially outside of the Scrum team during the requirements engineering, before any backlog item is created, and refined during the Grooming.
– Christian Strempfer
1 hour ago
add a comment |
A designer is a new contributor. Be nice, and check out our Code of Conduct.
A designer is a new contributor. Be nice, and check out our Code of Conduct.
A designer is a new contributor. Be nice, and check out our Code of Conduct.
A designer is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Project Management Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fpm.stackexchange.com%2fquestions%2f26291%2fshould-the-product-owner-dictate-what-info-the-ui-needs-to-display%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
In my opinion that's not a Scrum problem, but how you use your expertise efficiently. From a Scrum perspective it's fine to have clear requirements. From UX perspective you're doing a bad job.
– Christian Strempfer
1 hour ago