Agile for a mixed IT/non-IT teams

Last post 06:55 pm September 12, 2018 by Ian Mitchell

1 reply

11:50 am September 12, 2018

Hi everyone,

I work for a company who makes medical appliances. These appliances contains both SW and engineering/HW parts. Although, we follow Scrum in our SW teams but it becomes a problem since most of our products also involves task for the engineering teams. I just want to know how to use agile in such conditions? Should we have product owners in respective engineering and research teams? So that when a Product Manager for medical scanner machines comes up with a business feature than all POs from SW, engineering and research should derive their user-stories (tasks) on their own and manage separate backlogs? Please help.

Ian Mitchell

06:55 pm September 12, 2018

In Scrum, there should be exactly one Product owner for each Product which is represented by exactly one Product Backlog. Unless increments of hardware and software can be released separately to provide value in their own right, they’ll likely constitute the same product.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.