Login
Register
Scrum.org
Menu
Community
Community Blogfeed
Community Events
Community Publications
Forums
Scrum Guides
FAQs
Change the Scrum Guide
Resources
What is Scrum?
Scrum Glossary
Definition of Done
Scrum and Agile Webcasts
Courses
Professional Scrum Foundations
Professional Scrum Master
Professional Scrum Product Owner
Professional Scrum Developer
Java - Topics Covered
.NET - Topics Covered
Assessments
Open Assessments
Scrum Open Assessment
Developer Open Assessment
Professional Scrum Master Assessments
PSM I Assessment
PSM II Assessment
Professional Scrum Product Owner Assessments
PSPO I Assessment
PSPO II Assessment
Professional Scrum Developer Assessments
PSD I Assessment
PSD Objective Domain
Scrum.org Certifications
About
News
Mission/Vision
Contact Us
Work With Us
Trainers
Partners
Careers
Logo & Links
Forums
By posting to our forums you are agreeing to the
Forum terms of use.
Forums
Search
Unanswered
Active Topics
Forums
>
Discussion Forums
>
Scrum
Product backlog for prototypes, no SW development
Last Post 07 Jan 2013 08:46 AM by Mikkel Toudal Kristiansen. 1 Replies.
Sort:
Oldest First
Most Recent First
Prev
Next
You are not authorized to post a reply.
Author
Messages
Carlos Diaz
New Member
Posts:1
04 Jan 2013 05:26 PM
Hi all,
Do you have practical example of how to generate the product backlog on product development (not software), as not sure how the stories should be generated.
thanks in advance :)
Mikkel Toudal Kristiansen
New Member
Posts:7
07 Jan 2013 08:46 AM
I am not sure I fully understand your situation.
It sounds to me like you want to run Scrum on a innovation/concept project, that has nothing to do with software development.
If that is the case, I am not sure if Scrum is fully suited to your needs, but these would be my advices:
1. You need to know something about what the project needs to produce. If the expected outcome of the project is a design for a new system or tangible thing, then so be it.
2. Add product backlog items to the product backlog, that represents value to the product owner/customer. This could be along the lines of "Design a log-in mechanism for the system", "Design a My Profile page for the system", etc.
3. Make sure the team creates and refines a Definition of Done, so it is well understood what kind of output the team can be expected to deliver, both at the end of each sprint, but also at the end of the project.
Anyway, more details would be very welcome.
Kidnest regards, Mikkel
You are not authorized to post a reply.
Discussion Forums
--Scrum
--Scrum.org
Forums
>
Discussion Forums
>
Scrum
Community
Community Blogfeed
Community Events
Community Publications
Forums
Feedback