Lab 13 - Sprint 5 Mid

Lab Date: Monday, April 23

Sprint 5 continues. Keep going! The finish is in sight!

Pre-lab Activities

Normal meetings today in lab.

In-lab Activities

Activity 0: Stand-Up Meeting

  1. What did you do since the last meeting?
  2. What will you do between now and the next meeting?
  3. Are there any impediments in your way?

Activity 1: TA Check-In

The TAs will meet with their teams, checking on your progress. Today will be graded on a scale from 0-5.

Rubric:

Each team member will receive a separate score this week. Teams are given a base score and then individual scores may vary based upon their performance during this sprint.

We are explicitly looking for feature sets finalizing and in the polish phase. Some basic documentation should also start to form, including info about your external API and information about how to run your system. Be ready to demo what has changed since last week for your TA.

  • 5: Score reserved for above-and-beyond/excellent performance, including sprint planning, team participation and technical presentation.
  • 4: Good, solid progress was made. Team member performed their duties adequately. Proposed milestones were met.
  • 3: Reasonable progress was made. A small number of team members did not fully perform their duties / were lacking in their effort or contribution. Proposed milestones were met, but shows technical limitations.
  • 2: Progress was made, but the team needs to improve significantly to move forward.
  • 1: Teams did not make progress on Sprint 4 and are effectively still on this sprint.
  • 0: Literally nothing was done.

Post-lab Activities

Work on your sprint activities!!

more ...

Lab 12 - Sprint 4 Ends / Sprint 5 Begins

Lab Date: Monday, April 16

Sprint 4 ends today and Sprint 5 begins.

We want to see a "working" system! Come ready to demo and explain what you (yes, you individually) did during this sprint!

Pre-lab Activities

Normal meetings today in lab.

Please fill out the Sprint 4 Team Eval before coming: https://goo.gl/forms/PKvm0dLf5g1k1Dkb2

In-lab Activities

Activity 0: Stand-Up Meeting

  1. What did you do since the last meeting?
  2. What will you do between now and the next meeting?
  3. Are there any impediments in your way?

Activity 2: Sprint Planning

Pick your stories for Sprint 5. Note it might NOT be "the rest of the stories." Be smart about what you target during this last sprint.

Activity 3: TA Check-In

The TAs will meet with their teams, checking on your progress. Today will be graded on a scale from 0-5.

Rubric:

Each team member will receive a separate score this week. Teams are given a base score and then individual scores may vary based upon their performance during this sprint.

  • 5: Score reserved for above-and-beyond/excellent performance, including sprint planning, team participation and technical presentation.
  • 4: Good, solid progress was made. Team member performed their duties adequately. Proposed milestones were met.
  • 3: Reasonable progress was made. A small number of team members did not fully perform their duties / were lacking in their effort or contribution. Proposed milestones were met, but shows technical limitations.
  • 2: Progress was made, but the team needs to improve significantly to move forward.
  • 1: Teams did not make progress on Sprint 4 and are effectively still on this sprint.
  • 0: Literally nothing was done.

Post-lab Activities

Work on your sprint activities!!

more ...

Lab 11 - Sprint 4 Continues

Lab Date: Monday, April 9

Sprint 4 continues today. There is no formal grade for work you have (or have not) done during this sprint. However, your TA will still check in with you and discuss how things are going.

Use this time to plan out your activities for the rest of Sprint 4 and to work together to tackle key problems you are having.

Pre-lab Activities

Normal meetings today in lab.

In-lab Activities

Activity 0: Stand-Up Meeting

  1. What did you do since the last meeting?
  2. What will you do between now and the next meeting?
  3. Are there any impediments in your way?

Activity 1: Sprint Work

Continue working on Sprint 4, updating your stories as necessary.

Activity 2: TA Check-In

The TAs will meet with their teams, checking on your progress. There is no grade for today.

Post-lab Activities

Here is basically what we expect to see at the end of Sprint 4: "Everything works, but it's really ugly looking."

Essentially, at the end of Sprint 4, your overall functionality should be done, or really close. This includes whatever solution you chose for your production platform. Sprint 5 should be about UI and polish.

At the end of Sprint 4, you will do another team evaluation. If you have concerns before then, please discuss with your TA and contact Prof. Sherriff directly.

more ...

Lab 10 - Sprint 3 Ends / Sprint 4 Begins

Lab Date: Monday, April 2

Sprint 3 ends today and Sprint 4 begins. As noted specifically in Lab 8 (when Sprint 3 began), we expect a technical demo of your system today.

Now we truly begin evaluating your team efforts toward the development process. How did you choose the stories for this sprint? How did everyone on your team participate? What did the evaluations from last week show us?

Pre-lab Activities

Normal meetings today in lab.

In-lab Activities

Activity 0: Stand-Up Meeting

  1. What did you do since the last meeting?
  2. What will you do between now and the next meeting?
  3. Are there any impediments in your way?

Activity 2: Sprint Planning

Pick your stories for Sprint 4. The course staff will expect to see an even more polished system by the end of this sprint.

Activity 3: TA Check-In

The TAs will meet with their teams, checking on your progress. Today will be graded on a scale from 0-5. Individuals may recieve different scores that their teammates based upon their performance during this sprint.

Rubric:

Each team member will receive a separate score this week.

  • 5: Score reserved for above-and-beyond/excellent performance, including sprint planning, team participation and technical presentation.
  • 4: Good, solid progress was made. Team members performed their duties adequately. Proposed milestones were met.
  • 3: Reasonable progress was made. A small number of team members did not fully perform their duties / were lacking in their effort or contribution. Proposed milestones were met, but shows technical limitations.
  • 2: Progress was made, but the team needs to improve significantly to move forward.
  • 1: Teams did not make progress on Sprint 3 and are effectively still on this sprint.
  • 0: Literally nothing was done.

Post-lab Activities

Work on your sprint activities!!

more ...

Lab 9 - Sprint 3 Continues

Lab Date: Monday, March 26

Sprint 3 continues today. There is no formal grade for work you have (or have not) done during this sprint. However, your TA will still check in with you and discuss how things are going.

Use this time to plan out your activities for the rest of Sprint 3 and to work together to tackle key problems you are having.

Pre-lab Activities

Normal meetings today in lab.

In-lab Activities

Activity 0: Stand-Up Meeting

  1. What did you do since the last meeting?
  2. What will you do between now and the next meeting?
  3. Are there any impediments in your way?

Activity 1: Sprint Work

Continue working on Sprint 3, updating your stories as necessary.

Activity 2: TA Check-In

The TAs will meet with their teams, checking on your progress. There is no grade for today.

Post-lab Activities

Work on your sprint activities!!

more ...

Lab 8 - Sprint 2 Ends / Sprint 3 Begins

Lab Date: Monday, March 19

Sprint 2 ends today and Sprint 3 begins. Sprint 2 got you moving on learning Django and designing your system. When you demo Sprint 3, we will expect a technical demo of your system.

Pre-lab Activities

Normal meetings today in lab.

In-lab Activities

Activity 0: Stand-Up Meeting

  1. What did you do since the last meeting?
  2. What will you do between now and the next meeting?
  3. Are there any impediments in your way?

Activity 1: Sprint Reflection

Look back over the stories you worked on in Sprint 2. What worked for you? What didn't? What do you need to do differently in Sprint 3 to make sure things are going to move forward? What resources do you need from the staff?

Activity 2: Sprint Planning

Pick your stories for Sprint 3. The course staff will expect to see a technical demo at the end of Sprint 3.

Activity 3: TA Check-In

The TAs will meet with their teams, checking on your progress. Today will be graded on a scale from 0-5. The entire team will receive the same score.

Rubric:

  • 5: Good progress was made on the proposed stories from Sprint 2. Good, solid technical work was done AND good design/architecture work was done.
  • 4: Good progress was made on the proposed stories from Sprint 2. Good, solid technical work was done OR good design/architecture work was done.
  • 3: Some progress was made on the proposed stories from Sprint 2. Only Django tutorial code was written or some very high level drawings of the system.
  • 2: Teams did not make good progress on stories from Sprint 2, but there seems to be at least some understanding.
  • 1: Teams did not make progress on Sprint 2 and are effectively still on this sprint.
  • 0: Literally nothing was done.

Post-lab Activities

Work on your sprint activities!!

more ...

Lab 7 - Sprint 2 Continues

Lab Date: Monday, March 12

Sprint 2 continues today. There is no formal grade for work you have (or have not) done during this sprint. However, your TA will still check in with you and discuss how things are going.

Use this time to plan out your activities for the rest of Sprint 2 and to work together to tackle key problems you are having.

Pre-lab Activities

Be ready to discuss these with your TAs!

In-lab Activities

Activity 0: Stand-Up Meeting

From now on, every lab will start with a 15-minute stand up meeting. Everyone will answer three questions:

  1. What did you do since the last meeting?
  2. What will you do between now and the next meeting?
  3. 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 Work

Continue working on Sprint 2, updating your stories as necessary.

Activity 2: TA Check-In

The TAs will meet with their teams, checking on your progress. There is no grade for today.

Post-lab Activities

Work on your sprint activities!!

more ...

Lab 6 - Sprint 1 Ends / Sprint 2 Begins

Lab Date: Monday, February 26

Sprint 1 ends today and Sprint 2 begins. Sprint 1 was intended to be a short, exploratory sprint. Sprint 2 should encompass the first major parts of development.

Pre-lab Activities

Be ready to discuss these with your TAs!

Requirements Managers: Make sure your YouTrack board is ready to go and updated.

Scrum Masters: Be ready to run the stand up meeting. Check these out, paying special attention to the 3 questions.

  • https://www.mountaingoatsoftware.com/agile/scrum/meetings/daily-scrum
  • https://sprint.ly/blog/scrum-meeting-best-practices/

Technology Managers: Be ready to explain to everyone some of the tech that's going to be used.

CEOs: The staff needs to know if anyone is not showing up, etc. ASAP.

In-lab Activities

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"):

  1. What did you do since the last meeting?
  2. What will you do between now and the next meeting?
  3. 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

Make sure all stories are updated and now start to pick out functionality stories that you will tackle over the next several weeks. Sprint 2 is long (with spring break in the middle) so plan accordingly.

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. The entire team will receive the same score.

Rubric:

  • 5: Good progress was made on the proposed stories from Sprint 1. Team members have some good ideas / staring points for the technology needed for the project. Teams are ready to go on Sprint 2.
  • 4: Good progress was made on the proposed stories from Sprint 1.
  • 3: Some progress was made on the proposed stories from Sprint 1. Teams are not quite ready on the tech for the next sprint, and still need to do more research. A significant part of Sprint 1 still lingers.
  • 2: Teams did not make good progress on stories from Sprint 1, but there seems to be at least some understanding.
  • 1: Teams did not make progress on Sprint 1 and are effectively still on this sprint.
  • 0: Literally nothing was done.

Post-lab Activities

Work on your sprint activities!!

more ...

Lab 5 - Sprint 1 Begins

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.

Pre-lab Activities

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.

  • https://www.mountaingoatsoftware.com/agile/scrum/meetings/daily-scrum
  • https://sprint.ly/blog/scrum-meeting-best-practices/

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.

In-lab Activities

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"):

  1. What did you do since the last meeting?
  2. What will you do between now and the next meeting?
  3. 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.

Rubric:

  • 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.

Post-lab Activities

Work on your sprint activities!!

more ...

Lab 4 - Requirements

Lab Date: Monday, February 12

The project begins with requirements elicitation and modeling. We will be using YouTrack to manage our user stories. Using GitHub integration, you can map your commits to your code back to features and issues that have been opened for your project.

Students may not leave early starting this week. We are giving you this dedicated time to work together as a full company and we expect you to take advantage of this time.

Pre-lab Activities

Requirements managers should look over the requirements page as information is added. They should also go into YouTrack to play around a bit and get a feel for things.

In-lab Activities

Activity 1: Go through the requirements information

The goal of today's lab is for the entire company to read through the requirements information and start to come up with a set of user stories that you will use throughout the project. It is highly likely that this activity will go longer than this lab session.

If/when you have questions about the requirements (such as follow up questions for the stakeholders), write up all of your questions in one document and make a post on Piazza (either public or private) and tag it with "project" and "requirements." This will be how you ask for clarification going forward. Major pieces of information will be posted to the requirements page on the website, but smaller items (clarification about the color of something, as a random example) will only be answers in Piazza.

Activity 2: Supplemental stuff

Make sure all of these things happen during lab:

  • Everyone beeps in
  • All members of your company can login to YouTrack and can see your project in YouTrack
  • All members of your company have access to the company's GitHub repository

Post-lab Activities

Complete your user stories in YouTrack for presenation to your Company TA next week. You will plan your first sprint next week and development will begin.

more ...