Assessment Description This is a Collaborative Learning Community (CLC) assignment. Review "Release Planning and User Stories" located in the Topic 3 Resources for additional information on completing this assignment. Directions: Now that the HLA is complete, it is time to further divide the backlog into feature releases and to develop user stories for sprint planning. This will be a prerequisite to creating your project in Jira in Topic 4. For this assignment your team should: 1. Hold a release planning meeting. 2. Create the release plan for the project. 3. Using the "User Stories and Release Plan" template, develop an epic with three user stories, which will later be used to plan the team's iterations or sprints. See "Resources for Holding Virtual Meetings," located in Class Resources, for suggestions related to holding your release planning meeting. Submit your completed "User Stories and Release Plan" template. APA style is not required, but solid academic writing is expected. This assignment uses a rubric. Please review the rubric prior to beginning the assignment to become familiar with the expectations for successful completion.

MGT-641: Release Planning and User Stories

The software team supporting the purchasing of tickets for the March 2050 launch might tructure their epic like so: Concurrently, the propulsion teams might contribute to the same epic with these stories: The format of the user story is standard. The team should identify who the user is, what they want, and why they want it. The formula is as follows: User Story with Acceptance Criteria and Acceptance Testing Example: User Story: As an end user, I want to access the human resource database to generate reports so that I can periodically update the company's staffing contact list. Acceptance Criteria: - Ability to gain access to human resource database - Ability to generate a report which includes - Employee names 0 Dates of birth - Social security numbers 0 Addresses - Telephone numbers - Ability to use report data to update staffing contact list Acceptance Testing: - Database is accessible internally but not from outside company firewall - MS Access report can be generated from database based on query inputs - MS Access report data can be exported to MS Excel spreadsheet - Staffing contact list updates contain only most recent data from the database Release Planning Your timeline will be in weeks vs. months. It is a draft of the Epic Roadmap you will create in Topic 4 in Jira. Release Plan Example Release planning also logically contributes to finalizing the Epic Roadmap and Sprint planning later in the process. (While the terms sprint and iteration may be used interchangeably, this course will use the term sprint). Agile teams will plan their sprints based on releases with the goal of making sure release features are ready on time. Review the following Atlassian: Jira Support examples, located in the Topic 3 Resources: - "Stories, Epics, and Initiatives" - "User Stories With Examples and a Template" - "Agile Epics: Definition, Examples, and Templates" - "Using Agile Workflows for Fun \& Profit" Optional resources also available in the Topic 3 Resources that provide more information on user stories include the following information: - "Agile In Practice: Story Cards/User Stories" - "Mountain Goat Software: Frequently Asked Questions