Spaces:
Sleeping
Sleeping
Update Templates.py
Browse files- Templates.py +7 -1
Templates.py
CHANGED
@@ -16,7 +16,13 @@ user_story_template = """Given the project details with the following parameters
|
|
16 |
**RFP details:**
|
17 |
{rfp_details}
|
18 |
|
19 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
20 |
|
21 |
**Examples**
|
22 |
|
|
|
16 |
**RFP details:**
|
17 |
{rfp_details}
|
18 |
|
19 |
+
Analyze the given RFP details and identify the high-level epics or themes for the project. For each epic, break it down into distinct features, and further decompose each feature into the smallest possible requirements that adhere to the INVEST principles (where I refers to Independent (not dependent on other work deliverables), N refers to Negotiable (allows for best practices), V refers to valuable (provides working functionality), E refers to Estimable (allows clear work estimates), S refers to Small (sized for the team's sprint), T refers to Testable (can be measured to ensure it meets customer expectations)).
|
20 |
+
|
21 |
+
Craft a single user story for each requirement using the format below:
|
22 |
+
"As a [specific user role or stakeholder], I want to [perform one clear, distinct action or functionality], so that [articulate a precise business value or benefit]."
|
23 |
+
|
24 |
+
These user stories should encapsulate standalone, testable units of work that embody distinct functionality. Each story must represent a unique and essential aspect of the system, ensuring clarity and avoiding redundancy. Keep the focus on a singular responsibility or objective in each user story, ensuring its manageability and testability. Avoid using conjunctions like "and" or "or" in the "I want to" clause, as they often indicate multiple functionalities within a single story.
|
25 |
+
|
26 |
|
27 |
**Examples**
|
28 |
|