AgileProject_Development...

I have a bugzilla ticketing system that has about 100 tickets.
Some are bugs and some are enhancements to an existing system.

We started using agile development and scrum framework for new software and existing  maintenance...
We used to use rapid development and waterfall before this.

I was tasked to create baseline product backlog, baseline software specs, sprint plans, release targets, etc. that is required by scrum.

Do you know any site links or have any sample examples for small system that show how to do this starting with the product backlog?
sam15Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jessica RigaProducerCommented:
Those 100 tickets are the start to your backlog! The good news is in Scrum most of what you're after should be done collaboratively with your team. So while you may be the facilitator, don't go do all that work on your own in a vacuum!

To get you started I recommend this book.  

There are some great articles and blog posts available on Mountain Goat Software.

This video is a solid overview of the Product Owner role, which it sounds like you're in.

I've also attached Peter Hundermark's "Do Better Scrum" from InfoQ, and "What Every Product Owner Should Know" by ScrumSense to help get you started.
Do-Better-Scrum.pdf
What_Every_Product_Owner_Should_Know.pdf

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sam15Author Commented:
Excellent Links. BTW, I do have that book you referred to. It is good but lacks some real-life examples.

 It seems you are saying that each ticket in the systems becomes a feature on the baseline product backlog?
I thought each requirements might end up with one or more features on the backlog depending on level of detail.

Do  the detailed tasks for each Backlog Item go into the Sprint plan or Baseline software specifications?

There are also some acrobats called traceability and accessibility matrix Which I did not know what for. Do you know what those should include?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Agile

From novice to tech pro — start learning today.