Lab Date: Monday, February 19
Time to start your first sprint and get going on the project! This first sprint should be based around project and technology discovery.
Finish up your user stories! Think about your risks! Be ready to discuss these with your TAs!
Requirements Managers: Make sure your YouTrack board is ready to go. You will probably be creating a few more stories today. You will definitely be moving cards to be assigned to particular people.
Scrum Masters: You should read up on how to run a scrum stand-up meeting. Check these out, paying special attention to the 3 questions.
Technology Managers: This week you're going to be doing a deep-dive into the tech you'll be using. You'll need to task the others in the team with particular things to research.
CEOs: The staff needs to know if anyone is not showing up, etc. ASAP.
Activity 0: Stand-Up Meeting
From now on, every lab will start with a 15-minute stand up meeting. Everyone will answer three questions (albeit this week it may be a bit of "nothing"):
- What did you do since the last meeting?
- What will you do between now and the next meeting?
- Are there any impediments in your way?
If you meet as a team outside of lab, you should be considering these questions since the last meeting, wherever that is. We encourage you to use the stand-up meeting method whenever the whole (or nearly whole) team is present.
The Scrum Master should direct this meeting and ensure you keep to time.
Activity 1: Sprint Planning
Between now and next Monday (the Monday before Spring Break), what will you accomplish? Suggestion: this week should probably be a research phase into the tech. More info will be coming soon regarding Django, servers, etc. Also, check the project pages... more info may arrive just before lab.
Requirements Managers should login to YouTrack and work with the team to assign tasks/stories as necessary. You should not have a story that is "research things." Instead, couch the research in the context of a story. Researching Django and Docker can come with a basic story regarding making the system available at multiple stations, for instance.
Activity 2: TA Check-In
The TAs will meet with their teams, checking on your progress. Today will be graded on a scale from 0-5, with 5 being fully prepared with good stories and ready to move on to the first sprint, and 0 being completely lost with no stories. The entire team will receive the same score.
- 5: The stories capture the project well, covering all main and secondary requirements, and individual stories are well written.
- 4: The stories mostly capture the entire project, but could be lacking in a few areas. Individual stories are well written.
- 3: The stories mostly capture the entire project, but the stories themselves do not do a good job at communicating the requirement.
- 2: There is a reasonable set of stories, but there was an obvious lack of effort from the team to do the assignment.
- 1: There are a few stories, but no understanding of the project.
- 0: No stories were produced.
Work on your sprint activities!!