Personal Finance Manager Sprint Two (Part Five)

Content

Defining Sprint Two

Summary

In Sprint One we create a model project with one database entity defined the 'Owner' class. It was added to Git source control, tested and installed. We also created a persitance layer project and installed it in our local maven repositor. For Sprint two we will further develop our PFM application by creating a web application that will make use of these two maven projects.

Defining Sprint Two

In Sprint two we will continue with the Account Owner Epic and complete the User Stories from Sprint One so that the Acceptance Criteria are realised for each Story. We also add Epic 3, Web Application. Here then is our definition of Sprint Two.

  1. Epic Entity CRUD Operations

    Epic 1a Account Owners CRUD

    User Stories

    1. Create New Account Owner
    2. Read Account Owner Information
    3. Update Account Owner
    4. Delete Owner
  1. Epic Web Application
    This Epic has not been defined with lower level User Stories yet so we will add some here for Sprint Two.

    Epic 4a Web Application Views

    User Stories

    1. Account Owners List View
      As a PFM APPLICATION USER, I want to VIEW A LIST OF ACCOUNT OWNERS so that All PFM ACCOUNT OWNERS IN THE PFM APPLICATION CAN BE VIEWED IN A WEB BROWSER

      Acceptance Criteria 1
      Given that Account Owners exist within the application
      When the application user selects this view
      Then the application will display a listing of all the existing Account Owners
      And each Account Owner within the listing will contain a link to the View Account Owner Information View.
    2. Account Owners Create New View
      As a PFM APPLICATION USER, I want to CREATE NEW ACCOUNT OWNERS so that ACCOUNT OWNERS CAN BE ADDED TO THE PFM APPLICATION

      Acceptance Criteria 1
      Given the application user has sufficient permissions
      When the application user selects this view
      Then the application display a form for adding a new Account Owner
      And when the user submits the form the entered information is validated and added to the PFM application database.
    3. Account Owner Details View
      As a PFM APPLICATION USER, I want to VIEW ACCOUNT OWNER DETAILS so that THE ACCOUNT OWNER PERSISTED DETAILS CAN BE VIEWED IN A WEB BROWSER

      Acceptance Criteria 1
      Given that Account Owners exist within the application
      When the application user selects an Account Owner in the List View
      Then the application will present a read only view displaying the Account Owner details
    4. Account Owner Edit Details View (Update)
      As a PFM APPLICATION USER, I want to UPDATE ACCOUNT OWNER DETAILS so that ACCOUNT OWNER DETAILS CAN BE MANAGED WITHIN A WEB BROWSER

      Acceptance Criteria 1
      Given that Account Owners exist within the application
      When the application user selects this view
      Then the application will present a view displaying the Account Owner details that may be modified by the user
      And when the user selects 'save' the new information will be persisted
    5. Delete Account Owner View
      As a PFM APPLICATION USER, I want to DELETE ACCOUNT OWNERS so that ACCOUNT OWNERS CAN BE REMOVED WITHIN A WEB BROWSER

      Acceptance Criteria 1
      Given that Account Owner does not have any related Accounts
      When the application user selects delete for this Account Owner
      Then the application will display a confirmation request to delete the Account Owners
      And the Account Owner will be deleted from the application if the confirmation is confirmed

    Tasks

    1. Create a maven project for the web application
  1. Epic Software Configuration Management

    Epic 1a Account Owners CRUD

    Epic Tasks

    1. Add web application project contents to a git project.
    2. Create a feature branch for development of Owner Entity views.

This defines Sprint Two which will be developed on the following page, click next arrow to continue.

Date Entered2014-06-09