Week 4 Class 8 Thu Sep 17 Posted: Sep 17
After Class
- Project 1 The screencast for using asciinema is for an old version. I will demonstrate in class on Tuesday how to run it. The due date for the URL of the asciinema session is extended to 11:59:59 pm on Tuesday, Sep 22. The due date for the project commits to GitHub stays the same.
Announcements
-
Exercise 13: Commit to Project 1 Repository
-
Project 1: Requirements Report
- Include all user stories, even those without estimates. If a user story does not have an estimate, leave the estimate value blank.
- Project 1 is not a team project. They only thing that you share with your team is the user story cards. Everything else originates from you. Do not set a team template for this.
- This is a report about the team results and process, not your individual results and process.
- The first two sections will be shown to the customer. Those sections should only contain information the customer is allowed to see. You will lose a significant number of points if you do not follow this rule.
- All user stories belong to the team. This is a report of the current state of your team project.
- There is no "my user story". All user stories belong to the team, actually the customer.
- The customer is not interested in tasks, only the user stories.
- The report should be readable and consistent both in markdown and displayed as a web page at GitHub.
-
Project 1 asciinema session The asciinema session is after you complete Project 1. Since you are still performing estimation, you are not done with the user stories for Project 1.
-
Estimates
- Estimation in software development is not about finding the minimum time it would take you to complete a user story. It's about understanding and predicting the genuine effort required in the context of a 5-day week 50 weeks a year. Remember, an estimate is not a speed challenge but rather a measure of how long it will realistically take to completely implement a user story.
- Avoid the trap of only considering the quickest or simplest implementation. Proper estimation requires thoughtful consideration of all possible complexities. Moreover, completing a user story quickly doesn't mean the rest of the day is free; there's always another user story waiting. This is not a class assignment or a lab exercise where once you are finished you are done for the day.
- Refrain from using phrases like "All we have to do …” when discussing software tasks. Such assumptions oversimplify the complexities of coding.
Class
Unless stated otherwise, all exercises are due by 4 pm on Fri Sep 18