Tammy, Sounds like your team is doing a great job of hitting the core issues and the sections you list are the great foundation for a planning document. Many of the items you list are contained as part of the BA approach (as opposed to the BA plan in the BABOK which is specific to the deliverables to be created). For my thoughts and reader comments on the BA Approach task, check out this post: http://www.bridging-the-gap.com/the-babok-might-not-be-a-methodology-but-the-ba-still-needs-one-babok-2-1/

You might also check out this post for some more ideas (and the webinar referenced if you are an IIBA member): http://www.bridging-the-gap.com/leading-through-transparency-the-value-of-a-requirements-management-plan/

For each section you list, you might start by asking, “what decisions do we need to make?”” and “what information do we need?” and “how is that information going to be shared/approved/etc”. Those questions should lead you from a list of sections for your document towards a structure for each section.

This is something a mentor could definitely help you with too. For more information on our mentoring program, check out this page: http://www.bridging-the-gap.com/business-analyst-career-mentor/

A few other thoughts:
-In addition to stakeholders, consider what other sources of requirements-related information are necessary. Are there documents, competitive products, etc that are also sources of requirements? If so, how will you obtain requirements-related information from these sources?
-In lieu of “documentation” you might clarify this as “deliverables.” Often we create documentation such as meeting notes that are not formal deliverables. Your plan may or may not need to lay out non-deliverable documentation that’s created as part of a project.

I look forward to hearing how your initiative goes. Sounds like a great career opportunity! Be sure to check back with us and let us know what you find.

Thanks for sharing Michelle! Great point that as an individual BA we often need not just a plan for a project but some sort of tool to keep all of our projects organized and make sure we stay current on all of them based on priorities and critical path. Sounds like you are planning on multiple levels!