Collaborative Application Development: 5.3 Group Lab 1

Trivia - Sprint 2

  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 1' sprint in your team’s JIRA project
    3. Create a Sprint in your team’s JIRA project called 'Trivia - Sprint 2'
    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. Convert the existing trivia questions into a format the application can use.
        1. Take the trivia questions that were created as part of sprint 1, and put them in a multidimensional array variable. The format can be found in dataReader.js.
        2. Verify that the correct answer is specified for each question.
      2. Add the data reader to the project.
        1. Add the dataReader.js file to the project in the js folder.
        2. Add a reference to the dataReader.js file in the index.html page.
        3. Create a global variable which is set to the value returned when opening the trivia records in dataReader, passing the trivia questions array as a parameter.
      3. Create at least four unit tests for dataReader.
        1. Before you begin writing unit tests for dataReader, you will need to add references to dataReader.js to the unit test web page.
        2. Create an array with hard-coded trivia data. Use this array in your unit tests, e.g. comparing to ensure that the correct question is returned from dataReader. This can be done since the data is hard-coded and the correct answer is known, all within the scope of the unit test.
        3. Some potential unit test ideas: returning a question, returning a valid correct answer (A, B, C or D), returning four answers and returning a question.
      4. Rename the getRandomQuestion function to loadRandomQuestion. In that function, change the logic to get a random question (utilizing the dataReader). Then within that function, load the question and answers onto the page in the correct areas (e.g. answer A should be in the A tile).
      5. Add support for telling the user if they answered correctly.
        1. Update the checkAnswer function to compare the answer that the user clicked on with the current correct answer from the dataReader.
        2. Remove the code that converted the answer letter to an index (e.g. A = 0).
      6. Add a “50/50” button.
        1. When the user clicks the button, remove the text from two of the tiles which contain incorrect answers. One correct and one incorrect answer should remain visible.

          2. There are many ways that this can be done. Feel free to be creative.

      7. Add a “Phone a friend” button.
        1. Utilize the site Let Me Google That For You as the user’s “friend”.

          2. http://lmgtfy.com

        2. When the user clicks on the button, open the Let Me Google That For You site in a new tab. Pass the question as a parameter in the URL when opening the site (e.g. http://lmgtfy.com/?q=what+color+is+the+sky)
          1. Spaces in the question will need to be replaced with the plus (+) character, and the question mark at the end (if there is one, should be removed). Use JavaScript to accomplish this.
      8. When the user clicks an answer tile, show an alert message with either “Correct!” or “Incorrect!” based on the logic in the checkAnswer function.
    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 2'
      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. Coordinate with your team to tag the final commit of the sprint with 'Trivia - Sprint 2 end', or something similar.
    2. 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. To submit:

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