Watch the planning poker Youtube video - you'll be doing this today
Read through Homework 2 Part 1 and mark down question and points that need clarification. Bring a printout of the assignment to lab
Bring 8 notecards or small pieces of paper to lab. These will be your poker cards. Write the following numbers on the cards, one number on each card: 1, 2, 3, 5, 8, 13, 20, 40
To work with your partner/team on Homework 2 Part 1 by
Performing an inspection on Homework 2 and report "bugs" in the assignment
Estimating the amount of time to complete the tasks/stories and reporting that information
Identifying tasks/stories to complete as part of Homework 2 Part 1
Begin Homework 2 Part 1
Chat with your partner about the "Food for Thought".
Each group should join with another group to form a group of 4-6. Choose someone to be the reader and someone to be the scribe. Read line by line through Homework 2. The scribe records specific questions or problems with the assignment on the Google form.
With the same group you had for the assignment inspection, conduct a planning poker session for Homework 2 part 1. Break up the assignment into logical "chunks" that might be considered one deliverable in your own eyes. Consider a part of the assignment that would take 6 hours to complete to be and "8" and estimate the other parts relative to that part. Someone should assume the role of product owner and discuss what is required for the "chunk" and moderate a discussion with the group about what is believed to be required to complete that chunk. Run a planning poker session to record your estimate for each chunk.
Record the results in each team's GitHub wiki (more information on GitHub wikis can be found on the GitHub help site here). The teaching staff will be looking for the planning poker estimates
With your partner, list the tasks that you will need to complete to finish Homework 2 Part 1. You want to consider fine-grained tasks. A task like "fix UC2" is too broad and should be broken up into the different items that make up fixing UC2. Make sure you include non-coding items, like documentation.
Take the time during lab to start Homework 2 Part 1. You need to stay for the entire lab period. We recommend the following tasks:
Choose an iTrust from your team to start from. Disconnect it from the class repo and share it with the team's repo.
Ensure that all team members can successfully check out a local copy.
Make sure that each person's iTrust is configured and update the .gitignore to avoid pushing .classpath/.project files.
Create bug reports.
Identify the files that will likely need to be modified as part of fixing the bugs.
Write your black box test cases