This question is in reference to Atlassian Documentation: Product Requirements Blueprint
Hi all,
In our company we're in the process of going from a traditional product waterfall planning to an Agile / Scrum implementation.
With this in mind, I'm struggling to convince my colleagues that this "Product Requirements Blueprint" is not really appropriate when wanting to move to Scrum.
What do you think?
Thanks for your input!
Jacques.
Agile is about adaptation. In some context, you have to write requirements (and this is why I'm the author of an add-on on that topic).
What I find nice about Atlassian's blueprint:
So in my opinion, yes, this PRD blueprint and similar Customer Interview pages fit very well in an Agile/Scrum environment. However:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.