-
Office Hours For both Tuesday this week, Office Hours are 10:30 - 10:45 am and 3:15 - 4:15 pm.
-
Resume
If you bring a printed copy of your resume to me during my 3:15 - 5 pm extended Office Hours on Thursday, September 18, I will review it and provide suggestions for improvement.
-
Project 1: Requirements Report
Note the change in due date.
- 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.
So why have some of you submitted your asciinema session?
-
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.
-
Exercise 14: Commit to Project 1 Repository
First word of the commit message: