Expected duration
1 hour per team member
Deadline
2359 on Lessons 17, 28, 37
Points
10 points

Learning Objectives

  • Prepare written software engineering artifacts, such as project plans, schedules, and reports
  • Employ software project management principles to orchestrate team efforts, mitigate risks, and produce high quality software systems

Help Policy

Authorized Resources
Any, except classmates working on other teams
Notes
Never copy another person’s work and submit it as your own

You must document all help received from all sources, including the instructor and instructor-provided course materials (such as the textbook)

Assignment

Provide notes from your team’s sprint retrospective with the following information:

  • When the retrospective was held and who attended (which should be everyone on the team)
  • The URL of the pull request for your team’s specification
  • The URL(s) of the pull request(s) for your team’s implementation activities (i.e., source code and tests)
  • The change(s) that you made in response to the prior sprint’s retrospective
  • What issue(s) you encountered during the sprint
  • What change(s) you will make for the next sprint
  • The contribution(s) of each team member – i.e., how each individual contributed to the various sprint deliverables

Pull requests have the form https://github.com/user/repository/pull/number where account is the name of the GitHub user who should merge the pull request, repository is the name of the repository, and number is an integer that identifies the specific pull request. By listing the pull requests, you ensure that your submission links to the permanent record of your work.

Please ensure that the URLs are hyperlinked correctly – i.e., clicking on a URL should open the link in a new window.

Use the template in the project repository for the retrospective notes.

Submission

Create a pull request in GitHub for your retrospective notes. In Canvas, submit the URL for the pull request and include your documentation statement as part of your submission.

Only one person on each team should submit this assignment.

Grading

The following grading rubric will be used for this assignment:

Superb (100%)
Retrospective notes complete with no omissions. Clearly defines issues and changes with reflection on underlying causes; ideas are feasible to implement.
Proficient (90%)
Retrospective notes complete with no omissions. Defines issues and changes, but with high-level reflection, lacking specificity in places; ideas are feasible to implement.
Competent (75%)
Retrospective notes contain minor omission. Describes issues and possible changes, but only with high-level reflection; ideas may be unrealistic to implement.
Marginal (50%)
Retrospective notes have multiple omissions. Describes issues superficially; ideas may be unrealistic to implement.
Unsatisfactory (25%)
Retrospective notes obviously incomplete. Describes issues superficially; ideas missing or unrealistic to implement.

Resources

A Simple Way to Run a Sprint Retrospective

Project sprints retrospective overview