Collaborative Application Development: 6.1 Group Lab 1

Trivia Sprint 3

  1. Planning and preparation.

    1. Pull the latest changes from your team's Git repository (clone first, if necessary).
    2. Complete/Close the current 'Trivia - Sprint 2' sprint in your team’s JIRA project
    3. Create a Sprint in your team’s JIRA project called 'Trivia - Sprint 3'
    4. Drag the issues from the backlog into the sprint
    5. Create an issue in Jira for each of the following sprint tasks.

      6. Create the issues using the specified type - Task, Bug or User Story. If a user story, ensure that the correct user story format is being used.

      1. Add CSS functionality to the page that looks elegant whenever a user answers a question.
        1. If the user answers correctly, color the correct "tile" a distinct green.
        2. If the user answers incorrectly, highlight the tile they clicked a distinct red, and highlight the correct tile green.
      2. Delay the loading of the question until the user is ready.
        1. Add a start button to the page.
        2. When the start button is clicked, populate the page with a question.
        3. Whenever a game is in progress, the start button should be hidden.
      3. Allow stopping the trivia game.
        1. Add a stop button to the page.
        2. The stop button should only be visible when a game is in progress.
        3. When the stop button is clicked, clear all question data from the page.
      4. Subtract points if the user answers incorrectly.
        1. Subtract three points from the score on the page when the user answers incorrectly.
        2. If the user's score goes below zero, display an alert message on the screen saying "Sorry, you lost!", or a similar message.
      5. Allow the user to navigate to the next question.
        1. Add a "Next Question" button to the page.
        2. The button should only be visible when a game is in progress.
        3. If the user clicks the button, use the dataReader to get the next question.
      6. Track consecutive correct answers.
        1. If the user has answered five questions correctly in a row, alert the user with a message such as "Wow, five in a row!"
      7. Create a build script for the project.
        1. Add a build script and the required files to a “build” folder within the site.
        2. The build script should copy all needed files into a “.release” folder within the “build” folder. CSS file(s) should be compressed and JS files should compressed and obfuscate.
      8. Deploy the site.
        1. Using the build script, build the project.
        2. Copy the files from the .release folder to your team’s FTP location.
        3. Run the deployed site and test it, ensuring that everything functions as specified and that the files are compressed and obfuscated.
    6. Use the story point range of 1,2,4,8,16 (to represent Extra Small, Small, Medium, Large, Extra Large)
    7. Assign the issues as evenly as possible within your team.
    8. In the backlog, drag and drop all of the issues created into the sprint.
    9. Start the sprint
      1. For the Sprint Name specify 'Trivia - Sprint 3'
      2. For the Start Date, specify today's date
      3. For the End Date, specify the date of one week from now
  2. Work.

    1. View your team project board in Jira (showing the 'To Do', 'In Progress' and 'Done' columns).
    2. Drag and drop each issue from 'To Do' to 'In Progress' when starting work on the issue, and from 'In Progress' to 'Done' when completing the issue. Add comments to the issues as needed.
    3. Commit your code changes to the Git repository often (at least once per Jira issue). When committing your code changes to the Git repository, specify a description of the change and the issue number from Jira in your commit message, such as 'CADSB-9: Updated page title'.
    4. After completing each task, push the changes up to the remote repository so your team members can access them.
  3. Wrap up and sprint retrospective.

    1. Discuss the following items within your group.
      1. What worked well this sprint?
      2. What didn't work well this sprint (e.g. Git issues, Jira issues, poor communication, etc.)?
      3. What will you do differently next sprint?
  4. Once finished with this week's group work, please complete a peer-review for each member of your group (including a self-evaluation). See the attached peer-review document. You will make a copy of this for each member in your group, along with yourself, and complete each one to your best abilities.

  5. To submit:

    1. Submit the assignment via Blackboard with a note letting the instructor know that the work is completed and ready for grading.