Three questions:
- What went well this sprint?
- What did not go well this sprint?
- What do you want to see changed/improved in the next sprint?
No debating items during each person's feedback, we will talk about issues after everyone has given their feedback
Went well -
- Had Jon W. consistently develop and make changes for multipage. Had the knowledge. Took ownership and aggressively completed the tasks. He used one way that worked; not necessarily the 'best' way.
- Had git and instructions for basic usage to manage the resources. Allowed for schedule page changes to dev/qa/prod per week.
- Automated testing with Geb and Spock was useful. Also tied this to Jenkins.
Did not go so well -
- Paul's code and ideas were 'lost' in the development cycle.
- 1 meeting per week does not necessarily allow for multi-developer contributions.
- Could have had an improved/clear definition of single vs. multi-page design. Internal code design vs. display.
- Some changes were pushed through quickly without much review.
Improvements for next Sprint -
- May incorporate some of Paul's developments that lend themselves to a cleaner design as well as a cleaner display.
- Sharing more code through git branches across developers. Have more team coordination across developers.
- Schedule code reviews between acceptance of changes.
- Try to set strict time constraints on some changes to move the sprint along.
- Provide a gap analysis during our meetings. What is missing or should be added. Could be part of construction and/or display.
— start —
I, Lora, was not able to attend On MLK Day. Here's my input:
Went well -
- Jon W's tech skills and ownership to make the changes needed to get it released.
- Completed in one month.
Did not go so well -
- What went well did make me realize that allowing a team member to get the work done in his/her native environment and then share it with the team is better than putting up a road block that would slow or stop the process. In this case, Jon didn't need to know the GIT repository and if we demanded he learn that first he likely would not have done the code updates. That should be fine going forward, in this case, there seemed to be an expectation that if the team is using GIT, he would have to - it's good he went ahead and got it done.
- IMO, the end of this sprint could have had a release.
Improvements for next Sprint -
- To gain coordination across developers, establish a second day & time for that to happen in addition to the monday web team.
— end —
A list of future action items has not yet been produced, but we will re-visit this next Monday and try again.
Attendees: Paul, Bob L., Thomas, Ken, Jim T., Tyler