Every project starts with a Software requirement Specification (SRS) document, but somewhere in the middle a decision to adopt agile methods is made. So the question arises whether an SRS can serve as agile's product backlog? Let's find out. An SRS is a document with all the direct or indirect requirements of the system are listed. It generally has statements like "The system shall.."
Whereas product backlog serves two purposes: 1. It lists the work that is to be done and 2. It prioritizes the work to be done. It is different with the SRS in the sense that SRS only tells about what work which is to be done, not the priorities. So just for the sake of adopting agile, SRS should not be mixed with user stories, instead a product backlog should be created which will serve the purpose well. To know more, read the article by Mike Cohn (founder of Mountain Goat Software), at: https://www.mountaingoatsoftware.com/blog/can-a-traditional-srs-be-converted-into-user-stories#