Project Contribution Report for SDL
Write a PDF as directed below. Use sections of reports, screenshots of Jira
& GitLab, screenshots of your application, sections of code, portions
of documents, or other materials to provide evidence of contribution in
each of the following areas. Be sure to include the material in the report;
do not link to other documents. Be careful to keep your evidence relevant;
it's quite preferable to provide one or two detailed examples and then
describe your other work rather than simply dump everything you did into
the report.
Note this report is to reflect your personal contribution. It will not be
shared with the other students.
1. Contribution to Process
Provide evidence and discussion showing how you contributed to the team's
process, possibly including such things as
- notable contributions to the four Scrum ceremonies
- how you contributed to the team by executing your assigned Scrum role(s); be sure to state which roles you held
- following the appropriate Git workflow, including checkin comments,
branches you created, pull requests you created, examples of useful
comments you made during pull requests, and other ways in which you
contributed in Bitbucket, Gitlab, or similar repository
- ideas you contributed towards process improvement
- activities you've done that have lead to team process improvement
Be sure to include evidence where possible.
2. Software Product and Quality
Provide evidence of contributing to the team's product and quality,
including such things as
- stories that you have written
- PBIs for which you contributed a major portion; be sure to include
screenshots of any user-visible PBIs you implemented
- pull requests you created or to which you provided a major contribution
- features that you developed or to which you made major contributions
- tests you developed
- contributions you made to the continuous integration setup
- software design patterns you implemented
It is particularly important to document pull requests you wrote or to
which provided major contributions and screen shots and other evidence of
features you developed.
3. Effort
Construct a table showing your total hours for the quarter with breakdowns
for each sprint, the bye week, and any other time periods. If helpful,
write a paragraph discussing any discrepancies between your reported time
and the time computed by AboutTime.
4. Expected Grade
State what grade (or grade range) you believe would be appropriate given
your contributions. Defend your grade by describing your unique
contributions to the process, quality, and product. You might also discuss
any lessons you learned or improvements you made to your own process if you
believe they are relevant.
Submission
Submit your contribution report as instructed.
Author: Robert W. Hasker; last updated Nov. 11, 2019