Please include your answers below in a good format so it is easy for me to see. For answers to questions please use these Blockquotes. Make sure you also check the kickoff document for more details.
Topic you chose: Topic 3: Analyzing a Taiga Scrum Board
Sprint Number: 2
Scrum Master: Jessica Kuksuk
Git Master: Jemimah Thomas
Document your Sprint Planning here. Also check the kickoff document for more details on what needs to be done. This is just the documentation.
Sprint Goal: successful full functionality of the software and communication between memoranda and Taiga.
How many User Stories did you add to the Product Backlog: 13
How many User Stories did you add to this Sprint: 10
Answer the questions below about your Sprint Planning?
Why did you add exactly these US?
They were related to all of the functionaity mentioned in Topic 3 for analyzing the Taiga Scrum Board. There were a few US that were not finished from Sprint 1 and were also moved to this sprint to finish.
Why do you think you will get them done? (details)
They are all crucial and important pieces into getting the backend to work properly and function. This is also crucial because in Sprint 3 we will work on the front end UI which means that the backend will have to work properly.
Do you have a rough idea what you need to do? (if the answer is no then please let me know on Slack)
Yes we have a good understanding of our goals and what needs to be completed. We also set up a priority list for this sprint so we know which US have higher priority compared to others, which helps us understand what needs to get done first.
Fill out the Meeting minutes during your Sprint and keep track of things. Update your Quality policies when needed, as explained in the lectures and in the Quality Policy documents on Canvas. I would also advise you to already fill out the Contributions section (End of sprint) as you go, to create less work at the end.
Add as many rows as needed and fill out the table. (Burndown starts with Sprint 2 and Travis CI starts with Sprint 3, not needed before that)
| Date | Attendees | Rundown | Burndown Info | TravisCI info | Additional Info |
|---|---|---|---|---|---|
| 4/10 | 6 | Begining of sprint updates, starting to understand tasks and functionality | Optional Pending Points: 21, Real Points: 19 | NONE | Went Well |
| 4/13 | 6 | A lot of big tasks got completed for functions in the backend | Optional Pending Points: 14, Real Points: 13 | NONE | Went Well |
| 4/15 | 6 | More work and team updates focused on the backend and small changes to UI and logo's. | Optional Pending Points: 9, Real Points: 7 | NONE | Went Well |
| 4/17 | 6 | Completion of most all of the back end, with some focus on an early version of the scrumboard and login screen | Optional Pending Points: 7, Real Points: 5 | NONE | Went Well |
Add rows as needed and add the number how many meetings they attended:
Kevin : Num Meetings 3
Trent : Num Meetings 3
Maija : Num Meetings 3
Jemi : Num Meetings 3
Michael : Num Meetings 3
Jessica : Num Meeting 3
Screen Cast link: https://youtu.be/aQ3VeMPQ3Hc
Answer the following questions as a team.
What do you think is the value you created this Sprint?
Backend is basically done! Functionality is there and all that is left is displaying that information. Basic foundation for UI is laid and we have a good idea of what we need to develop in the next Sprint.
Do you think you worked enough and that you did what was expected of you?
We think we could have worked more consistently and we can agree that some put more hours in others. We did struggle to do reviews and as a result never really got everything to a 'common' branch and that was a problem throughout the sprint as we all tried to work using pieces of others' code. Process was not great and we can do better.
Would you say you met the customers’ expectations? Why, why not?
We met our Sprint goal, for the most part, but didn't get the chance to verify / integrate that functionality into the existing system.
Include your Sprint retrospective here and answer the following questions in an evidence based manner as a team (I do not want each of your individuals opinion here but the team perspective). By evidence-based manner it means I want a Yes or No on each of these questions, and for you to provide evidence for your answer. That is, don’t just say "Yes we did work at a consistent rate because we tried hard"; say "we worked at a consistent rate because here are the following tasks we completed per team member and the rate of commits in our Git logs."
Did you meet your sprint goal?
Yes, we did.
Did you complete all stories on your Spring Backlog?
No.
If not, what went wrong?
We had dependency issues and may have overcommitted and/or not worked consistently enough over the course of the sprint to process everything.
Did you work at a consistent rate of speed, or velocity? (Meaning did you work during the whole Sprint or did you start working when the deadline approached.)
This was a little different for everyone. We kind of dropped off in productivity as a team towards the end of the Sprint, as seen in our burndown.
Did you deliver business value?
Not many front end developments have been made so there's not a whole lot of user facing functionality to speak of at this point in time. That being said, the core components are in place to deliver this in our next Sprint.
Are there things the team thinks it can do better in the next Sprint?
We are working on a system that will help us communicate more frequently and asynchronously and hope to adhere to that in our next Sprint. We can be faster with reviews and test more.
How do you feel at this point? Get a pulse on the optimism of the team.
We are all looking forward to see the fruits of our labor realized through UI development. We're hoping the changes we make to our process will help resolve any outstanding concerns we have with the team dynamic and workflow.
In this section I want you to point me to your main contributions (each of you individually). Some of the topcs are not needed for the first deliverables (you should know which things you should have done in this Sprint, if you don't then you have probably missed something):
**Links to GitHub commits with main code contribution (up to 5 links):
- https://github.com/amehlhase316/Lebkuchen/pull/45/commits/7f73d0b182d6b3ef2d39d34b5b89000a544232ea
- https://github.com/amehlhase316/Lebkuchen/pull/45/commits/1488c3a7c16fe8d31e8ffd94759994bbd6b2ab7e
- https://github.com/amehlhase316/Lebkuchen/pull/49/commits/8f8b25347eda4042d52e7690954bef40cd485324
- https://github.com/amehlhase316/Lebkuchen/pull/50/commits/a17488cb5e60bea5c9eed2337e5a1a4e47666728
- https://github.com/amehlhase316/Lebkuchen/commit/b58d3cd3b098ab3517798114fdb58bbc2961c10e
**GitHub links to your Unit Tests (up to 3 links):
- https://github.com/amehlhase316/Lebkuchen/pull/45/commits/7f73d0b182d6b3ef2d39d34b5b89000a544232ea
- https://github.com/amehlhase316/Lebkuchen/pull/45/commits/1488c3a7c16fe8d31e8ffd94759994bbd6b2ab7e
**GitHub links to your Code Reviews (up to 3 links):
- https://github.com/amehlhase316/Lebkuchen/pull/52#pullrequestreview-396064194
- https://github.com/amehlhase316/Lebkuchen/pull/33#pullrequestreview-391669000
- https://github.com/amehlhase316/Lebkuchen/pull/37#pullrequestreview-391795073
**How did you contribute to Static Analysis: - I did my best to ensure that my own code followed style guidelines & had a wealth of readable documentation that everyone could lean on - I don't really have links that demonstrate this but my key code commits should demonstrate this, for the most part
**What was your main contribution to the Quality Policy documentation?:
- I basically wrote all of it
**Links to GitHub commits with main code contribution (up to 5 links):
- https://github.com/amehlhase316/Lebkuchen/tree/Task%2392
- https://github.com/amehlhase316/Lebkuchen/tree/Task%2393
- https://github.com/amehlhase316/Lebkuchen/tree/Task%23115
**GitHub links to your Code Reviews (up to 3 links):
- https://github.com/amehlhase316/Lebkuchen/pull/40
- https://github.com/amehlhase316/Lebkuchen/pull/49
- https://github.com/amehlhase316/Lebkuchen/pull/52
**How did you contribute to Static Analysis:
- I read through the style and bug guidelines and the Quality Policy Documentation (written by Trent) to help ensure that my code and reviews were followed properly.
**What was your main contribution to the Quality Policy documentation?:
- Helping with decisions on what should be added/removed/changed in the documentation.
**Links to GitHub commits with main code contribution (up to 5 links):
- https://github.com/amehlhase316/Lebkuchen/pull/40
- https://github.com/amehlhase316/Lebkuchen/pull/38
- https://github.com/amehlhase316/Lebkuchen/pull/43
- https://github.com/amehlhase316/Lebkuchen/pull/48 // not yet merged
- https://github.com/amehlhase316/Lebkuchen/pull/57 // not yet merged
**GitHub links to your Code Reviews (up to 3 links):
- https://github.com/amehlhase316/Lebkuchen/pull/46
- https://github.com/amehlhase316/Lebkuchen/pull/42
- https://github.com/amehlhase316/Lebkuchen/pull/45 // errors
**How did you contribute to Static Analysis:
- Removed out/ from git tracking
**What was your main contribution to the Quality Policy documentation?: - Helping with decisions on what should be added/removed/changed in the documentation.
**Links to GitHub commits with main code contribution (up to 5 links):
-https://github.com/amehlhase316/Lebkuchen/commit/7180e8e39d99a06c7c61cd05273050fc345e245b
-https://github.com/amehlhase316/Lebkuchen/commit/cad96825662d3f4e4298a3e1e51637a9be7d1ce5
-https://github.com/amehlhase316/Lebkuchen/commit/6b0105f07ef9c652f86ca6aa5d1ff50ca0231d3e
-https://github.com/amehlhase316/Lebkuchen/commit/8f68216c0250baf0e341adc03bc5e1f4883a7967
**GitHub links to your Code Reviews (up to 3 links):
-https://github.com/amehlhase316/Lebkuchen/pull/43#pullrequestreview-393952417
-https://github.com/amehlhase316/Lebkuchen/pull/50#pullrequestreview-396095954
-https://github.com/amehlhase316/Lebkuchen/pull/49#pullrequestreview-396096593
**How did you contribute to Static Analysis:
- Followed Quality Policy when coding/reviewing
**What was your main contribution to the Quality Policy documentation?:
- Discussed Quality Policy with team
**Links to GitHub commits with main code contribution (up to 5 links): - My commits are spread out all over the place. I built the entire api package and interfaced with the model package. Built all data store data structures.
-https://github.com/amehlhase316/Lebkuchen/commit/fe05a07182b042b542c96f5f9a1012f3974a672d
-https://github.com/amehlhase316/Lebkuchen/commit/7b740118378ff9285fb855b8a5ff2355caee67a9
-https://github.com/amehlhase316/Lebkuchen/commit/379e8db619660972b7cd910e28eb3d0409d6d093
-https://github.com/amehlhase316/Lebkuchen/commit/4fc6a1ca365d2fce9395a235f8d3fc52efd8703e
-https://github.com/amehlhase316/Lebkuchen/commit/3d04b9296ec1a4f10f9f1121b3630f72061b5dc3
**GitHub links to your Code Reviews (up to 3 links):
-https://github.com/amehlhase316/Lebkuchen/pull/37
-https://github.com/amehlhase316/Lebkuchen/pull/33
-https://github.com/amehlhase316/Lebkuchen/pull/39
**How did you contribute to Static Analysis:
-I integrated spotbugs, checkstyle, and travis ci with the project. Fixed multiple checkstyle and spotbugs.
**What was your main contribution to the Quality Policy documentation?:
- Discussed Quality Policy with team and suggested quality policy adjustments
#### Jemimah Thomas:
**Links to GitHub commits with main code contribution (up to 5 links): - My main commit this Sprint was mapping out all of the Memoranda UI to it's respective classes in the source code. Also made cosmetic changes to language bugs and removing references to Memoranda from the existing UI
- https://github.com/amehlhase316/Lebkuchen/pull/53/commits/9087f68bc892c1d544c1a89ea165f3e68d7a56e3
- https://github.com/amehlhase316/Lebkuchen/pull/56/files
- https://github.com/amehlhase316/Lebkuchen/commit/a32d50fbee3aa5194eb50701d9b1191f93794c42
- https://github.com/amehlhase316/Lebkuchen/commit/9b782513ec45b6e6c51954c28bf09edafbbecd00
**GitHub links to your Code Reviews (up to 3 links):
- https://github.com/amehlhase316/Lebkuchen/pull/44
- https://github.com/amehlhase316/Lebkuchen/pull/57
**How did you contribute to Static Analysis:
- Acted as GitMaster to ensure merges, and the required reviews, were happening in a timely manner.
- Configured Spotbugs to not fail on build
- Fixed Spotbugs errors in the Storyless branch
**What was your main contribution to the Quality Policy documentation?:
- We came up with quality policy measures together and collaborated on Quality Policy updates regarding review policies
(make it the first thing you do before moving onto any other part of the project).
ScrumMaster acts as backup to GitMaster in case GitMaster is not available
- Filled out the complete form from above, all fields are filled and written in full sentences
- Read the kickoff again to make sure you have all the details
- User Stories that were not completed, were left in the Sprint and a copy created
- Your Quality Policies are accurate and up to date
- Individual Survey was submitted individually (create checkboxes below -- see Canvas to get link)
- Trent Engelman
- Jessica Kuksuk
- Michael Schnapp
- Maija Kingston
- Jemimah Thomas
- The original of this file was copied for the next Sprint (needed for all but last Sprint where you do not need to copy it anymore)
- Basic information (part 1) for next Sprint was included (meaning Spring Planning is complete)
- All User Stories have acceptance tests
- User Stories in your new Sprint Backlog have initial tasks which are in New
- You know how to proceed