[Pulp-dev] Roadmaps for plugins

Robin Chan rchan at redhat.com
Mon Oct 16 20:17:38 UTC 2017


During our internal Pulp meeting this year, we discussed creating a roadmap
for plugins.  I would like to capture our discussion and ask for feedback
so that we can start working on our first few roadmaps for plugins.  We
hope that this will be an iterative approach to planning and creating
roadmaps, extending it to other plugins or core if they are helpful.

*Why? - What will a roadmap help do?*
Communicate relative priority of work for a plugin
Determine MVP (for Pulp 3) for a plugin
Help identify dependencies on work outside of the plugin
Capture architectural decisions especially when departing from past Pulp 2
implementations (was this implied in conversation? writing this out is
Provide direction with the understanding that work planned farther in
future is subject to change.

EPIC level descriptions of work - so not user stories, not tasks, not use
Describe major functionality delivered in an order
Use y release descriptions for EPICs

What did I forget to add?  What else would be helpful to add to a roadmap,
take away, or state that it would be described/accounted for elsewhere?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20171016/a9d37327/attachment.htm>

More information about the Pulp-dev mailing list