Should the Product Owner dictate what info the UI needs to display? Announcing the arrival of...
How can I wire a 9-position switch so that each position turns on one more LED than the one before?
How do I reattach a shelf to the wall when it ripped out of the wall?
Can a level 2 Warlock take one level in rogue, then continue advancing as a warlock?
My bank got bought out, am I now going to have to start filing tax returns in a different state?
Is Diceware more secure than a long passphrase?
How long after the last departure shall the airport stay open for an emergency return?
Does Mathematica have an implementation of the Poisson binomial distribution?
Suing a Police Officer Instead of the Police Department
Why does Arg'[1. + I] return -0.5?
What is the best way to deal with NPC-NPC combat?
A strange hotel
A faster way to compute the largest prime factor
How do I prove this combinatorial identity
I preordered a game on my Xbox while on the home screen of my friend's account. Which of us owns the game?
Is it acceptable to use working hours to read general interest books?
`microtype`: Set Minimum Width of a Space
Retract an already submitted recommendation letter (written for an undergrad student)
What is /etc/mtab in Linux?
Why do distances seem to matter in the Foundation world?
Is there really no use for MD5 anymore?
Can I criticise the more senior developers around me for not writing clean code?
A Paper Record is What I Hamper
Philosophical question on logisitic regression: why isn't the optimal threshold value trained?
How to avoid introduction cliches
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 36 mins ago
Sarov
9,74932143
asked 47 mins ago
A designerA designer
111
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 36 mins ago
Sarov
9,74932143
asked 47 mins ago
A designerA designer
111
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
37 mins 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 36 mins ago
Sarov
9,74932143
asked 47 mins ago
A designerA designer
111
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 36 mins ago
Sarov
9,74932143
asked 47 mins ago
A designerA designer
111
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 36 mins ago
Sarov
9,74932143
asked 47 mins ago
A designerA designer
111
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 36 mins ago
Sarov
9,74932143
edited 36 mins ago
Sarov
9,74932143
edited 36 mins ago
Sarov
9,74932143
9,74932143
asked 47 mins ago
A designerA designer
111
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 47 mins ago
A designerA designer
111
asked 47 mins ago
A designerA designer
111
111
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
37 mins 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
37 mins 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
37 mins 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
37 mins 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 21 mins ago
Todd A. Jacobs♦
34.4k333124
answered 35 mins ago
nvoigtnvoigt
3,952918
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
28 mins 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 21 mins ago
Todd A. Jacobs♦
34.4k333124
answered 35 mins ago
nvoigtnvoigt
3,952918
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
28 mins 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 21 mins ago
Todd A. Jacobs♦
34.4k333124
answered 35 mins ago
nvoigtnvoigt
3,952918
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
28 mins 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 21 mins ago
Todd A. Jacobs♦
34.4k333124
answered 35 mins ago
nvoigtnvoigt
3,952918
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 21 mins ago
Todd A. Jacobs♦
34.4k333124
answered 35 mins ago
nvoigtnvoigt
3,952918
edited 21 mins ago
Todd A. Jacobs♦
34.4k333124
edited 21 mins ago
Todd A. Jacobs♦
34.4k333124
edited 21 mins ago
Todd A. Jacobs♦
34.4k333124
34.4k333124
answered 35 mins ago
nvoigtnvoigt
3,952918
answered 35 mins ago
nvoigtnvoigt
3,952918
answered 35 mins ago
nvoigtnvoigt
3,952918
3,952918
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
28 mins 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
28 mins 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
28 mins 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
28 mins 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
37 mins ago