Transformation of SRS to Agile Requirements, Journey of Caterpillar to Butterfly.....

While we talk about Agile adoption, many teams implement Scrum for product development but still maintain SRS (System Requirements Specification) as a signed of requirements document from customer. Or it is possible to adopt "Slice the cake" option much later in requirements.

How to maintain these SRS and convert to Agile requirements.

Is it enough just to create a story out of SRS and start this as a product backlog, or does it really require re-looking at the way requirements were captures?

Will it take lot of time and effort to convert this SRS document into Agile requirements?

Is there an effective way to transform the existing SRS to Agile Requirements?

Is product backlog same as Agile requirements?? If not what's missing?

This session will answer all of these questions.


Outline/Structure of the Case Study

What is the difference between SRS and Agile requirements? 5 mins

Is Agile requirements same as having a product backlog? 5 mins

Tools and Technique to convert SRS to Product Backlog : 15 mins

What will be missing when you convert SRS to Agile requirements : 5 mins

Case study and lessons learned : 10 mins

Q&A : 5-7 mins

Learning Outcome

Tools and techniques to convert SRS to Agile Requirements

Target Audience

EveryOne :-)

Prerequisites for Attendees

There are no special requisite for this session

schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker
  • Rajiv Bajwala
    By Rajiv Bajwala  ~  1 year ago
    reply Reply

    I like these aspects of the submission, and they should be retained:

    • While this topic is relevant, I think its a big aged
    • Could be a workshop to take people through the process of writing stories from SRS documents

    I think the submission could be improved by:

    • Not sure if this is the right track
    • I think it might not attract enough attendees
    • Sharmila Patwardhan
      By Sharmila Patwardhan  ~  1 year ago
      reply Reply

      This is like hands on session where a sample SRS will be translated to product backlog.

      This involves techniques like impact mapping and story mapping together

      I think its about experience that i have gained in a large complex project.