Create WM Story

Published on August 24, 2026 Agile Manager

Creating a WM Story

A WM Story represents a feature, requirement, or user story that your team needs to deliver. Stories break down the work into units that team members can complete within a sprint. Each story is linked to a specific sprint and can have tasks, acceptance criteria, and test cases associated with it.

📚 Create a New WM Story

Follow these steps to create a story within a sprint:

1. Open Agile Manager
   Click the App Launcher (9-dot grid icon) and select Agile Manager.
2. Navigate to Sprints
   In the navigation menu, click on WM Sprints or go to your Releases and open a sprint from the related list.
3. Open the Sprint
   Click on the specific sprint record where you want to add stories.
4. Scroll to Stories Section
   On the sprint detail page, scroll down to find the WM Stories related list.
5. Click New Story
   Click the New button in the WM Stories section to open the story creation form.

6. Fill in Story Details
   Enter the following information:
   • Story Name/Title: A clear, descriptive name for the story (e.g., "User Login with SSO")
   • Story Description: Provide context about what needs to be built and why
   • Story Points/Effort: Estimate the complexity or effort required (e.g., 5 points, 8 points)
   • Priority: Set as High, Medium, or Low based on business importance
   • Assigned To: Assign the story to a team member (optional at creation)
   • Status: Mark as Not Started, In Progress, or Completed
7. Save the Story
   Click Save. The story is now created and automatically linked to your sprint.

📌 Next Steps After Creating a Story

Once your story is created, you can:

• Add Tasks: Break the story into smaller tasks that team members can work on
• Write Acceptance Criteria: Define what "done" means for this story
• Create Test Cases: Design tests to verify the story meets requirements
• Assign Team Members: Add developers, QA, and other roles to the story
• Track Progress: Update the status as work progresses through the sprint

💫 Writing Good User Stories

• Use the User Story Format: "As a [user type], I want [feature], so that [benefit]"
• Be specific: Avoid vague descriptions. Include details about what the user needs to accomplish
• Set realistic size: Stories should be completable within a sprint (typically 2-8 story points)
• Include acceptance criteria: Clearly define when the story is considered "done"
• Link to business value: Explain how the story delivers value to users or the business

Knowledge Article Number: KA-00361