This question is in reference to Atlassian Documentation: Product Requirements Blueprint
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!
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:
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs