# Strategic Planning

In the context of agile development and a Consortium with a diverse set of members, the application of various agile-development terms may mean different things to different individuals.

The table below defines the BDC Core Terminology:

| **Term**       | **Definition/Description**                                                                                                                                                                                                                                              | **Example**                                                                                                                                                           |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| User Narrative | Descriptions of a user interaction experience within the system from the perspective of a particular persona. User Narratives are further broken down into Features, Epics, and User Stories.  Currently formulated into rough 6-month timelines to benchmark progress. | An experience bioinformatician wants to search TOPMed studies for a qualitative trait to be used in a GWAS study                                                      |
| Feature        | <p>A functionality at the system level that fulfills a meaningful stakeholder need</p><p>\*Level at which the BDC3 coordinates</p>                                                                                                                                      | Search TOPMed datasets using PIC-SURE platform                                                                                                                        |
| Epic           | <p>A very large user story which can be broken down into executable stories</p><p>\*NHLBI’s cost-monitoring level</p>                                                                                                                                                   | PIC-SURE is accessible on BDC                                                                                                                                         |
| User Stories   | <p>A backlog item that describes a requirement or functionality for a user</p><p>\*Finest level of PM Monitoring </p>                                                                                                                                                   | A user can access PIC-SURE through an icon on BDC to initiate search                                                                                                  |
| Workstream     | A collection of related features; orthogonal to a User Narrative                                                                                                                                                                                                        | <p>Workstreams impacted by the User Narrative above include:</p><ul><li>production system</li><li>data analysis</li><li>data access</li><li>data management</li></ul> |

![](/files/-MSQNN0y27R3XvSggCjT)

{% file src="/files/-MSQNpAV7V0-XJ5tF7Sq" %}
Project Management Approach PDF
{% endfile %}

### Strategic Planning Documents Reviewed & Approved by NHLBI Leadership

{% file src="/files/-MSQO\_2spal\_snzJZC4b" %}

{% file src="/files/-MSQOijxZ4YQKKDFlJo1" %}

{% file src="/files/-MSQOqTObVjOCSU52OF1" %}

{% file src="/files/-MSQP0tne403SO3b\_J09" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bdcatalyst.gitbook.io/biodata-catalyst-documentation/community/strategic-planning.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.