Sprint Documentation Example 2018 PDF

Preview

Summary

assignment specifications...

Description

Team Name Iteration/Sprint Documentation (Example) Incoming Product Backlog These may be listed in priority order, or include a written priority such as low, medium, high, critical Include your complete backlog. It’s fine if it’s a few pages

US1: As a user, I want to create a new shopping cart from my existing login so that I can purchase items US2: As a user, I want to retrieve any of my shopping carts quickly, so that I can review them US3: As a user, I want to update an existing shopping cart, so that I can correct or amend the items US4: As a user, I want to delete an existing shopping cart, so that I can remove it completely US5: As a user, I want to create a login to do online shopping

Wishlist, Theme or Increment goals This is an indication of the major goal or theme of this sprint. It’s a good idea to try to get a few related pieces of functionality done at the same time so you can maintain your mental model of the data flows, user experience, etc. Early on, consider what your minimum viable product is and work towards that. Resetting passwords and messaging can wait for later.

Theme: Create registered user capable of creating shopping cart for adding the selected items

Sprint Backlog These are the more refined backlog items chosen for this sprint. This list is selected by the team during the planning meeting based on the goals and the product owner’s vision, and reflects what you think you can get done through the sprint. Note that the task identifiers (T1, T2 etc) are optional but may be useful for you to communicate about tasks. If you are using a tool these might be generated automatically

Requirement

Conditions of satisfaction

Tasks

US5 As a user, I want to create a login to do online shopping

Login link exists on homepage

T1 The web based form should be present in the web page for the user to enter their personal information – 1 day (Jane) T2 The user should be able to submit the form online, which should create details in the database – ½ day (Ella)

Clicking that link leads to a registration form. The form should send an email to the user’s entered email id for verification. Once verified, the user should be able to login using the username/password

Sprint Documentation Example 2018

CRICOS Provider No. 00103D

Page 1 of 3

T3 Create user table in the database with the necessary meta data – ½ day (Lucy) T4 Create web page to show the successful creation of the login – 1 day (Jane) US1 As a user, I want to create a new shopping cart from my existing login so that I can purchase items

When logged in and an item is selected for purchase, a new, empty shopping cart is created

T5 Design data model of shopping cart T6 Create shopping cart tables in the database etc

Review meeting This meeting is where the work that has been implemented is reviewed by the client and/or other stakeholders. It is critically important that the stakeholders and the team share the same idea of what it means to be “done” here. Is it done, ready to ship and completely ready, or is it at a prototype stage and will continue to receive updates. This “definition of done” is something that needs to be established by the team and communicated clearly to the client.

Sprint 1 - Create registered user capable of creating shopping cart for adding the selected items Date and time: 26/04/2018, 1:30 pm Venue: Client’s premises / Skype conversation / Meeting space Attendees: Tom, Mark & Sam

Apologies: Donald

Minutes taken by: Cam F Agenda item 1: Demonstration feedback: The front page should have different colour. The navigation needs bread crumbs. The shopping cart should appear at the top. Overall the client was happy with the demo. Peter V suggested automatically creating a cart for anonymous/public users too. Client agrees

Agenda item 2: Theme of next sprint Client suggested next highest priority is to be able to add products to the database so they can start working on adding their stock. Cam F suggested that this could be started immediately in Excel with the appropriate spreadsheet design, and client agreed. Richard D suggested time better spend working on the public-facing site and next priority should be displaying the products and further implementing shopping cart. Client happy with this direction Agenda item 3: Next review meeting Scheduled for 20/05/2018 at 1:30 pm

CRICOS Provider No. 00103D

Page 1 of 3

Retrospective meeting The retrospective meeting is a team-only review of the development process itself. It’s not really about the product but the team. Date and time: 26/04/2018, 1:30 pm Venue: Client’s premises / Skype conversation / Meeting space Attendees: Tom, Mark & Sam

Apologies: Donald

Minutes taken by: Cam F Item 1: What went well? •

The client demo went well.

•

The team finished the task as expected

•

The development team found the estimation was good responsible

Item 2: What could be improved? •

The estimation should be improved for the design team.

•

The monitoring of the task should be done regularly by the product owner.

•

The documentation team should do the task well before the due dates • Any last minute preparation should be avoided.

Item 3: What can we do? •

The documentation should be started based on the template

•

The test cases have to written before the code development.

Item 4: What is not in our control? •

The compatibility of the software is not known to the development team until the installation. • Falling sick during the sprint

Please note: whatever you mentioned under the question “what is not in our control?” should be addressed in the next sprint to mitigate the risk imposed by the events which are not under your team’s control.

Backlog grooming meeting The “Product Backlog Grooming” meeting is where you assess the backlog items as a team, remove any that are no longer necessary, reprioritize based on the sprint outcomes and client feedback, and otherwise get ready for the next sprint.

CRICOS Provider No. 00103D

Page 1 of 3...